https://www.w3.org/Bugs/Public/show_bug.cgi?id=28659
Bug ID: 28659
Summary: [Shadow]: Remove Section 8. HTML Elements and Their
Shadow Trees from the spec
Product: WebAppsWG
Version: unspecified
Hardware: PC
On Mon, May 18, 2015 at 8:54 PM, Hayato Ito hay...@chromium.org wrote:
The hint we can use is:
- tag name
- id attribute
- class attribute
- any other attributes. (Okay to have a dedicated attribute, such as
'content-slot')
- The position of the node in the list
- Other status, such as
From: Elliott Sprehn [mailto:espr...@chromium.org]
Given the widget ui-collapsible that expects a ui-collapsible-header in the
content model, with slots I can write:
ui-collapsible
my-header-v1 slot=ui-collapsible-header ... /...
/ui-collapsible
ui-collapsible
my-header-v2
Congratulations to Ian and all the contributors!
On 5/19/15 12:53 PM, Coralie Mercier wrote:
It is my pleasure to announce that HTML5 Web Messaging is published as
a W3C Recommendation
http://www.w3.org/TR/2015/REC-webmessaging-20150519/
This specification defines two mechanisms
On Tue, May 19, 2015 at 10:09 AM, Domenic Denicola d...@domenic.me wrote:
From: Elliott Sprehn [mailto:espr...@chromium.org]
Given the widget ui-collapsible that expects a ui-collapsible-header
in the content model, with slots I can write:
ui-collapsible
my-header-v1
On Tue, May 19, 2015 at 10:09 AM, Domenic Denicola d...@domenic.me wrote:
I think this model you cite Polymer using is different from what HTML
normally does, which is why it was confusing to me. In HTML the insertion
point tags (e.g. summary or li or option) act as dumb containers.
This was
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16103
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Resolution|LATER |DUPLICATE
--- Comment
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26492
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
From: Dimitri Glazkov [mailto:dglaz...@google.com]
Not sure what you mean by Polymer model.
I was referring to Elliot's This is identical to the common usage today in
polymer apps where you annotate your own element with classes.
When we have custom elements, the assumption of dumb
