url: http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style; type: property; text: overflow-style; url: http://dev.w3.org/csswg/selectors-3/#subject; type: dfn; text: subject; +url: http://dev.w3.org/csswg/css-containment/#propdef-contain; type: property; text: contain +url: http://dev.w3.org/csswg/css-containment/#paint-containment; type: dfn; text: paint containment+ @@ -308,7 +239,7 @@
body element to the viewport
+ from the body element to the viewport
if the value on the root element is visible.
The visible value when used for the viewport
must be interpreted as auto.
@@ -963,7 +906,7 @@ import examples from [CSS3-BOX].
+import examples from [CSS3-BOX].
The naming of this property and its values is preliminary. +
The naming of this property and its values is preliminary. This was initially proposed as "fragmentation: auto | none | break | clone | page" in https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html, and there is not yet wide agreement as to which naming is better.
-This property is meant to generalize and replace region-fragment. +
This property is meant to generalize and replace region-fragment. Once it is sufficiently stable in this specification, region-fragment should be removed from the regions specification in favor of this.
@@ -1079,7 +1022,7 @@When the element isn’t a fragmentation container already, should this work by turning it directly into one, or by creating a fragment box inside it like fragments does?
@@ -1148,7 +1091,7 @@If we introduce a pseudo element that can select columns in a multicol, we would need to specify that auto computes to auto on it, or introduce a new value and have auto compute to that (but what would that value compute to on things that aren’t columns?).
@@ -1165,10 +1108,10 @@Pages should be possible to style with @page rules. How does that work for nested pages?
+Pages should be possible to style with @page rules. How does that work for nested pages?
@media (overflow-block: paged), (overflow-block: optional-paged) {
- :root {
- continue: paginate;
- }
-}
-@media (overflow-block: paged), (overflow-block: optional-paged) {
+ :root {
+ continue: paginate;
+ }
+}Traditional pagination (e.g. when printing) assumes that +
Traditional pagination (e.g. when printing) assumes that :root is contained in the page box, rather than having the page box be a pseudo element child of :root. Can we work around that using something similar to fragment boxes? Or maybe by having a fragment box (reproducing :root) inside a page box inside :root?
-How does the page box model work when it is a child of a regular css box?
+How does the page box model work when it is a child of a regular css box?
-The initial proposal in [CSS3GCPM] and implemantation from Opera +
The initial proposal in [CSS3GCPM] and implemantation from Opera used 4 values instead of paginate: "paged-x | paged-y | paged-x-controls | paged-y-controls". Should this property also include these values, @@ -1203,13 +1145,13 @@
Ability to display N pages at once +
Ability to display N pages at once rather than just one page at once? Could this be a value of "pagination-layout", such as: "pagination-layout: horizontal 2;"
-Brad Kemper has proposed a model for combining pagination and +
Brad Kemper has proposed a model for combining pagination and fragment overflow, which also deals with displaying multiple pages. http://www.w3.org/mid/FF1704C5-D5C1-4D6F-A99D-0DD094036685@gmail.com
@@ -1514,15 +1456,15 @@Specifying other values of display, position, or float is permitted, but is not allowed to change - the computed value of display-inside. + the computed value of display-inside. (Since continue only applies to block containers, flex containers, and grid containers - the computed value of display-inside is always - block, flex, or - grid. + the computed value of display-inside is always + block, flex, or + grid. Need to specify exactly how this works, but it depends on - having display-inside and display-outside specified. + having display-inside and display-outside specified.
@@ -1550,7 +1492,7 @@This inheritance rule allows specifying styles indirectly (by using explicit inherit or using default inheritance - on properties that don’t apply to ::first-letter) + on properties that don’t apply to ::first-letter) that can’t be specified directly (based on the rules in the next section). This is a problem. @@ -1610,14 +1552,14 @@
having max-lines do nothing on regular elements is not ideal. +
having max-lines do nothing on regular elements is not ideal. When applied to non fragmentainers, it should probably cause continue to compute to discard so that you only need to reach for one property rather than 2 to get @@ -2136,14 +2078,6 @@
@media (overflow-block: paged), (overflow-block: optional-paged) {
- :root {
- continue: paginate;
- }
-}
-@media (overflow-block: paged), (overflow-block: optional-paged) {
+ :root {
+ continue: paginate;
+ }
+}