Skip to content

Commit

Permalink
[giow] (1) Make non-modal <dialog>s use the regular containing block,…
Browse files Browse the repository at this point in the history
… since they're not on the top layer.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=20418
Affected topics: CSS, DOM APIs, HTML

git-svn-id: http://svn.whatwg.org/webapps@8448 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 30, 2014
1 parent 45d3296 commit f4404b0
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 18 deletions.
11 changes: 5 additions & 6 deletions complete.html
Expand Up @@ -52189,8 +52189,10 @@ <h4 id=the-dialog-element><span class=secno>4.11.7 </span>The <dfn><code>dialog<
initialized to be empty.</p>

<p>When an element is added to the <a href=#pending-dialog-stack>pending dialog stack</a>, it must also be added to the
<a href=#top-layer>top layer</a> layer. When an element is removed from the <a href=#pending-dialog-stack>pending dialog
stack</a>, it must be removed from the <a href=#top-layer>top layer</a>. <a href=#refsFULLSCREEN>[FULLSCREEN]</a></p>
<a href=#top-layer>top layer</a> layer and its containing block must be the initial containing block. When
an element is removed from the <a href=#pending-dialog-stack>pending dialog stack</a>, it must be removed from the
<a href=#top-layer>top layer</a>, and its containing block must revert to that given by the regular
containing block rules as defined by CSS. <a href=#refsFULLSCREEN>[FULLSCREEN]</a> <a href=#refsCSS>[CSS]</a></p>

<p>When the <dfn id=dom-dialog-showmodal title=dom-dialog-showModal><code>showModal()</code></dfn> method is invoked,
the user agent must run the following steps:</p>
Expand Down Expand Up @@ -52297,10 +52299,7 @@ <h4 id=the-dialog-element><span class=secno>4.11.7 </span>The <dfn><code>dialog<

<p class=note>An example of such a UI mechanism would be the user pressing the "Escape" key.</p>

<hr><p>The containing block of all <code><a href=#the-dialog-element>dialog</a></code> elements that are <i>absolutely positioned</i>
must be the initial containing block.</p>

<p>All <code><a href=#the-dialog-element>dialog</a></code> elements are always in one of two modes: <dfn id=mundanely-aligned>mundanely aligned</dfn>,
<hr><p>All <code><a href=#the-dialog-element>dialog</a></code> elements are always in one of two modes: <dfn id=mundanely-aligned>mundanely aligned</dfn>,
or <dfn id=magically-aligned>magically aligned</dfn>. When a <code><a href=#the-dialog-element>dialog</a></code> element is created, it must be placed
in the <a href=#mundanely-aligned>mundanely aligned</a> mode and the user agent must <a href=#set-up-the-default-static-position>set up the default static
position</a> for that element, without an anchor.</p>
Expand Down
11 changes: 5 additions & 6 deletions index
Expand Up @@ -52189,8 +52189,10 @@ dictionary <dfn id=relatedeventinit>RelatedEventInit</dfn> : <a href=#eventinit>
initialized to be empty.</p>

<p>When an element is added to the <a href=#pending-dialog-stack>pending dialog stack</a>, it must also be added to the
<a href=#top-layer>top layer</a> layer. When an element is removed from the <a href=#pending-dialog-stack>pending dialog
stack</a>, it must be removed from the <a href=#top-layer>top layer</a>. <a href=#refsFULLSCREEN>[FULLSCREEN]</a></p>
<a href=#top-layer>top layer</a> layer and its containing block must be the initial containing block. When
an element is removed from the <a href=#pending-dialog-stack>pending dialog stack</a>, it must be removed from the
<a href=#top-layer>top layer</a>, and its containing block must revert to that given by the regular
containing block rules as defined by CSS. <a href=#refsFULLSCREEN>[FULLSCREEN]</a> <a href=#refsCSS>[CSS]</a></p>

<p>When the <dfn id=dom-dialog-showmodal title=dom-dialog-showModal><code>showModal()</code></dfn> method is invoked,
the user agent must run the following steps:</p>
Expand Down Expand Up @@ -52297,10 +52299,7 @@ dictionary <dfn id=relatedeventinit>RelatedEventInit</dfn> : <a href=#eventinit>

<p class=note>An example of such a UI mechanism would be the user pressing the "Escape" key.</p>

<hr><p>The containing block of all <code><a href=#the-dialog-element>dialog</a></code> elements that are <i>absolutely positioned</i>
must be the initial containing block.</p>

<p>All <code><a href=#the-dialog-element>dialog</a></code> elements are always in one of two modes: <dfn id=mundanely-aligned>mundanely aligned</dfn>,
<hr><p>All <code><a href=#the-dialog-element>dialog</a></code> elements are always in one of two modes: <dfn id=mundanely-aligned>mundanely aligned</dfn>,
or <dfn id=magically-aligned>magically aligned</dfn>. When a <code><a href=#the-dialog-element>dialog</a></code> element is created, it must be placed
in the <a href=#mundanely-aligned>mundanely aligned</a> mode and the user agent must <a href=#set-up-the-default-static-position>set up the default static
position</a> for that element, without an anchor.</p>
Expand Down
11 changes: 5 additions & 6 deletions source
Expand Up @@ -57699,9 +57699,11 @@ dictionary <dfn>RelatedEventInit</dfn> : <span>EventInit</span> {
initialized to be empty.</p>

<p>When an element is added to the <span>pending dialog stack</span>, it must also be added to the
<span>top layer</span> layer. When an element is removed from the <span>pending dialog
stack</span>, it must be removed from the <span>top layer</span>. <a
href="#refsFULLSCREEN">[FULLSCREEN]</a></p>
<span>top layer</span> layer and its containing block must be the initial containing block. When
an element is removed from the <span>pending dialog stack</span>, it must be removed from the
<span>top layer</span>, and its containing block must revert to that given by the regular
containing block rules as defined by CSS. <a href="#refsFULLSCREEN">[FULLSCREEN]</a> <a
href="#refsCSS">[CSS]</a></p>

<p>When the <dfn data-x="dom-dialog-showModal"><code>showModal()</code></dfn> method is invoked,
the user agent must run the following steps:</p>
Expand Down Expand Up @@ -57840,9 +57842,6 @@ dictionary <dfn>RelatedEventInit</dfn> : <span>EventInit</span> {

<hr>

<p>The containing block of all <code>dialog</code> elements that are <i>absolutely positioned</i>
must be the initial containing block.</p>

<p>All <code>dialog</code> elements are always in one of two modes: <dfn>mundanely aligned</dfn>,
or <dfn>magically aligned</dfn>. When a <code>dialog</code> element is created, it must be placed
in the <span>mundanely aligned</span> mode and the user agent must <span>set up the default static
Expand Down

0 comments on commit f4404b0

Please sign in to comment.