- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 23 Aug 2016 12:00:34 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 23 August 2016 19:01:09 UTC
Indeed. In general the multi-tag designs of HTML (e.g. `<select>` + `<option>`, `<ul>` + `<li>`, `<picture>` + `<source>` + `<img>`, etc.) are very fragile; the amount of spec machinery involved in making them work correctly is extensive and in some cases still buggy in the current spec. (We don't even have a correct design for `<li>` yet, this many years later: https://github.com/whatwg/html/issues/1617.) Web devs should be very cautious when trying to set up such designs for their custom elements; you need to be aware of how children change dynamically, and not just use the children as some kind of setup data. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/551#issuecomment-241840803
Received on Tuesday, 23 August 2016 19:01:09 UTC