W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 20186] New: [Custom]: Add a CSS pseudo to distinguish between upgraded, custom elements

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Nov 2012 18:06:33 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20186-2532@http.www.w3.org/Bugs/Public/>

            Bug ID: 20186
           Summary: [Custom]: Add a CSS pseudo to distinguish between
                    upgraded, custom elements
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: danieljb2@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

There should be a sane way to distinguish/style elements in their original,
non-upgraded state. We don't want every component developer to roll their own
attribute flag for this, as it will surely be a common case.

You can approach this from two angles: a pseudo to specify an element is
upgraded, :upgraded, or a pseudo for custom elements that are yet to be
upgraded, :beforeupgrade.

I can almost guarantee devs will write far more styles targeting the upgraded
state, and mostly small visual stuff for elements that are not yet upgraded (a
background spinner for instance).

Not sure what route to take, thoughts?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 November 2012 18:06:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:28 UTC