MSEdgeExplainers
MSEdgeExplainers copied to clipboard
Home for explainer documents originated by the Microsoft Edge team
HighlightPointerEvent extends PointerEvent and the explainer says: "When a user performs a pointer action on part of an element containing a highlighted Range, a HighlightPointerEvent object must be fired" In...
If event.target stays as the element, and when currentTarget == target, that is supposed to be AT_TARGET phase. But since propagation goes through Highlight, the examples seem to hint that...
Potential issue for the version history explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VersionHistory/explainer.md The MiniApp Manifest is an extension to the web app manifest, and it already defines a version member: https://www.w3.org/TR/miniapp-manifest/#version-member Not sure what...
The highlight events explainer (https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/events-explainer.md#multiple-ranges-and-highlightrangegroups) describes two options for firing the HighlightRangePointerEvent. The first option states that the event is only fired to the Range/HighlightRangeGroup pair with the highest priority....
`Highlight`, as currently defined (https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/events-explainer.md#interaction-with-pointer-capture), cannot receive implicit or explicit pointer capture. This is largely because there is no currently known scenario that requires pointer capture on highlights, and also...
@Brandr0id for initial review, then Firefox/WebKit folks and Identity folks.
There are 3 readyStates in this order: 1. loading | | -> DOMContentLoaded fires 2. interactive | | < - script executes, `!complete ? addEventListener(...) : OneTimeInit()` // addEventListener wins...
An element can have the `contenteditable` value "true" but also "" (emty string) or to be editable. See: https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/contenteditable But anyway, an easier way to see if it's a contenteditable-root...
Hi folks, I just reviewed the spec and my knee-jerk reaction is that we're introducing a lot of additional terms into the ecosystem and I wonder if we could leverage...
- Add permissions bundles to allow for tiered API access. - Minor changes (implementor → implementer [Ngrams](https://books.google.com/ngrams/graph?content=implementor%2Cimplementer&year_start=1900&year_end=2008&corpus=15&smoothing=3&share=&direct_url=t1%3B%2Cimplementor%3B%2Cc0%3B.t1%3B%2Cimplementer%3B%2Cc0)).