- From: <bugzilla@jessica.w3.org>
- Date: Sun, 23 Nov 2014 19:00:47 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27401 --- Comment #4 from Dimitri Glazkov (afk until Dec 1, 2014) <dglazkov@chromium.org> --- (In reply to Olli Pettay from comment #3) > (In reply to Dimitri Glazkov (afk until Dec 1, 2014) from comment #2) > > > > For example, the question "when should I put things in Shadow DOM?" is a > > > > symptom of approaching the problem from the wrong angle. > > > Why? > > > > See the rest of that sentence, it meant to all work together :) > It still doesn't say why > 'the question "when should I put things in Shadow DOM?" is a > symptom of approaching the problem from the wrong angle' Let me try this way: the answer to this question is not specific to Shadow DOM, it's a general OOP question. Thus, the angle of looking at it as feature-specific practices is wrong. > > > Yes! This is effectively what Shadow DOM and custom elements do today. The > > custom elements are the insertion points. > But why the need for shadow DOM then? Why the need for making the platform > much more complicated when > something simpler might have been enough. (if we didn't have shadow DOM, we > wouldn't have to modify event dispatch, nor go through > all the spec and their use of is-in-document etc.) I disagree. Having gone over this exercise many times in the last few years, I am convinced that we have the right solution shape. We do need to make sure we give developers the ability to opt in/out with some features. That's what this bug is about. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 23 November 2014 19:00:49 UTC