This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16898 - [Shadow]: Normative requirements
Summary: [Shadow]: Normative requirements
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17050
  Show dependency treegraph
 
Reported: 2012-05-01 17:41 UTC by Anne
Modified: 2012-05-14 22:52 UTC (History)
0 users

See Also:


Attachments

Description Anne 2012-05-01 17:41:06 UTC
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.
Comment 1 Dimitri Glazkov 2012-05-11 23:21:22 UTC
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.
Comment 2 Anne 2012-05-12 09:31:16 UTC
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.
Comment 3 Anne 2012-05-12 09:35:23 UTC
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.)
Comment 4 Dimitri Glazkov 2012-05-14 22:52:31 UTC
http://dvcs.w3.org/hg/webcomponents/rev/d6134e2e897e