16898 2012-05-01 17:41:06 +0000 [Shadow]: Normative requirements 2012-05-14 22:52:31 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 17050 1 annevk dglazkov public-webapps-bugzilla oldest_to_newest 67219 0 annevk 2012-05-01 17:41:06 +0000 The ShadowRoot constructor has no must-level requirements and the same goes for other parts of the specification. Look at e.g. DOM/XMLHttpRequest/HTML for ideas on how to address this. 67626 1 dglazkov 2012-05-11 23:21:22 +0000 http://dvcs.w3.org/hg/webcomponents/rev/822d9cdf8db8, what do you think of constructor changes? It looks like I need to make each attribute/method a sub-section and specify what happens on invokation/getting/setting. I'll do that next. 67631 2 annevk 2012-05-12 09:31:16 +0000 I don't think they necessarily need to be a subsection. That was done for XMLHttpRequest because the descriptions are rather elaborate, but whether that's the best division is not entirely clear to me. 67632 3 annevk 2012-05-12 09:35:23 +0000 The new constructor text looks okay, although parameters are typically marked up as <var>, not <code>, and using a <dl>/<table> structure to define something as simple as this seems wrong. (In most specifications a constructor/method/attribute is defined as a <p>/<ol> structure preceded by a <dl class=domintro> box.) 67699 4 dglazkov 2012-05-14 22:52:31 +0000 http://dvcs.w3.org/hg/webcomponents/rev/d6134e2e897e