-
Notifications
You must be signed in to change notification settings - Fork 85
Close watchers #604
Copy link
Copy link
Closed
Labels
position: positivevenue: W3C CGSpecifications in W3C Community Groups (e.g., WICG, Privacy CG)Specifications in W3C Community Groups (e.g., WICG, Privacy CG)venue: WHATWGSpecifications in a WHATWG WorkstreamSpecifications in a WHATWG Workstream
Metadata
Metadata
Assignees
Labels
position: positivevenue: W3C CGSpecifications in W3C Community Groups (e.g., WICG, Privacy CG)Specifications in W3C Community Groups (e.g., WICG, Privacy CG)venue: WHATWGSpecifications in a WHATWG WorkstreamSpecifications in a WHATWG Workstream
Type
Fields
Give feedbackNo fields configured for issues without a type.

Request for Mozilla Position on an Emerging Web Specification
Other information
We've been prototyping this API over in Chromium for some time. It's a small offshoot of the work in #543 on new history APIs generally. The original intent was to make it so that developers don't have to abuse the history API to detect Android back button presses, and this is still probably the largest impact. We've also found that it has some significant benefits in terms of smoothing over platform differences, since it "just works" no matter if you're using a keyboard, Android software back button, Android swipe gestures, or assistive tech gestures.
Previous feedback from @annevk was that we should be sure to integrate with existing primitives such as fullscreen and
<dialog>. We took that to heart and I'm pretty happy with how the result turned out; the updates to other specs now put them on a shared foundation that's pretty nice and much more rigorous than previous prose, IMO.