8000 [css-overflow] Rephrase and move issue · xfq/csswg-drafts@329656c · GitHub
Skip to content

Commit 329656c

Browse files
frivoalfrivoal
committed
[css-overflow] Rephrase and move issue
1 parent 436d09b commit 329656c

2 files changed

Lines changed: 16 additions & 15 deletions

File tree

‎css-overflow/Overview.bs‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -488,6 +488,11 @@ and extends it further.
488488
Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
489489
</pre>
490490

491+
Issue: The naming of this property and its values is preliminary.
492+
This was initially proposed as
493+
"fragmentation: auto | none | break | clone | page"
494+
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>,
495+
and there is not yet wide agreement as to which naming is better.
491496

492497
Note: ''continue: fragments'' replaces "overflow:fragments"
493498
from earlier versions of this specification,
@@ -549,11 +554,6 @@ The computed value of the 'continue' for a given element or pseudo element is de
549554
<li>In all other cases, the computed value is the specified value
550555
</ol>
551556

552-
Issue: The naming of this property and its values is preliminary.
553-
This was initially proposed as
554-
"fragmentation: auto | none | break | clone | page"
555-
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.
556-
557557
Issue: If we introduce a pseudo element that can select columns in a multicol,
558558
we would need to specify that next computes to next on it,
559559
or introduce a new value and have next compute to that

‎css-overflow/Overview.html‎

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1435,6 +1435,12 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
14351435
<td><abbr title="follows order of property value definition">per grammar</abbr></table>
14361436

14371437

1438+
<p class="issue" id="issue-b2c6e3da"><a class="self-link" href="#issue-b2c6e3da"></a>The naming of this property and its values is preliminary.
1439+
This was initially proposed as
1440+
"fragmentation: auto | none | break | clone | page"
1441+
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>,
1442+
and there is not yet wide agreement as to which naming is better.</p>
1443+
14381444

14391445
<p class="note" role="note">Note: <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> replaces "overflow:fragments"
14401446
from earlier versions of this specification,
@@ -1536,12 +1542,6 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
15361542
</ol>
15371543

15381544

1539-
<p class="issue" id="issue-77a336c3"><a class="self-link" href="#issue-77a336c3"></a>The naming of this property and its values is preliminary.
1540-
This was initially proposed as
1541-
"fragmentation: auto | none | break | clone | page"
1542-
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.</p>
1543-
1544-
15451545
<p class="issue" id="issue-598fb492"><a class="self-link" href="#issue-598fb492"></a>If we introduce a pseudo element that can select columns in a multicol,
15461546
we would need to specify that next computes to next on it,
15471547
or introduce a new value and have next compute to that
@@ -2752,13 +2752,14 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
27522752
despite that implementations have implemented
27532753
<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> instead?
27542754
<a href="#issue-52e2a181"> ↵ </a></div>
2755-
<div class="issue">When the element isn’t a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-break-3/#fragmentation-container">fragmentation container</a> already,
2756-
should this work by turning it directly into one,
2757-
or by creating a <a data-link-type="dfn" href="#fragment-box">fragment box</a> inside it like <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> does?<a href="#issue-36be54be"> ↵ </a></div>
27582755
<div class="issue">The naming of this property and its values is preliminary.
27592756
This was initially proposed as
27602757
"fragmentation: auto | none | break | clone | page"
2761-
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.<a href="#issue-77a336c3"> ↵ </a></div>
2758+
in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>,
2759+
and there is not yet wide agreement as to which naming is better.<a href="#issue-b2c6e3da"> ↵ </a></div>
2760+
<div class="issue">When the element isn’t a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-break-3/#fragmentation-container">fragmentation container</a> already,
2761+
should this work by turning it directly into one,
2762+
or by creating a <a data-link-type="dfn" href="#fragment-box">fragment box</a> inside it like <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> does?<a href="#issue-36be54be"> ↵ </a></div>
27622763
<div class="issue">If we introduce a pseudo element that can select columns in a multicol,
27632764
we would need to specify that next computes to next on it,
27642765
or introduce a new value and have next compute to that

0 commit comments

Comments
 (0)