Skip to content

Commit 2e70ccf

Browse files
committed
[css2] Tantek's changes to explanation of background for canvas, as per Oslo ftf
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402151
1 parent 2080cc7 commit 2e70ccf

1 file changed

Lines changed: 6 additions & 28 deletions

File tree

css2/colors.src

Lines changed: 6 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22
<html lang="en">
3-
<!-- $Id: colors.src,v 2.34 2003-08-04 12:53:20 bbos Exp $ -->
3+
<!-- $Id: colors.src,v 2.35 2003-08-27 16:57:50 bbos Exp $ -->
44
<head>
55
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66
<title>Colors and backgrounds</title>
77
<meta name="editor" lang="tr" content="Tantek &Ccedil;elik">
8-
<!-- Changed by: Tantek Celik, 2003-07-29 -->
8+
<!-- Changed by: Tantek Celik, 2003-08-27 -->
99
<style type="text/css">
1010
.current,.proposed,span.delcurrent { background:#feb }
1111
ins.proposed,span.insproposed,p.insproposed { background:#bfb }
@@ -61,55 +61,33 @@ background will shine through by default because of the initial
6161
'transparent' value on <span
6262
class="propinst-background-color">'background-color'</span>.
6363
</p>
64-
<del class="current">
6564
<p>
66-
The background of the box generated by the root element covers the
67-
entire <a href="intro.html#canvas">canvas</a>,
68-
anchored at the same point as it would be if the root
69-
element were a block level element.
65+
The background of the root element becomes the background of the canvas and covers the entire <a href="intro.html#canvas">canvas</a>, anchored at the same point as it would be if it was painted only for the root element itself. The root element does not paint this background again.
7066
</p>
71-
</del>
72-
<ins class="proposed">
73-
<p>
74-
The background of the <a href="intro.html#canvas">canvas</a> covers the entire canvas and is the background of the root element, anchored at the same point as it would be if it was painted only for the root element itself. The root element does not paint this background again.
75-
</p>
76-
</ins>
7767

7868
<p>For HTML documents, however, we recommend that authors specify the
7969
background for the BODY element rather than the HTML element. User
8070
agents should observe the following precedence rules to fill in the
81-
background of the canvas <span class="insproposed">of HTML documents</span>:
71+
background of the canvas of HTML documents:
8272
if the value of the <span class="propinst-background">'background'</span> property for the HTML
8373
element is different from 'transparent' then use it, else use the
8474
value of the <span class="propinst-background">'background'</span>
8575
property for the BODY element. If the resulting value is
86-
'transparent', the rendering is undefined. <span class="delproposed">(</span>This does not apply to XHTML documents.<span class="delproposed">)</span>
76+
'transparent', the rendering is undefined. This does not apply to XHTML documents.
8777
</p>
8878
<div class="html-example"><p>
8979
According to these rules, the canvas underlying the following
9080
HTML document will have a "marble" background:
9181
</p>
9282
<pre>
9383
&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"&gt;
94-
<span class="delproposed">
95-
&lt;HTML&gt;
96-
&lt;HEAD&gt;
97-
</span>
9884
&lt;TITLE&gt;Setting the canvas background&lt;/TITLE&gt;
9985
&lt;STYLE type="text/css"&gt;
10086
BODY { background: url("http://example.com/marble.png") }
10187
&lt;/STYLE&gt;
102-
<span class="delproposed">
103-
&lt;/HEAD&gt;
104-
&lt;BODY&gt;
105-
</span>
10688
&lt;P&gt;My background is marble.
107-
<span class="delproposed">
108-
&lt;/BODY&gt;
109-
&lt;/HTML&gt;
110-
</span>
11189
</pre>
112-
<p class="insproposed">
90+
<p>
11391
Note that the rule for the BODY element will work even though the BODY tag has been omitted in the HTML source since the HTML parser will infer the missing tag.
11492
</p>
11593
</div>

0 commit comments

Comments
 (0)