- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jun 2019 20:54:36 +0000
- To: public-css-archive@w3.org
A few points I'd like to highlight from the discussion in the teleconference yesterday: * @frivoal raised the issue that changing this as I initially proposed would be inconsistent with the behavior of print formatters * #3224 was originally resolving an issue where today's browsers behave differently (Gecko on one side, Blink and WebKit (and EdgeHTML) on the other side), but we weren't aware (I think) of compatibility problems caused by that difference * my concern in this issue was inconsistency between formatting of multicol on screen and when printed; users printing from web browsers expect the printing to produce something generally similar to what they see on screen (and the developers often haven't considered or tested printing behavior). My underlying principle is that the last fragment in a paginated context should behave like the behavior in a continuous context; this is particularly important because the *last* fragment is often the *only* fragment, and it is bad for something that is not actually fragmented to behave in a substantially different way on paper. So the option that seemed the most attractive in the teleconference was to revert the change in #3224 and ask Blink and WebKit to to change their behavior. At the same time... we should probably also clarify what the `height: auto` behavior is in this case. What do browsers do, and what do print formatters do? (I think reverting the decision also avoids having to figure out which cases where the height is influenced by the flex or grid algorithms count as a constrained height and which ones don't.) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4036#issuecomment-506507437 using your GitHub account
Received on Thursday, 27 June 2019 20:54:37 UTC