MSEdgeExplainers
MSEdgeExplainers copied to clipboard
MicrosoftEdge
Home for explainer documents originated by the Microsoft Edge team
Web Install is an imperative (JS) API. Is this better than declarative? What are the reasons for this?
Updates the same-origin Web Install explainer to support a 0-param installation (instead of requiring a single `id` param) and adds the requirement that the app to-be-installed must have a manifest...
Originally mentioned here by @dmurph: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/893#issuecomment-2427070370 > I think **we should consider preventing install if there is an app already installed that controls the start_url of the app**, or the...
[Declarative Shadow DOM Style Sharing] consider compatibility between declarative and imperative use
It's common for users to create Shadow DOM imperatively in custom elements. Libraries can then server side render SSR the result into declarative Shadow DOM that later upgrades to a...
The comparison table at the bottom of the explainer is useful, but it's unfortunately an image, which is not accessible to screen readers (unless it had an alt text, which...
Document showing how to enable and use ClipboardItem data DOMString support in Chromium-based browsers. This serves as supporting document for https://chromestatus.com/feature/4926138582040576
The proposal allows multiple module specifiers in in `adoptedstylesheets` like so: ```html ``` This indicates that comma (or comma-space) is a delimiter between multiple URLs, however commas and spaces are...
Adds initial files to publish the systray icon explainer to the edge repo.
The main issues with using `` in declarative Shadow DOM (DSD) are: 1. It's not equivalent to adopting a stylesheet since the sheet is not shared between different shadowRoots. A...
Metadata
Owner
Metadata
Home for explainer documents originated by the Microsoft Edge team