Skip to content

Commit a64eab5

Browse files
annevkannevk
committed
new abstract and sort out LinkStyle a bit
1 parent 2133853 commit a64eab5

2 files changed

Lines changed: 104 additions & 58 deletions

File tree

‎cssom/Overview.html‎

Lines changed: 60 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,14 @@
2929
<div class=head>
3030
<h1 id=cssom>Cascading Style Sheets Object Model (<abbr>CSSOM</abbr>)</h1>
3131

32-
<h2 class="no-num no-toc" id="">Editor's draft <!--W3C Working Draft--> 21
32+
<h2 class="no-num no-toc" id="">Editor's draft <!--W3C Working Draft--> 27
3333
January 2007</h2>
3434

3535
<dl>
3636
<dt>This version:
3737

3838
<dd><a
39-
href="http://www.w3.org/TR/2007/WD-cssom-20070121">http://www.w3.org/TR/2007/WD-cssom-20070121/</a>
39+
href="http://www.w3.org/TR/2007/WD-cssom-20070127">http://www.w3.org/TR/2007/WD-cssom-20070127/</a>
4040

4141
<dt>Latest version:
4242

@@ -57,12 +57,11 @@ <h2 class="no-num no-toc" id="">Editor's draft <!--W3C Working Draft--> 21
5757

5858
<h2 class="no-num no-toc" id=abstract>Abstract</h2>
5959

60-
<p>The Cascading Style Sheets Object Model defines the object model for
61-
<abbr title="Cascading Style Sheets">CSS</abbr> in order to be able to
62-
modify rules within the style sheets. It also defines ways for accessing
63-
style sheets associated with documents. In addition, this specification
64-
defines several ways for retrieving the dimensions of objects within a
65-
document.
60+
<p>The Cascading Style Sheets Object Model defines enables developers to
61+
find style sheets associated with a <code>Document</code>, to query and
62+
modify rules within a CSS style sheet (through an object model) and to
63+
find out layout related information from objects within a
64+
<code>Document</code>.
6665

6766
<h2 class="no-num no-toc" id=sotd>Status of this Document</h2>
6867

@@ -96,6 +95,16 @@ <h2 class="no-num no-toc" id=toc>Table of Contents</h2>
9695

9796
<li><a href="#the-linkstyle"><span class=secno>2.2. </span>The
9897
<code>LinkStyle</code> Interface</a>
98+
<ul class=toc>
99+
<li><a href="#requirements"><span class=secno>2.2.1.
100+
</span>Requirements on specifications</a>
101+
102+
<li><a href="#requirements0"><span class=secno>2.2.2.
103+
</span>Requirements on specific user agents</a>
104+
105+
<li><a href="#ltxml-stylesheet"><span class=secno>2.2.3.
106+
</span><code>&lt;?xml-stylesheet?></code> processing instruction</a>
107+
</ul>
99108

100109
<li><a href="#the-documentstyle"><span class=secno>2.3. </span>The
101110
<code>DocumentStyle</code> Interface</a>
@@ -460,28 +469,6 @@ <h3 id=the-linkstyle><span class=secno>2.2. </span>The <code><a
460469
class=ct>must</em> implement the <code><a
461470
href="#linkstyle">LinkStyle</a></code> interface.
462471

463-
<p>SVG UAs <em class=ct>must</em> implement <code><a
464-
href="#linkstyle">LinkStyle</a></code> on objects implementing the
465-
<code>SVGStyleElement</code> interface. HTML UAs <em class=ct>must</em>
466-
implement <code><a href="#linkstyle">LinkStyle</a></code> on objects
467-
implementing <code>HTMLLinkElement</code> or
468-
<code>HTMLStyleElement</code>. They <em class=ct>must</em> also implement
469-
it on objects implementing <code>HTMLMetaElement</code> if the
470-
<code>Link</code> HTTP header is supported. UAs supporting the
471-
<code>&lt;?xml-stylesheet?></code> processing instruction <em
472-
class=ct>must</em> implement <code><a
473-
href="#linkstyle">LinkStyle</a></code> on objects implementing
474-
<code>ProcessingInstruction</code>.
475-
476-
<p class=issue>Perhaps the above should be left to specifications defining
477-
those objects.
478-
479-
<p>Specifications introducing new ways of associating style sheets through
480-
the DOM <em class=ct>should</em> define which objects implement the
481-
<code><a href="#linkstyle">LinkStyle</a></code> interface. In addition,
482-
these specifications <em class=ct>should</em> define how these objects
483-
create a <code><a href="#stylesheet">StyleSheet</a></code> object.
484-
485472
<pre class=idl>interface <dfn id=linkstyle>LinkStyle</dfn> {
486473
readonly attribute <a href="#stylesheet">StyleSheet</a> <a href="#linkstyle-sheet" title=linkstyle-sheet>sheet</a>;
487474
};</pre>
@@ -501,6 +488,49 @@ <h3 id=the-linkstyle><span class=secno>2.2. </span>The <code><a
501488
<p class=note>Whether or not the node refers to a style sheet is defined by
502489
the specification the defines the semantics of said node.
503490

