[csswg-drafts] [css-multicol] Spanning elements late in the content, treated as column-span: none

rachelandrew has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-multicol] Spanning elements late in the content, treated as column-span: none ==
In the section for [column-span](https://drafts.csswg.org/css-multicol/#column-span) is the following text:

> "A spanning element takes up more space than the element would take up otherwise. When space is limited, it may be impossible to find room for the spanning element. In these cases, user agents may treat the element as if none had been specified on this property."

The current example 21 is a demonstration of the expected result. The only web UA currently rendering as per the example is Edge. [Example CodePen](https://codepen.io/rachelandrew/full/LdNPEg/). Chrome spans the element but ends up with a different rendering issue, I can't get the example to load in Safari.

I raised this as [Chromium issue 821760](https://bugs.chromium.org/p/chromium/issues/detail?id=821760), it was pointed out that the spec says "user agents _may_ treat the element as if none had been specified on the property", and there was not interest in implementing the feature.

In the interest of interoperability, I wanted to raise this for discussion. Is this a useful thing for multicol to be doing in this case? I'd be interested in @dbaron's thoughts on it



Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2448 using your GitHub account

Received on Friday, 16 March 2018 09:27:23 UTC