- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 23 May 2014 23:14:26 +0900
- To: Axel Dahmen <brille1@hotmail.com>
- Cc: public-webapps <public-webapps@w3.org>
On Tue, May 20, 2014 at 8:41 PM, Axel Dahmen <brille1@hotmail.com> wrote: > I got redirected here from a HTML5 discussion on an <IFrame>'s SEAMLESS > attribute: > > https://www.w3.org/Bugs/Public/show_bug.cgi?id=25376 > > Ian Hickson suggested to publish my findings here so the Web Components team > may consider to re-evaluate the draft and probably amending the spec. Could you post your findings here? Digging through the bug thread, it appears you might be talking about this: > Web Components require a plethora of additional browser features and behaviours. > > Web Components require loads of additional HTML, CSS and client script code for displaying content. > > Web Components install complex concepts (e.g. <decorators>) by introducing unique, complex, opaque behaviours, abandoning the pure nature of presentation. > > Web Components require special script event handling, so existing script code cannot be reused. > > Web Components require special CSS handling, so existing CSS cannot be reused. > > Web Components unnecessarily introduce a new clumsy “custom”, or “undefined” element, leaving the path of presentation. Custom Elements could as easy be achieved using CSS classes, and querySelector() in ECMA Script. > > The W3C DOM MutationObserver specification already provides functionality equivalent to insertedCallback()/readyCallback()/removeCallback(). Is this correct? Is this the full list of comments you wish to make? ~TJ
Received on Friday, 23 May 2014 14:15:17 UTC