Skip to content
Permalink
Browse files
[giow] (3) Be more explicit about viewport rendering sizes (rendered …
…and not)

Affected topics: Rendering

git-svn-id: http://svn.whatwg.org/webapps@8518 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Mar 1, 2014
1 parent 8cd88fc commit bd8c8af43bb76d0838e54c2809ec23fff7579659
Showing 3 changed files with 28 additions and 10 deletions.
@@ -298,7 +298,7 @@

<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 28 February 2014</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 1 March 2014</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -95508,7 +95508,12 @@ <h4 id=the-page><span class=secno>14.3.2 </span>The page</h4>
in which a page is rendered not as the author intended, possibly for the purposes of phishing or
otherwise misleading the user.</p>

<hr><p>If the <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, and the <a href=#browsing-context-container>browsing
<hr><p>If a <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, it is expected to be
positioned and sized to fit inside the content box of its <a href=#browsing-context-container>browsing context container</a>.
If a <a href=#browsing-context>browsing context</a> is not <a href=#being-rendered>being rendered</a>, it is expected to have a
viewport with zero width and zero height.</p>

<p>If the <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, and the <a href=#browsing-context-container>browsing
context container</a> of that <a href=#nested-browsing-context>nested browsing context</a> is a <code><a href=#frame>frame</a></code> or
<code><a href=#the-iframe-element>iframe</a></code> element, and that element has a <code title="">scrolling</code> attribute,
and that attribute's value is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">off</code>", "<code title="">noscroll</code>", or "<code title="">no</code>", then the
@@ -97722,8 +97727,9 @@ <h3 id=frames-and-framesets><span class=secno>14.6 </span>Frames and framesets</
<code>frame</code> element is rendered outside a <code>frameset</code>.)</p>
http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2722 - as of Jan 2014, Chrome did this, but Firefox did not
--><p>The contents of a <code><a href=#frame>frame</a></code> element that does not have a <code><a href=#frameset>frameset</a></code> parent
are expected to be rendered as transparent black (the <a href=#nested-browsing-context>nested browsing context</a> is not
shown in this case).</p>
are expected to be rendered as transparent black; the user agent is expected to not render the
<a href=#nested-browsing-context>nested browsing context</a> in this case, and that <a href=#nested-browsing-context>nested browsing context</a>
is expected to have a viewport with zero width and zero height.</p>

</div>

14 index
@@ -298,7 +298,7 @@

<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 28 February 2014</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 1 March 2014</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -95508,7 +95508,12 @@ html, body { display: block; }</pre>
in which a page is rendered not as the author intended, possibly for the purposes of phishing or
otherwise misleading the user.</p>

<hr><p>If the <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, and the <a href=#browsing-context-container>browsing
<hr><p>If a <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, it is expected to be
positioned and sized to fit inside the content box of its <a href=#browsing-context-container>browsing context container</a>.
If a <a href=#browsing-context>browsing context</a> is not <a href=#being-rendered>being rendered</a>, it is expected to have a
viewport with zero width and zero height.</p>

<p>If the <code><a href=#document>Document</a></code> is a <a href=#nested-browsing-context>nested browsing context</a>, and the <a href=#browsing-context-container>browsing
context container</a> of that <a href=#nested-browsing-context>nested browsing context</a> is a <code><a href=#frame>frame</a></code> or
<code><a href=#the-iframe-element>iframe</a></code> element, and that element has a <code title="">scrolling</code> attribute,
and that attribute's value is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">off</code>", "<code title="">noscroll</code>", or "<code title="">no</code>", then the
@@ -97722,8 +97727,9 @@ keygen { binding: <i title="">keygen</i>; }</pre>
<code>frame</code> element is rendered outside a <code>frameset</code>.)</p>
http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2722 - as of Jan 2014, Chrome did this, but Firefox did not
--><p>The contents of a <code><a href=#frame>frame</a></code> element that does not have a <code><a href=#frameset>frameset</a></code> parent
are expected to be rendered as transparent black (the <a href=#nested-browsing-context>nested browsing context</a> is not
shown in this case).</p>
are expected to be rendered as transparent black; the user agent is expected to not render the
<a href=#nested-browsing-context>nested browsing context</a> in this case, and that <a href=#nested-browsing-context>nested browsing context</a>
is expected to have a viewport with zero width and zero height.</p>

</div>

10 source
@@ -106548,6 +106548,11 @@ html, body { display: block; }</pre>

<hr>

<p>If a <code>Document</code> is a <span>nested browsing context</span>, it is expected to be
positioned and sized to fit inside the content box of its <span>browsing context container</span>.
If a <span>browsing context</span> is not <span>being rendered</span>, it is expected to have a
viewport with zero width and zero height.</p>

<p>If the <code>Document</code> is a <span>nested browsing context</span>, and the <span>browsing
context container</span> of that <span>nested browsing context</span> is a <code>frame</code> or
<code>iframe</code> element, and that element has a <code data-x="">scrolling</code> attribute,
@@ -108811,8 +108816,9 @@ keygen { binding: <i data-x="">keygen</i>; }</pre>
-->

<p>The contents of a <code>frame</code> element that does not have a <code>frameset</code> parent
are expected to be rendered as transparent black (the <span>nested browsing context</span> is not
shown in this case).</p>
are expected to be rendered as transparent black; the user agent is expected to not render the
<span>nested browsing context</span> in this case, and that <span>nested browsing context</span>
is expected to have a viewport with zero width and zero height.</p>

</div>

0 comments on commit bd8c8af

Please sign in to comment.