1.1 --- a/css-overflow/Overview.bs Tue Mar 03 21:51:56 2015 -0800
1.2 +++ b/css-overflow/Overview.bs Tue Feb 24 14:42:29 2015 +0900
1.3 @@ -380,7 +380,7 @@
1.4
1.5 <pre class=propdef>
1.6 Name: overflow-x, overflow-y
1.7 - Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto'' | ''paged-x'' | ''paged-y'' | ''paged-x-controls'' | ''paged-y-controls'' | ''fragments''
1.8 + Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto''
1.9 Initial: ''visible''
1.10 Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
1.11 Inherited: no
1.12 @@ -399,7 +399,7 @@
1.13
1.14 <pre class=propdef>
1.15 Name: overflow
1.16 - Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto'' | ''paged-x'' | ''paged-y'' | ''paged-x-controls'' | ''paged-y-controls'' | ''fragments''
1.17 + Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto''
1.18 Initial: see individual properties
1.19 Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
1.20 Inherited: no
1.21 @@ -410,6 +410,24 @@
1.22 Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
1.23 </pre>
1.24
1.25 + <div id="overflow-computed-values">
1.26 + <p>The computed values of 'overflow-x' and 'overflow-y'
1.27 + are determined from the cascaded values [[!CSS3CASCADE]]
1.28 + based on the following rules:</p>
1.29 +
1.30 + <ol>
1.31 + <li>
1.32 + If one cascaded values is ''overflow/visible''
1.33 + and the other is not,
1.34 + then computed values are the cascaded values
1.35 + with ''overflow/visible'' changed to ''overflow/auto''.
1.36 + </li>
1.37 + <li>
1.38 + Otherwise, the computed values are as specified.
1.39 + </li>
1.40 + </ol>
1.41 + </div>
1.42 +
1.43 <p>The values of these properties are:</p>
1.44
1.45 <dl dfn-for="overflow" dfn-type="value">
1.46 @@ -422,10 +440,41 @@
1.47 <dt><dfn>scroll</dfn>
1.48 <dt><dfn>auto</dfn>
1.49 <dd>
1.50 - These values are collectively the <dfn dfn>scrolling values</dfn>;
1.51 - they are defined in the section on
1.52 - <a href="#scrolling-overflow">scrolling and hidden overflow</a>.
1.53 + <p class="issue">
1.54 + Move material from [[CSS21]] and [[CSS3BOX]] here.
1.55 + </p>
1.56 </dd>
1.57 + </dl>
1.58 +
1.59 + <p class="issue">
1.60 + Explain which directions allow scrolling and which don't,
1.61 + as a function of 'direction'
1.62 + (including propagation of 'direction' to the ICB).
1.63 + </p>
1.64 +
1.65 +
1.66 + <p class="issue">
1.67 + [[CSS3-MARQUEE]] describes an 'overflow-style' property,
1.68 + but it has not picked up implementation experience
1.69 + that the working group is aware of.
1.70 + Should this document treat 'overflow-style' as a defunct proposal,
1.71 + or should this document describe the 'overflow-style' property
1.72 + and attempt to revive it,
1.73 + despite that implementations have implemented
1.74 + 'overflow-x' and 'overflow-y' instead?
1.75 + </p>
1.76 +
1.77 +<h2 id="fragmentation-properties">Fragmentation properties</h2>
1.78 +
1.79 +Issue: This section is a WIP, and currently just holds bits of information that need to be massaged into proper form.
1.80 +
1.81 + | ''paged-x'' | ''paged-y'' | ''paged-x-controls'' | ''paged-y-controls'' | ''fragments''
1.82 +
1.83 + <p class="issue">
1.84 + Are all 4 of the ''paged-*'' values really needed?
1.85 + </p>
1.86 +
1.87 + <dl>
1.88 <dt><dfn>paged-x</dfn>
1.89 <dt><dfn>paged-y</dfn>
1.90 <dt><dfn>paged-x-controls</dfn>
1.91 @@ -439,77 +488,10 @@
1.92 </dd>
1.93 </dl>
1.94
1.95 - <div id="overflow-computed-values">
1.96 - <p>The computed values of 'overflow-x' and 'overflow-y'
1.97 - are determined from the cascaded values [[!CSS3CASCADE]]
1.98 - based on the following rules:</p>
1.99 + <div class="issue">
1.100 + Having split the overflow and fragmentation properties, this issue is no longer relevant, but there are
1.101 + useful bits of information in the thread, so I am leaving it here for now.
1.102
1.103 - <ol>
1.104 - <li>
1.105 - If one or both of the cascaded values are
1.106 - <a>fragmenting values</a>, then:
1.107 - <ol>
1.108 - <li>
1.109 - If one of the cascaded values is one of the
1.110 - <a>fragmenting values</a>
1.111 - and the other is not,
1.112 - then the computed values are
1.113 - the same as the cascaded values.
1.114 - </li>
1.115 - <li>
1.116 - If both of the cascaded values are <a>fragmenting values</a>, then:
1.117 - <ol>
1.118 - <li>
1.119 - for horizontal writing mode [[!CSS3-WRITING-MODES]],
1.120 - the computed value for 'overflow-y' is the cascaded value
1.121 - and the computed value for 'overflow-x' is ''overflow/hidden'', or
1.122 - </li>
1.123 - <li>
1.124 - for vertical writing mode [[!CSS3-WRITING-MODES]],
1.125 - the computed value for 'overflow-x' is the cascaded value
1.126 - and the computed value for 'overflow-y' is ''overflow/hidden''.
1.127 - </li>
1.128 - </ol>
1.129 - </li>
1.130 - </ol>
1.131 - </li>
1.132 - <li>
1.133 - Otherwise, if one cascaded values is
1.134 - one of the <a>scrolling values</a>
1.135 - and the other is ''overflow/visible'',
1.136 - then computed values are the cascaded values
1.137 - with ''overflow/visible'' changed to ''overflow/auto''.
1.138 - </li>
1.139 - <li>
1.140 - Otherwise, the computed values are as specified.
1.141 - </li>
1.142 - </ol>
1.143 - </div>
1.144 -
1.145 - <p class="issue">
1.146 - Are all 4 of the ''paged-*'' values really needed?
1.147 - </p>
1.148 -
1.149 - <p>
1.150 - When the <a>fragmenting values</a> are used,
1.151 - the overflow from the fragments themselves
1.152 - treats the fragmenting value as ''overflow/hidden''.
1.153 - <span class="issue">Is this the right behavior?</span>
1.154 - <span class="issue">Give example.</span>
1.155 - </p>
1.156 -
1.157 - <p class="issue">
1.158 - [[CSS3-MARQUEE]] describes an 'overflow-style' property,
1.159 - but it has not picked up implementation experience
1.160 - that the working group is aware of.
1.161 - Should this document treat 'overflow-style' as a defunct proposal,
1.162 - or should this document describe the 'overflow-style' property
1.163 - and attempt to revive it,
1.164 - despite that implementations have implemented
1.165 - 'overflow-x' and 'overflow-y' instead?
1.166 - </p>
1.167 -
1.168 - <p class="issue">
1.169 There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
1.170 about how overflow, overflow-style, overflow-x and overflow-y
1.171 should work and interact with each other.
1.172 @@ -517,19 +499,8 @@
1.173 it is not completely clear which of these
1.174 should be used for
1.175 paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
1.176 - </p>
1.177 + </div>
1.178
1.179 -<h2 id="scrolling-overflow">Scrolling and hidden overflow</h2>
1.180 -
1.181 - <p class="issue">
1.182 - Move material from [[CSS21]] and [[CSS3BOX]] here.
1.183 - </p>
1.184 -
1.185 - <p class="issue">
1.186 - Explain which directions allow scrolling and which don't,
1.187 - as a function of 'direction'
1.188 - (including propagation of 'direction' to the ICB).
1.189 - </p>
1.190
1.191 <h2 id="paginated-overflow">Paginated overflow</h2>
1.192
