W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

[csswg-drafts] [css-page-floats] Snap to nearest edge

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Tue, 18 Apr 2017 05:58:17 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-222310416-1492495096-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-page-floats] Snap to nearest edge ==
There is a common requirements for page (or column) floats that cannot be achieved with the current spec, but could be with a minor tweak.

Authors often want a figure to be floated either to the top or the bottom of the page, whichever is nearest.

This could be achieved by amending the definition of snap-block() as follow:

> If `near` is in effect and the element is within the specified distance both from the `start` and the `end`, <del>`end`</del><ins>the nearest edge</ins> wins. <ins>In case the distance to the `start` and `end` edges is equal, the `end` edge wins.</ins>

Also, for convenience, and to prevent authors from needing to write `snap-block(9999px, near)` or other arbitrarily large values just to make sure both edges are within the specified distance, we suggest that the definition of `snap-block` (without parentheses) is changed to mean `snap-block( infinity, near)` instead of `snap-block(2em, near)`

The same changes should be done to `snap-inline`.


Note: regardless of whether we fix that or not, we need a precise definition of how to measure that distance. I'll file a separate issue for that.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1233 using your GitHub account
Received on Tuesday, 18 April 2017 05:58:23 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:11 UTC