Bug 144065

Summary: IndieUI: proof-of-concept for dismiss request
Product: WebKit Reporter: James Craig <jcraig>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: cfleizach, jcraig, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   

Description James Craig 2015-04-22 12:19:05 PDT
Even though this is not an accessibility-specific feature, filing under the Accessibility component for now b/c there isn't a better place to implement end-to-end.

The "dismiss" request proof-of-concept example will fire a single event for any of the following physical events:

- mouse click (OS X) on the UITrigger "close" <button>.
- tap (iOS) on the UITrigger "close" <button>.
- spacebar key press (OS X) on the UITrigger "close" <button> (when focused).
- escape key press (OS X) anytime focus is in the view.
- VoiceOver's two-finger "scrub" gesture when VoiceOver is active on iOS.

Test case to be added.
Comment 1 Radar WebKit Bug Importer 2015-04-22 12:19:31 PDT
<rdar://problem/20655266>
Comment 2 James Craig 2015-04-22 12:22:24 PDT
Related to bug 144066
Comment 3 chris fleizach 2015-04-22 15:35:44 PDT
When you say UITrigger, where is that coming from?
Comment 5 James Craig 2015-05-19 01:42:44 PDT
(In reply to comment #3)
> When you say UITrigger, where is that coming from?

A UITrigger is an element whose default action (click, etc) is to trigger a action on an ancestor element. For example, a "cancel" button might trigger a "dismiss" action on a sheet. A "remove item from cart" button might trigger a "delete" action on an item in a web shopping cart. The association between the trigger and the event receiver is defined through use of the @uiactions attribute on the receiver element, and a corresponding @uitrigger attribute on the descendant trigger element.
Comment 6 James Craig 2015-05-19 01:49:45 PDT
*** Bug 144551 has been marked as a duplicate of this bug. ***
Comment 7 James Craig 2015-08-20 17:17:08 PDT
The goal of this proof-of-concept is to take work previously specified in IndieUI and demonstrate its value to other WGs, especially the general value that is not related to accessibility. The final API is unlikely to end up using the exact IndieUI API, in part due to baggage related to WAI process.

The concepts are just complicated enough that few people understand the problem space. A demo is worth a thousand words.
Comment 8 James Craig 2019-04-24 17:48:57 PDT
Obsolete.