- From: <bugzilla@jessica.w3.org>
- Date: Sat, 01 Mar 2014 06:06:34 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24872
Ryosuke Niwa <rniwa@webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eoconnor@apple.com,
| |rniwa@webkit.org
--- Comment #3 from Ryosuke Niwa <rniwa@webkit.org> ---
(In reply to Jonas Sicking from comment #1)
> My concern with this is that it means that anytime that a node is inserted
> anywhere, we need to recheck the insertion-point for all of its siblings.
Same concern here. The problem with :first-of-type is that it involves walking
previous siblings to check this condition when multiple children are inserted
via document fragments.
(In reply to Domenic Denicola from comment #2)
> I would really much prefer if there was an imperative way to add content;
> the <content> element is un-ergonomic and very hard to use in a sensible
> way. I am hearing this feedback from multiple developers as I try to show
> them shadow DOM.
>
> I know there is already an open issue for this (bug 18429) but I thought it
> was relevant since this bug seems to be about putting lipstick on the
> <content> pig, whereas we could instead try to create something non-pig-like.
Yes. In fact, we (Apple) would argue that we should implement the imperative
API first.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 1 March 2014 06:06:37 UTC