Skip to content

Commit

Permalink
[] (0) <fieldset> and <br> rendering fixes (credit: ds); also, additi…
Browse files Browse the repository at this point in the history
…onal ack for previous checkin

git-svn-id: http://svn.whatwg.org/webapps@2964 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Apr 18, 2009
1 parent 2a027b7 commit a7ca049
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 2 deletions.
10 changes: 9 additions & 1 deletion index
Expand Up @@ -61229,7 +61229,10 @@ rt { display: ruby-text; }

<p>The <code><a href=#the-br-element>br</a></code> element is expected to render as if its
contents were a single U+000A LINE FEED (LF) character and its
'white-space' property was 'pre'.</p>
'white-space' property was 'pre'. User agents are expected to
support the 'clear' property on inline elements (in order to render
<code><a href=#the-br-element>br</a></code> elements with <code title=attr-br-clear>clear</code> attributes) in the manner
described in the non-normative note to this effect in CSS2.1.</p>

<p>The user agent is expected to hide <code><a href=#the-noscript-element>noscript</a></code> elements
for whom <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>,
Expand Down Expand Up @@ -62042,6 +62045,9 @@ fieldset {
padding: 0.35em 0.625em 0.75em;
}</pre>

<p>The <code><a href=#the-fieldset-element>fieldset</a></code> element is expected to establish a new
block formatting context.</p>

<p>The first <code><a href=#the-legend-element>legend</a></code> element child of a
<code><a href=#the-fieldset-element>fieldset</a></code> element, if any, is expected to be rendered
over the top border edge of the <code><a href=#the-fieldset-element>fieldset</a></code> element. If
Expand Down Expand Up @@ -63577,6 +63583,7 @@ interface <dfn id=timeouthandler>TimeoutHandler</dfn> {
Alexander J. Vincent,
Alexey Feldgendler,
&#1040;&#1083;&#1077;&#1082;&#1089;&#1077;&#1081; &#1055;&#1088;&#1086;&#1089;&#1082;&#1091;&#1088;&#1103;&#1082;&#1086;&#1074; (Alexey Proskuryakov),
Alexis Deveria,
Allan Clements,
Anders Carlsson,
Andreas<!-- mqmq87 -->,
Expand Down Expand Up @@ -63646,6 +63653,7 @@ interface <dfn id=timeouthandler>TimeoutHandler</dfn> {
Daniel Brumbaugh Keeney,
Daniel Glazman,
Daniel Peng,
Daniel Schattenkirchner,
Daniel Sp&aring;ng,
Daniel Steinberg,
Danny Sullivan,
Expand Down
11 changes: 10 additions & 1 deletion source
Expand Up @@ -71900,7 +71900,11 @@ rt { display: ruby-text; }

<p>The <code>br</code> element is expected to render as if its
contents were a single U+000A LINE FEED (LF) character and its
'white-space' property was 'pre'.</p>
'white-space' property was 'pre'. User agents are expected to
support the 'clear' property on inline elements (in order to render
<code>br</code> elements with <code
title="attr-br-clear">clear</code> attributes) in the manner
described in the non-normative note to this effect in CSS2.1.</p>

<p>The user agent is expected to hide <code>noscript</code> elements
for whom <span title="concept-n-script">scripting is enabled</span>,
Expand Down Expand Up @@ -72830,6 +72834,9 @@ fieldset {
padding: 0.35em 0.625em 0.75em;
}</pre>

<p>The <code>fieldset</code> element is expected to establish a new
block formatting context.</p>

<p>The first <code>legend</code> element child of a
<code>fieldset</code> element, if any, is expected to be rendered
over the top border edge of the <code>fieldset</code> element. If
Expand Down Expand Up @@ -74576,6 +74583,7 @@ interface <dfn>TimeoutHandler</dfn> {
Alexander J. Vincent,
Alexey Feldgendler,
&#1040;&#1083;&#1077;&#1082;&#1089;&#1077;&#1081; &#1055;&#1088;&#1086;&#1089;&#1082;&#1091;&#1088;&#1103;&#1082;&#1086;&#1074; (Alexey Proskuryakov),
Alexis Deveria,
Allan Clements,
Anders Carlsson,
Andreas<!-- mqmq87 -->,
Expand Down Expand Up @@ -74645,6 +74653,7 @@ interface <dfn>TimeoutHandler</dfn> {
Daniel Brumbaugh Keeney,
Daniel Glazman,
Daniel Peng,
Daniel Schattenkirchner,
Daniel Sp&aring;ng,
Daniel Steinberg,
Danny Sullivan,
Expand Down

0 comments on commit a7ca049

Please sign in to comment.