- From: <bugzilla@jessica.w3.org>
- Date: Tue, 28 May 2013 00:06:33 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20294
Dominic Cooney <dominicc@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |dominicc@chromium.org
Resolution|--- |FIXED
--- Comment #1 from Dominic Cooney <dominicc@chromium.org> ---
I removed that specific language--I guess it refers to "author reset
stylesheets", but that is a novel concept, I think most web developers would
take that to mean "browser reset stylesheets" which are of course still
necessary.
So I engaged in some exposition pointing out that if you want maximum style
isolation you'll turn off apply-author-styles and turn on
reset-style-inheritance; it now reads:
"You can relax this boundary with the apply-author-styles attribute on the
<template> element. With the attribute present, document's author styles start
applying in the shadow DOM subtree.
Conversely, you can make the boundary even stronger by setting the
reset-style-inheritance attribute on the <template> element. With the attribute
present, all styles are reset to initial values at the shadow boundary.
If you omit apply-author-styles and set reset-style-inheritance you're back to
a clean slate. Your element is insulated from the styles in the page—even
inherited properties—and you can use a browser reset stylesheet to build up the
exact style you want."
<https://dvcs.w3.org/hg/webcomponents/rev/0154dbb74713>
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 28 May 2013 00:06:42 UTC