Changes between Version 9 and Version 10 of Component Model

Timestamp:

Apr 29, 2011, 2:21:08 PM (14 years ago)

Author:

Dimitri Glazkov

Comment:

--

Component Model

@@ -19 +19 @@
 Current difference from the [http://dev.w3.org/2006/xbl2/ XBL2] spec:
 
-|| Shadow Root Element || Instead of it being a `<template>` element clone, we use a different node type (SHADOW_ROOT_NODE = 14) for the root node ||
-|| Event retargeting || We don't create a separate Event object for each re-targeting, because we don't worry about component isolation (yet)  ||
-|| `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 ||
-|| Tree Scopes || Implemented, matches the [http://dev.w3.org/2006/xbl2/#shadow-scope shadow scope] notion of in XBL2 ||
-|| 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  ||
-|| `<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 ||
+ * '''Shadow Root Element''' Instead of it being a `<template>` element clone, we use a different node type (SHADOW_ROOT_NODE = 14) for the root node.
+ * '''Event retargeting''' We don't create a separate Event object for each re-targeting, because we don't worry about component isolation (yet).
+ *  '''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.
+ * '''Tree Scopes''' Matches the [http://dev.w3.org/2006/xbl2/#shadow-scope shadow scope] notion of in XBL2, but is a more explicit abstraction.
+ * '''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.
+ * '''content element''' 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.