You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -2610,13 +2616,14 @@ <h2>Page and column floats</h2>
2610
2616
2611
2617
<p>The optional keyword value specifies where the element is floated: top, bottom, or the nearest of the two. The initial value is 'near'.
2612
2618
2619
+
<p>An element is considered to be a float if it has a snap() value, even if the element does not appear within the specified distance. This way, it can be determined whether an element is float or not without laying out the document.
2620
+
2613
2621
<dt>snap
2614
2622
2615
2623
<dd>same as <tt>snap(2em, near)</tt>
2616
2624
2617
2625
</dl>
2618
2626
2619
-
2620
2627
<divclass=example>
2621
2628
<p>In this example, tables will snap to the top/bottom if the top/bottom of the border box is closer than '3em' from the top/bottom of the page/column.
2622
2629
@@ -2630,7 +2637,6 @@ <h2>Page and column floats</h2>
2630
2637
2631
2638
<pclass=issue>Should we define a reasonable default (say, 3em) instead of relying on implementation-specific values?
2632
2639
<pclass=issue>Do numberic values (in addition to length values) make sense, like for orphans/widows
2633
-
<pclass=issue>is an element with a snap() value considered to be a float? only when it really floats, or always?
2634
2640
2635
2641
2636
2642
<!--
@@ -3611,6 +3617,16 @@ <h2>Selecting lines</h2>
3611
3617
</pre>
3612
3618
</div>
3613
3619
3620
+
<h2>Conditional text</h2>
3621
+
3622
+
<divclass=example>
3623
+
<pre>
3624
+
a:target-layout(attr(href url), same-page) { content: " on this page" }
3625
+
a:target-layout(attr(href url), next-page) { content: " on the next page" }
3626
+
a:target-layout(attr(href url), previous-page) { content: " on the previous page" }
0 commit comments