Changes between Version 4 and Version 5 of Component Model


Ignore:
Timestamp:
Apr 24, 2011 11:37:55 AM (13 years ago)
Author:
Dimitri Glazkov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Component Model

    v4 v5  
    77,,If this is older than 30 days, it's probably out of date.,,
    88
    9 At this point, no author-facing APIs are exposed.
     9Use [http://dev.w3.org/2006/xbl2/ XBL2] spec as a reference:
    1010
    11 Differences and similarities with [http://dev.w3.org/2006/xbl2/ XBL2]:
    12 
    13 || Area || Status || Differences ||
     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[http://dev.w3.org/2006/xbl2/#processing-content-elements defined] in XBL 2.0 ||
     19|| `<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
     20|| 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 ||
    1421|| 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 || Shadow Root || We now create a root object at which the shadow DOM subtree begins || Instead of it being a `<template>` element clone, we use a different node type (SHADOW_ROOT_NODE = 14) ||
    16 || `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 ||
    17 || 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 ||
    18 || Tree Scopes || Implemented, matches the [http://dev.w3.org/2006/xbl2/#shadow-scope shadow scope] notion of in XBL2 || ||
    19 || Style blocks/script blocks || Not yet implemented || ||
    20 || 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  ||
    21 || `<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 ||