This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7115 - 4.2 add something about properties that cause other actions to be possible
Summary: 4.2 add something about properties that cause other actions to be possible
Status: RESOLVED WONTFIX
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC All
: P1 normal
Target Milestone: ---
Assignee: Andi Snow-Weaver
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 12:12 UTC by Andi Snow-Weaver
Modified: 2010-11-11 12:45 UTC (History)
2 users (show)

See Also:

Attachments

Description Andi Snow-Weaver 2009-07-17 12:12:09 UTC 
From Jul 10 meeting: for example, draggable, editable, etc.
Comment 1 Andi Snow-Weaver 2009-08-05 16:46:48 UTC 
Placeholder for all properties that make other actions possible - draggable, editable, others? 

Expect that if object has draggable property, browser should do something about it. 

AT could send synthetic mouse down if wanted to start drag action.

Discussed at July 20 F2F in Boston. Andi has notes on her hardcopy of the UAIG.
Comment 2 Andi Snow-Weaver 2009-10-01 21:15:12 UTC 
Cynthia, please review the table I added.
Comment 3 Andi Snow-Weaver 2010-01-12 15:56:02 UTC 
table is currently in section 4.7 Actions
Comment 4 Cynthia Shelly 2010-04-20 19:27:34 UTC 
This looks good to me.  Some thoughts below.  I'm not sure all of these need to be documented.

aria-disabled removes all actions. 

I wonder if aria-labelledby makes the referenced element recieve clicks and focus?  That happens with <label for>

multiselectable allows for ctrl+click and shift+click.

read-only removes edit action
Comment 6 Cynthia Shelly 2010-10-28 14:52:59 UTC 
Delete this table
Comment 7 Andi Snow-Weaver 2010-11-11 12:45:21 UTC 
Deleted table.