Contact emails ksc...@microsoft.com<mailto:ksc...@microsoft.com>
Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/LocalReferenceLinkRel/explainer.md Specification This will be added to the HTML5 specification. Summary Extends the ability of the <link> tag to support fragment identifier references to inline style tags. This is only supported when the <link> tag is used to include a stylesheet (<link rel="stylesheet">). This feature is useful for shadow DOM, allowing developers to selectively share inline styles between the light DOM and shadow DOM. Without this feature, the only declarative options for sharing styles with shadow DOM nodes are to either duplicate <style> tags or use external CSS files. Blink component Blink>DOM<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22> Motivation Shadow DOM provides style isolation, but developers often want to share some set of styles between shadow DOM subtrees and the light DOM. Existing solutions either require external files or duplicated styles. There are more options available when scripting is involved (e.g. adoptedStylesheets), but fully declarative options are limited. This feature provides an additional option for sharing styles declaratively without duplicated markup or external resource requests. Initial public proposal https://github.com/whatwg/html/issues/11019 TAG review None - this will be started soon TAG review status Pending Risks Interoperability and Compatibility None Gecko: No signal WebKit: No signal Web developers: No signals Other signals: https://css-tricks.com/encapsulating-style-and-structure-with-shadow-dom/#aa-strategies-for-styling-the-shadow-dom https://stackoverflow.com/questions/35694328/how-to-use-global-css-styles-in-shadow-dom https://lamplightdev.com/blog/2021/03/23/how-to-share-styles-in-the-shadow-dom/ https://eisenbergeffect.medium.com/sharing-styles-in-declarative-shadow-dom-c5bf84ffd311 https://www.smashingmagazine.com/2016/12/styling-web-components-using-a-shared-style-sheet/ WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability None Is this feature fully tested by web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? Will be added upon implementation. Flag name on about://flags None Finch feature name None Non-finch justification None Requires code in //chrome? False Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5138494732894208?gate=5183021279608832 This intent message was generated by Chrome Platform Status<https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DS0PR00MB25414C7956CF9294BA9D4267D6832%40DS0PR00MB2541.namprd00.prod.outlook.com.
