W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

[Bug 24876] New: [Custom Elements]: Custom elements should be display: block by default

From: <bugzilla@jessica.w3.org>
Date: Sat, 01 Mar 2014 08:38:13 +0000
To: public-webapps@w3.org
Message-ID: <bug-24876-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24876

            Bug ID: 24876
           Summary: [Custom Elements]: Custom elements should be display:
                    block by default
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: esprehn@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14949

Almost every custom element I've seen so far has:

<style>
  :host { display: block }
</style>

inside the ShadowRoot, or a rule in the owning page that makes it into display:
block since the default of display: inline for unknown elements is really never
want you want. I've also seen lots of authors stumble trying to figure out why
their custom elements look busted when they first start before they realize
they all need this rule.

I think we should consider add some kind of pseudo like :custom and then say
the UA sheet has :custom { display: block } to make this simpler.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 1 March 2014 08:38:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC