24876 2014-03-01 08:38:13 +0000 [Custom Elements]: Custom elements should be display: block by default 2015-07-06 08:08:37 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 14949 1 esprehn dglazkov adamk bzbarsky mike public-webapps public-webapps-bugzilla oldest_to_newest 101695 0 esprehn 2014-03-01 08:38:13 +0000 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. 101701 1 bzbarsky 2014-03-01 20:15:58 +0000 Custom form controls presumably wouldn't be display:block... 101792 2 esprehn 2014-03-03 21:35:39 +0000 (In reply to Boris Zbarsky from comment #1) > Custom form controls presumably wouldn't be display:block... Indeed, they probably want to be display: inline-block. What I've observed is that in many modern applications custom elements are placed inside flex boxes so display: block is fine since they end up flexed anyway (if they were inline they end up inside anonymous blocks instead). 101793 3 bzbarsky 2014-03-03 22:15:19 +0000 Inlines in a flex container don't create anonymous blocks; they just end up with a computed display of "block". The only anonymous anything that happens with flexbox is that text that's a direct child of a flexbox is wrapped in an anonymous flex item. 121675 4 hayato 2015-07-06 08:08:37 +0000 Moved to https://github.com/w3c/webcomponents/issues/224