Re: [csswg-drafts] [css-break-4] control space before element depending on page position

The CSS Working Group just discussed `fragmentation`, and agreed to the following:

* `RESOLVED: Add margin-break to break L4`

<details><summary>The full IRC log of that discussion</summary>
&lt;gregwhitworth> Topic: fragmentation<br>
&lt;gregwhitworth> fantasai: the suggested was to add a margin break property which controls how margin behaves at page breaks<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/253<br>
&lt;gregwhitworth> fantasai: if you have to start a new fragmentation then the margin after it is preserved, for example a new margin heading<br>
&lt;gregwhitworth> fantasai: if you're at an unforced break then it isn't preserved - this makes sense because margins are there to create space between things<br>
&lt;gregwhitworth> fantasai: so this would allow you to keep or discard<br>
&lt;gregwhitworth> fantasai: auto, keep, discard are proposed keywords in fragmentation L4<br>
&lt;gregwhitworth> fantasai: this is the only thing in that level<br>
&lt;gregwhitworth> florian: this property exists in the antenna house formatter<br>
&lt;gregwhitworth> Rossen: is there any discrepency on the type (columns, page, etc)<br>
&lt;gregwhitworth> fantasai: no they all behave the same<br>
&lt;gregwhitworth> jensimmons: I beleive this fixes one of the things that bugs me with multicolumn<br>
&lt;gregwhitworth> fantasai: we would have to be clear that it would occur with the different fragmentainers<br>
&lt;gregwhitworth> fantasai: there are different set of issues that are dealing with margins that aren't fragmented<br>
&lt;gregwhitworth> TabAtkins: would this apply to general BFC?<br>
&lt;jensimmons> rachelandrew: what’s the number of that bug?<br>
&lt;gregwhitworth> fantasai: no<br>
&lt;gregwhitworth> TabAtkins: to me that sounds like the thing that Jen just asked for<br>
&lt;rachelandrew> 1939<br>
&lt;gregwhitworth> fantasai: we need to determine if it works with the first fragmentainer or not<br>
&lt;jensimmons> This is the bug we need fixed. https://github.com/w3c/csswg-drafts/issues/1939<br>
&lt;florian> https://www.antennahouse.com/product/ahf60/docs/ahf-ext.html#axf.margin-break<br>
&lt;gregwhitworth> gregwhitworth: and it's the same 1:1 scenario?<br>
&lt;gregwhitworth> florian: yes<br>
&lt;gregwhitworth> TabAtkins: I'm curious why they only allow after margin<br>
&lt;gregwhitworth> fantasai: because the only option is keeping it because currently it's truncated<br>
&lt;fantasai> s/truncated/always truncated/<br>
&lt;TabAtkins> s/only allow/only allow an optional 'keep' for/<br>
&lt;gregwhitworth> Rossen: this propety, if we bring it forward to fragmentation 4...<br>
&lt;emilio> So, is `auto keep` a valid value? That sounds wrong<br>
&lt;gregwhitworth> fantasai: we could also put it in box 3 or 4, etc<br>
&lt;gregwhitworth> fantasai: there's little requested, this is currently the only thing<br>
&lt;gregwhitworth> Rossen: any other opinions about margin break?<br>
&lt;gregwhitworth> emilio: does it allow the auto keep value to be correct, because that's kind of weird<br>
&lt;gregwhitworth> florian: I recommend we open an issue on that<br>
&lt;gregwhitworth> emilio: sure<br>
&lt;gregwhitworth> jensimmons: I don't want to bikeshed the name, but is margin-break the right name?<br>
&lt;gregwhitworth> fantasai: we have margin-decoration-break as well so this carries that forward<br>
&lt;TabAtkins> AH behavior: https://github.com/w3c/csswg-drafts/issues/253#issuecomment-229367559<br>
&lt;gregwhitworth> iank_: this only applies to forced breaks?<br>
&lt;gregwhitworth> fantasai: this is expected to work on anything that has a margin<br>
&lt;gregwhitworth> Rossen: ok, I'm hearing people are in favor for break L4<br>
&lt;TabAtkins> auto=discard on unforced breaks, keep on forced or start-of-container; discard=discard on all breaks; keep=keep on all breaks<br>
&lt;gregwhitworth> Rossen: people can open issues against the proposal<br>
&lt;gregwhitworth> Rossen: Objections?<br>
&lt;gregwhitworth> RESOLVED: Add margin-break to break L4<br>
&lt;TabAtkins> end-side break is always discard right now, regardless of break type; option to specify "keep" for those too.<br>
&lt;TabAtkins> &lt;br dur=20min><br>
&lt;heycam> scribenick: heycam<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/253#issuecomment-431773588 using your GitHub account

Received on Monday, 22 October 2018 09:51:35 UTC