[css-multicol][css-page-floats] Figure out the interaction between column-span and page floats

[frivoal]

Having a page (column) float span multiple columns is a question that soon gets raised when you have both multi columns and page floats.

We need to figure out a sensible model for making that work, and propose it for inclusion in either the page-floats spec or the next level (2) of multi-col.

[johanneswilm]

Hey, I need to update the page float spec for other reasons, but I remember we removed the multi-column part from that spec because this made it overly complex. What's the reason for wanting to include again now?

…

On Fri, Dec 16, 2016 at 9:42 AM, Florian Rivoal ***@***.***> wrote: Having a page (column) float span multiple columns is a question that soon gets raised when you have both multi columns and page floats. We need to figure out a sensible model for making that work, and propose it for inclusion in either the page-floats spec or the next level (2) of multi-col. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#812>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkWOHmD5zSFzdK8XEpurwKjGCraq9ayks5rIk7ggaJpZM4LO9jB> .

-- Johannes Wilm http://www.johanneswilm.org tel: +1 (520) 399 8880

[frivoal]

Whether we should include it now is an separate question, but we need to address it eventually, so this issue is to track that need.

For now, it may be sufficient to make sure that whatever we're specifying is forward compatible with what we'll eventually want. That is a fuzzy thing, since what we eventually want isn't really defined, but we should probably think about it a bit still.

If it was in early version of the spec, do you have a link to the best / latest version to include it, to get a sense of what has already been proposed on this topic?

[johanneswilm]

On Tue, Dec 20, 2016 at 5:37 AM, Florian Rivoal ***@***.***> wrote: Whether we should include it *now* is an separate question, but we need to address it eventually, so this issue is to track that need.

Maybe. The thing is that if we want browsers to implement the spec, then we cannot ask for complexity that will let it take several minutes before the end user can see their webpage. If I recall correctly, I think we previiously said that page floats can in reality be replaced by a combination of Exclusions + absolute positioning + JavaScript, and that the provided page floats should therefore only be the simple kinds that browsers could provide natively.

For now, it may be sufficient to make sure that whatever we're specifying is forward compatible with what we'll eventually want. That is a fuzzy thing, since what we eventually want isn't really defined, but we should probably think about it a bit still. If it was in early version of the spec, do you have a link to the best / latest version to include it, to get a sense of what has already been proposed on this topic?

Håkon's Figure Spec: https://figures.spec.whatwg.org/#floating-inside-and-outside-pages

…

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <#812 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkWOMkn_qvzOyzJ1057z-ZyMUL5bokfks5rJ1uUgaJpZM4LO9jB> .

-- Johannes Wilm http://www.johanneswilm.org tel US: +1 (520) 399 8880 tel NO: +47 94109013 tel DE: +49 176 370 18082

[SebastianZ]

The title of this issue is still not correct. It should read "column floats".

Sebastian