W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

Re: [csswg-drafts] [css-cascade][css-pseudo] How does 'inherit' keyword behave in a child of ::first-line?

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 May 2017 16:15:51 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-302141798-1495037750-sysbot+gh@w3.org>
The CSS Working Group just discussed `How does 'inherit' keyword behave in a child of ::first-line?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: How does 'inherit' keyword behave in a child of ::first-line?<br>
&lt;dael> github topic: https://github.com/w3c/csswg-drafts/issues/1097#issuecomment-300553985<br>
&lt;dael> fremy: We added this last week and people needed more time to review.<br>
&lt;dael> fremy: Did people review?<br>
&lt;dael> Florian: I did not.<br>
&lt;dael> astearns: Looks like you added the summary which is great.<br>
&lt;dael> astearns: Is it just Florian that needs to look?<br>
&lt;TabAtkins> I haven't reviewed it, but now that Elika and I have thought more about ::first-line this week, we should be able to understand it better now.<br>
&lt;dael> Florian: I don't think so. Reason I need to look is to see if it will scale to similar pseudos. That's forward looking. For now someone else needs to check.<br>
&lt;dael> fantasai: I think...I was looking at proposal with that in mind. There's parts to the proposal.<br>
&lt;dael> fantasai: The part that says if you inherit non-inheritied you go directly to parent is fine.<br>
&lt;dael> fantasai: There was some discussion I didn't follow about how first-line is text inside a span inside a first line...it didn't make sense. Text inside a span should inherit from a span and text inside a first-line inherits from first-line.<br>
&lt;dael> fantasai: There was something about how a unstyled firs-tline should act like the first line isn't htere.<br>
&lt;dael> fantasai: There were three inveriants we need to preserve for things to work in the same way.<br>
&lt;tantek> present=<br>
&lt;dael> fantasai: One part of proposal was about variables and I don't have a strong opinion on that. THere was concern about setting display via a variable but has same problem if you set not via a variable<br>
&lt;dael> fantasai: I'm not sure variable behavior in there is necessarily what we want, but at this point in time it doesn't much matter. It's a q for as we extend in the future. We might want variables ot work more like normal inherited then.<br>
&lt;dael> fremy: Reason we didn't want variables to work is because first-line is more special then fragment. THere is condition that you need to be inline to be first-line. We didn't want to spend too much time figuring this out.<br>
&lt;dael> Florian: From birds eye view it seemed sane. Id idn't review details.<br>
&lt;dael> fantasai: I suggest we go one by one for the proposal<br>
&lt;dael> astearns: Do we want to continue on GH?<br>
&lt;dael> fantasai: I'm okay either way. I wand dbaron opinion on this.<br>
&lt;dael> astearns: and dbaron can't be on so I suggest...this transcript will go into the issue. We can refine in GH and resolve next week.<br>
&lt;dael> fantasai: sounds good.<br>
&lt;dael> astearns: fremy?<br>
&lt;dael> fremy: Yes. It just should be done at some point.<br>
&lt;dael> astearns: Yeah. There's a few things to hammer out. Getting dbaron next week. Please @ him on the issue if he's not there.<br>
&lt;dael> fremy: He's in the issue.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1097#issuecomment-302141798 using your GitHub account
Received on Wednesday, 17 May 2017 16:15:58 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC