This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18534 - [Custom]: Pseudo-class to mitigate FOUC
Summary: [Custom]: Pseudo-class to mitigate FOUC
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
: 20186 (view as bug list)
Depends on:
Blocks: 18720
  Show dependency treegraph
 
Reported: 2012-08-10 23:15 UTC by Dimitri Glazkov
Modified: 2012-12-10 20:30 UTC (History)
2 users (show)

See Also:


Attachments

Description Dimitri Glazkov 2012-08-10 23:15:33 UTC
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.
Comment 1 Dimitri Glazkov 2012-08-13 20:45:15 UTC
Elliott Sprehn suggested ":unknown" for any elements that have HTMLUnknownElement backing. This seems awesome.
Comment 2 Dimitri Glazkov 2012-08-28 20:45:08 UTC
http://dvcs.w3.org/hg/webcomponents/rev/94e3b76fa3a2
Comment 3 Dimitri Glazkov 2012-12-10 20:30:47 UTC
*** Bug 20186 has been marked as a duplicate of this bug. ***