- From: <bugzilla@jessica.w3.org>
- Date: Thu, 15 Nov 2012 07:52:57 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19874
Tab Atkins Jr. <jackalmage@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackalmage@gmail.com
--- Comment #6 from Tab Atkins Jr. <jackalmage@gmail.com> ---
(In reply to comment #1)
> I believe the cascade/specificity bit is actually well-defined, or at the
> very least there is a proposal everyone agrees on last I checked.
It's now well-defined in the Cascade module:
<http://dev.w3.org/csswg/css3-cascade/#cascade>
> I agree that fonts and variables are a problem that may warrant pulling this
> from the HTML5 REC.
Variables are a non-issue. They're properties, and so scope just as well as
anything else.
For fonts, it depends. If we're willing to say "welp, those aren't actually
scoped - they leak into the global font set", then it's easy. I've seen
pushback in doing anything better. :/
We could do something like disable @font-face normally, only allowing it in an
@host rule (which relaxes the scoping). @host still needs to be properly
defined, of course.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 15 November 2012 07:52:58 UTC