A quick HTTPArchive search shows only 63 domains with "webkit-paged-(x|y)" in HTML or CSS (assuming I did that correctly). It seems like there might be some support for a version of -webkit-paged-x/y to be in the spec (https://github.com/rachelandrew/multicol-wip/issues/5), but as of 1/15/2018 there were very few domains using it.

cc-ing some of the the editors of CSS Multicol. Is this something that could possibly be added to the spec in the future, and so we should leave alone? Or do you think removal makes sense due to the very low usage numbers?

I am quite keen to see some kind of way to enable overflow in the Block dimension for web purposes. I think Florian mentions this in the linked thread too - and I actually had a conversation with Tab Atkins briefly at the Working Group meeting on the subject.

This would make multicol much more useful in a web context. Whether these properties are the way to do that I don't know, it's something I've only just begun thinking about . I'll raise it as a Level 2 issue though against the spec and see if we can get some feedback.

Works for me, I'll mark this as blocked on the spec work.

Do note that since there's such low usage of the existing feature, behavior/syntax could probably be changed without fear of web-incompatibility.

Hi There.

I intend to add a cleaner version of this in the future, either as a multicol specific thing, or as a generic fragmentation on block overflow mechanism, or maybe both.

Until then, I agree it is nice to keep this feature. As the linked thread shows, while few websites use it, it is of interest people writing ebook / EPUB readers apps, in order to emulate pagination.