- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Aug 2012 23:15:33 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18534
Summary: [Custom]: Pseudo-class to mitigate FOUC
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
AssignedTo: dglazkov@chromium.org
ReportedBy: dglazkov@chromium.org
QAContact: public-webapps-bugzilla@w3.org
Blocks: 14968
It seems that it might be good to have a CSS pseudo-class to help mitigate the
inherent FOUC with Web Components (now that they are asynchronous again).
The question is what should they be?
One idea is to have ":shadow-host", which simply indicates if the current
element is a shadow host or not. This is specific to shadow DOM spec, which
makes it applicable in non-Web Components world
Another idea would be to have ":component", which matches when an element is a
custom DOM element.
Yet another thought is to just add ":components-ready", which only matches on
document and shares the timing of some "componentsready" DOM event.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 August 2012 23:15:36 UTC