Changes between Version 7 and Version 8 of Component Model


Ignore:
Timestamp:
Apr 29, 2011 2:07:13 PM (9 years ago)
Author:
Dimitri Glazkov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Component Model

    v7 v8  
    77,,If this is older than 30 days, it's probably out of date.,,
    88
    9 Use [http://dev.w3.org/2006/xbl2/ XBL2] spec as a reference:
     9|| Area || Status || Comments ||
     10|| [https://bugs.webkit.org/show_bug.cgi?id=48698 Convert all existing shadow DOM to new model] ||`input`/`textarea` remain|| ||
     11|| [https://bugs.webkit.org/show_bug.cgi?id=59802 Shadow Content Plumbing] || Basic plumbing in place || Instead of it being a `<template>` element clone, we use a different node type (SHADOW_ROOT_NODE = 14) for the root node ||
     12|| [https://bugs.webkit.org/show_bug.cgi?id=59803 DOM Interfaces] || Not yet implemented || Waiting on the plumbing to settle down ||
     13|| [https://bugs.webkit.org/show_bug.cgi?id=59804 Declarative API (Markup)] || Not yet implemented || Waiting on the plumbing to settle down ||
     14|| [https://bugs.webkit.org/show_bug.cgi?id=59805 Events] || Matches logic in [http://dev.w3.org/2006/xbl2/#event-handlers event handlers] section || We don't create a separate Event object for each re-targeting, because we don't worry about component isolation (yet) ||
     15|| [https://bugs.webkit.org/show_bug.cgi?id=59806 Lifecycle] || Not yet implemented || Built-in HTML elements implementation uses direct wiring ||
     16|| [https://bugs.webkit.org/show_bug.cgi?id=59807 Document/Resource Loading] || Not yet implemented || ||
     17|| [https://bugs.webkit.org/show_bug.cgi?id=59827 CSS matching] || Some of the [http://dev.w3.org/2006/xbl2/#selectors-and-shadow-scopes selectors and shadow scopes] implemented || Need to further align with the XBL2 spec ||
    1018
    11 || Area || Status || Comments ||
    12 || HTML Elements and DOM interfaces || Not yet implemented || Waiting on the plumbing to settle down ||
    13 || `pseudo` attribute || Same as [http://dev.w3.org/2006/xbl2/#the-pseudo-attribute XBL2 pseudo] || Allows arbitrary value and CSS machinery has been modified to allow any value ||
    14 || Component lifecycle || Not yet implemented || Native controls implementation uses direct wiring ||
    15 || Shadow DOM || Basic plumbing in place || Instead of it being a `<template>` element clone, we use a different node type (SHADOW_ROOT_NODE = 14) for the root node ||
    16 || Tree Scopes || Implemented, matches the [http://dev.w3.org/2006/xbl2/#shadow-scope shadow scope] notion of in XBL2 || ||
    17 || Inheritance || Won't be implementing || We decided that this feature is overly complex and unnecessary for the component model.  See [http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0941.html this post] to public-webapps  ||
    18 || `<content>` element || Basic building blocks are being used by `<summary>` and `<details>` || Need to better understand requirements and use cases to spec/implement properly. Certainly won't be implementing the way it's [http://dev.w3.org/2006/xbl2/#processing-content-elements defined] in XBL 2.0 ||
    19 || CSS matching || Some of the [http://dev.w3.org/2006/xbl2/#selectors-and-shadow-scopes selectors and shadow scopes] implemented || Need to further align with the XBL2 spec ||
    20 || Events || Matches logic in [http://dev.w3.org/2006/xbl2/#event-handlers event handlers] section || We don't create a separate Event object for each re-targeting, because we don't worry about component isolation (yet) ||
     19Current difference from the [http://dev.w3.org/2006/xbl2/ XBL2] spec:
     20
     21|| `pseudo` attribute || Same as [http://dev.w3.org/2006/xbl2/#the-pseudo-attribute XBL2 pseudo], but allows arbitrary value and CSS machinery has been modified to allow any value ||
     22|| Tree Scopes || Implemented, matches the [http://dev.w3.org/2006/xbl2/#shadow-scope shadow scope] notion of in XBL2 ||
     23|| Inheritance || Won't be implementing. This feature is overly complex and unnecessary for the component model.  See [http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0941.html this post] to public-webapps  ||
     24|| `<content>` element || Basic building blocks are being used by `<summary>` and `<details>`, Need to better understand requirements and use cases to spec/implement properly. Certainly won't be implementing the way it's [http://dev.w3.org/2006/xbl2/#processing-content-elements defined] in XBL 2.0 ||