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 7044 (Kkk2) - [ARIA 2.0] Work with browser vendors to come up with convention for forward compatibility of ARIA states and properties
Summary: [ARIA 2.0] Work with browser vendors to come up with convention for forward c...
Status: RESOLVED WONTFIX
Alias: Kkk2
Product: ARIA
Classification: Unclassified
Component: General (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P3 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
: Kkk (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-22 15:47 UTC by Andi Snow-Weaver
Modified: 2016-01-19 18:51 UTC (History)
3 users (show)

See Also:

Attachments

Description Andi Snow-Weaver 2009-06-22 15:47:01 UTC 
From section 3.5, bullet # 5: "For forward compatibility with new ARIA properties in future versions, user agents SHOULD expose all properties not in this table with an object attribute, removing the "ari-" prefix from the name."
Comment 1 Andi Snow-Weaver 2010-07-28 17:13:11 UTC 
From Gez:

Hi Gregory,

Thank you so much for picking up this issue. I think it's clear that
although the HTML5 specification states that the drag and drop
mechanism should be device independent, it's reverse engineered from a
mouse-based implementation, and the order of states required to
complete a drag and drop implementation couldn't possibly completed
using the keyboard alone.

Like you, I would like to see the current drag and drop mechanism
altered so that it can be implemented in a device independent way. If
the copy and paste API is required to make this work, it will need to
be amended so that it fits with the workflow defined in the WAI-ARIA
authoring practices document - for example, identifying draggable
objects and explaining the effect of dropping the source on a target.
Comment 2 Andi Snow-Weaver 2010-07-28 17:15:50 UTC 
Please ignore comments I posted in from Gez. These were meant for 6912.
Comment 3 James Craig 2013-11-12 18:40:11 UTC 
*** Bug 23301 has been marked as a duplicate of this bug. ***
Comment 4 Cynthia Shelly 2016-01-19 18:51:06 UTC 
I think this is overcome by events