- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Mar 2014 21:20:10 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24872 Daniel Freedman <dfreedm@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfreedm@google.com --- Comment #6 from Daniel Freedman <dfreedm@google.com> --- (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. > > Anyway that's the last I'll say on the subject to avoid derailing further; > we can continue discussing the imperative API in bug 18429. I think it would be very helpful for browser vendors to hear what reactions actual web developers are having with <content> that make them feel the need of an imperative API as a first draft. Could we have that conversation in 18429 as you suggested? Thanks! -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 6 March 2014 21:20:12 UTC