491+
<h4 id=requirements><span class=secno>2.2.1. </span>Requirements on
492+
specifications</h4>
493+
494+
<p>Specifications introducing new ways of associating style sheets through
495+
the DOM <em class=ct>should</em> define which objects implement the
496+
<code><a href="#linkstyle">LinkStyle</a></code> interface. In addition,
497+
these specifications <em class=ct>should</em> define how these objects
498+
create a <code><a href="#stylesheet">StyleSheet</a></code> object.
499+
500+
<h4 id=requirements0><span class=secno>2.2.2. </span>Requirements on
501+
specific user agents</h4>
502+
503+
<p>SVG user agents <em class=ct>must</em> implement <code><a
504+
href="#linkstyle">LinkStyle</a></code> on objects implementing the
505+
<code>SVGStyleElement</code> interface. HTML user agents <em
506+
class=ct>must</em> implement <code><a
507+
href="#linkstyle">LinkStyle</a></code> on objects implementing
508+
<code>HTMLLinkElement</code> or <code>HTMLStyleElement</code>. They <em
509+
class=ct>must</em> also implement it on objects implementing
510+
<code>HTMLMetaElement</code> if the <code>Link</code> HTTP header is
511+
supported.
512+
513+
<p class=issue>Perhaps the above should be left to specifications defining
514+
those objects.
515+
516+
<h4 id=ltxml-stylesheet><span class=secno>2.2.3.
517+
</span><code>&lt;?xml-stylesheet?></code> processing instruction</h4>
518+
519+
<p>User agents supporting supporting <code>ProcessingInstruction</code> <em
520+
class=ct>must</em> support the <code>&lt;?xml-stylesheet?></code>
521+
processing instruction. They must also implement the <code><a
522+
href="#linkstyle">LinkStyle</a></code> on objects implementing
523+
<code>ProcessingInstruction</code>.
524+
525+
<div class=issue>
526+
<p>This section needs to define how to obtain pseudo-attributes from a
527+
processing instruction. How to handle error handling. For instance, the
528+
first attribute declaration wins.</p>
529+
530+
<p>This needs to be done in generic terms so other specifications can
531+
reuse it.</p>
532+
</div>
533+
504534
<h3 id=the-documentstyle><span class=secno>2.3. </span>The <code><a
505535
href="#documentstyle">DocumentStyle</a></code> Interface</h3>
506536

‎cssom/Overview.src.html‎

Lines changed: 44 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -57,11 +57,10 @@ <h2 class="no-num no-toc" id="">Editor's draft <!--W3C Working Draft--> [DATE: 3
5757

5858
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
5959

60-
<p>The Cascading Style Sheets Object Model defines the object model for
61-
<abbr title="Cascading Style Sheets">CSS</abbr> in order to be able to modify
62-
rules within the style sheets. It also defines ways for accessing style sheets
63-
associated with documents. In addition, this specification defines several
64-
ways for retrieving the dimensions of objects within a document.</p>
60+
<p>The Cascading Style Sheets Object Model defines enables developers to find
61+
style sheets associated with a <code>Document</code>, to query and modify
62+
rules within a CSS style sheet (through an object model) and to find out
63+
layout related information from objects within a <code>Document</code>.</p>
6564

6665
<h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
6766

@@ -246,26 +245,6 @@ <h3>The <code>LinkStyle</code> Interface</h3>
246245
<p>Nodes within the DOM causing the association of a style sheet
247246
<em class="ct">must</em> implement the <code>LinkStyle</code> interface.</p>
248247

