Re: [csswg-drafts] [css-inline][css-text-4] Allow padding to be applied at line start and end

The Working Group just discussed `line-start/end padding`, and agreed to the following resolutions:

* `RESOLVED: Add a line-padding property as described in minutes to text level 4.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: line-start/end padding<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/1973<br>
&lt;fantasai> leaverou, they're the first links in each issue<br>
&lt;dael> fantasai: This one is an issue where they want padding at start and end of line and applied to inner most element at that point.<br>
&lt;dael> fantasai: If ou have a span broken across 2 lines and at the end line padding is inserted into the span. With CSS you can wrap all the text but it gives you the last result. THis is effectively the opposite of letter spacing. This is outside the letter on the start and end.<br>
&lt;dael> fantasai: SHould be easy to impl, but we need syntax for it. I wanted to do this because it's easy to understand.<br>
&lt;dael> TabAtkins: Am I imagining a difference in the black line from hello and my?<br>
&lt;dael> fantasai: I think that's not intentional.<br>
&lt;dael> TabAtkins: Okay.<br>
&lt;dael> myles: If you have 2 nested do you use innermost<br>
&lt;dael> TabAtkins: It would be like letter spacing where one wins on the letter that ends the line.<br>
&lt;dael> florian: this inherits?<br>
&lt;dael> fantasai: I think that's simple.<br>
&lt;dael> TabAtkins: Has to. Letter spacing but for the space where we don't put letters.<br>
&lt;dael> myles: Recommendation is at the tie you do the line breaking you do this for the end of the line? Not sure how it works for beginning.<br>
&lt;dael> fantasai: You look at first character on your line and before you figure out how big the character is and like that you have to go forward a bit.<br>
&lt;fantasai> You take the line-padding value of that character<br>
&lt;dael> astearns: They use line padding as the avenue to control this.<br>
&lt;dael> fantasai: We could introduce a line-padding property that has a longhand.<br>
&lt;dael> florian: and if you're intrupted by a float?<br>
&lt;dael> fantasai: It's between you and the float.<br>
&lt;dael> dbaron: Are there interesting things with bidi?<br>
&lt;dael> fantasai: no.<br>
&lt;dael> dbaron: pre or post reordering<br>
&lt;dael> fantasai: post<br>
&lt;dael> myles: there's always a character at the end of the line. Whatever element that's part of is what you consult.<br>
&lt;dael> florian: If you're post-reorder you might get a different character at the end.<br>
&lt;dael> fantasai: Alternative is have this on the block. Whatever block makes the line box gets the value<br>
&lt;dael> Rossen: Similar to the box direction.<br>
&lt;dael> TabAtkins: Then you jsut shoot the line box.<br>
&lt;dael> TabAtkins: Possiblity is make it not inherit.<br>
&lt;TabAtkins> s/shoot/shrink/<br>
&lt;dael> fantasai: YOu want inherit because you mana anon boxes. BUt you can put it on the block container at which point it's applied.<br>
&lt;TabAtkins> s/mana/make/<br>
&lt;dael> florian: I think possibility of different padding based on bidi is not useful and complicates things quite a bit.<br>
&lt;dael> TabAtkins: This does seem better. NO drilling down and no bidi. I like this.<br>
&lt;dael> fantasai: The property is inherited by applies to block containers. When you do your layout you look at line padding property of the line box you're in which comes from the block container.<br>
&lt;dael> fantasai: I guess we're rsolved on that approach of having the property<br>
&lt;dael> astearns: Text level 4 again?<br>
&lt;dael> fantasai: Yeah. Other option is css Inline. Not sure where it fits better.<br>
&lt;dael> astearns: Prop: Add a line-padding property as described in minutes to text level 4.<br>
&lt;dael> RESOLVED: Add a line-padding property as described in minutes to text level 4.<br>
</details>


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

Received on Tuesday, 10 April 2018 14:52:45 UTC