249-
<p>SVG UAs <em class="ct">must</em> implement <code>LinkStyle</code> on
250-
objects implementing the <code>SVGStyleElement</code> interface. HTML UAs
251-
<em class="ct">must</em> implement <code>LinkStyle</code> on
252-
objects implementing <code>HTMLLinkElement</code> or
253-
<code>HTMLStyleElement</code>. They <em class="ct">must</em> also implement
254-
it on objects implementing <code>HTMLMetaElement</code> if the
255-
<code>Link</code> HTTP header is supported. UAs supporting the
256-
<code>&lt;?xml-stylesheet?></code> processing instruction
257-
<em class="ct">must</em> implement <code>LinkStyle</code> on objects
258-
implementing <code>ProcessingInstruction</code>.</p>
259-
260-
<p class="issue">Perhaps the above should be left to specifications defining
261-
those objects.</p>
262-
263-
<p>Specifications introducing new ways of associating style sheets through
264-
the DOM <em class="ct">should</em> define which objects implement the
265-
<code>LinkStyle</code> interface. In addition, these specifications
266-
<em class="ct">should</em> define how these objects create a
267-
<code>StyleSheet</code> object.</p>
268-
269248
<pre class="idl">interface <dfn>LinkStyle</dfn> {
270249
readonly attribute <span>StyleSheet</span> <span title="linkstyle-sheet">sheet</span>;
271250
};</pre>
@@ -286,6 +265,43 @@ <h3>The <code>LinkStyle</code> Interface</h3>
286265
<p class="note">Whether or not the node refers to a style sheet is defined by
287266
the specification the defines the semantics of said node.</p>
288267

268+
<h4>Requirements on specifications</h4>
269+
270+
<p>Specifications introducing new ways of associating style sheets through
271+
the DOM <em class="ct">should</em> define which objects implement the
272+
<code>LinkStyle</code> interface. In addition, these specifications
273+
<em class="ct">should</em> define how these objects create a
274+
<code>StyleSheet</code> object.</p>
275+
276+
<h4>Requirements on specific user agents</h4>
277+
278+
<p>SVG user agents <em class="ct">must</em> implement <code>LinkStyle</code>
279+
on objects implementing the <code>SVGStyleElement</code> interface. HTML user
280+
agents <em class="ct">must</em> implement <code>LinkStyle</code> on objects
281+
implementing <code>HTMLLinkElement</code> or <code>HTMLStyleElement</code>.
282+
They <em class="ct">must</em> also implement it on objects implementing
283+
<code>HTMLMetaElement</code> if the <code>Link</code> HTTP header is
284+
supported.</p>
285+
286+
<p class="issue">Perhaps the above should be left to specifications defining
287+
those objects.</p>
288+
289+
<h4><code>&lt;?xml-stylesheet?></code> processing instruction</h4>
290+
291+
<p>User agents supporting supporting <code>ProcessingInstruction</code>
292+
<em class="ct">must</em> support the <code>&lt;?xml-stylesheet?></code>
293+
processing instruction. They must also implement the <code>LinkStyle</code> on
294+
objects implementing <code>ProcessingInstruction</code>.</p>
295+
296+
<div class="issue">
297+
<p>This section needs to define how to obtain pseudo-attributes from a
298+
processing instruction. How to handle error handling. For instance, the first
299+
attribute declaration wins.</p>
300+
301+
<p>This needs to be done in generic terms so other specifications can reuse
302+
it.</p>
303+
</div>
304+
289305
<h3>The <code>DocumentStyle</code> Interface</h3>
290306

291307
<p>Any object implementing the <code>Document</code> interface
@@ -858,9 +874,9 @@ <h3>The <code>CSSStyleSheet</code> Interface</h3>
858874
method</dt>
859875

860876
<dd>This method <em class="ct">must</em> raise a <code>INDEX_SIZE_ERR</code>
861-
exception if the given <var>index</var> does not correspond to a rule in the
862-
style sheet. Otherwise, it <em class="ct">must</em> remove the rule at
863-
<var>index</var>.</dd>
877+
exception if the given <var>index</var> does not correspond to a rule in the
878+
style sheet. Otherwise, it <em class="ct">must</em> remove the rule at
879+
<var>index</var>.</dd>
864880

865881
</dl>
866882

0 commit comments

Comments
 (0)