Options:
- # Session Start: Wed Nov 26 00:00:00 2014
- # Session Ident: #css
- # [00:10] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [00:21] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [00:26] * Joins: adenilson (~anonymous@public.cloak)
- # [00:29] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [00:39] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [00:56] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [01:10] * Joins: ArronEi (~ArronEi@public.cloak)
- # [01:14] * Quits: liam (liam@public.cloak) (Client closed connection)
- # [01:22] * Joins: jdaggett (~jdaggett@public.cloak)
- # [01:27] * Quits: thinkxl (~thinkxl@public.cloak) (Ping timeout: 180 seconds)
- # [01:30] <plinss> TabAtkins: not sure which krit means, but I’ve been improving the spec parser’s handling of SVG1 and picked up a bunch more dfn types. At one point it was too agressive and had a bunch of duplicates. Should be good now.
- # [01:47] * Joins: adenilson (~anonymous@public.cloak)
- # [01:57] * Joins: zcorpan (~zcorpan@public.cloak)
- # [02:28] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [02:49] * Quits: ArronEi (~ArronEi@public.cloak) (Ping timeout: 180 seconds)
- # [03:07] * Joins: ArronEi (~ArronEi@public.cloak)
- # [03:11] * Joins: Florian (~Florian@public.cloak)
- # [03:18] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [03:39] * Quits: dbaron (~dbaron@public.cloak) (Ping timeout: 180 seconds)
- # [03:51] * Joins: liam (liam@public.cloak)
- # [03:56] * Quits: liam (liam@public.cloak) (Client closed connection)
- # [03:58] * Joins: liam (liam@public.cloak)
- # [04:04] * Joins: thinkxl (~thinkxl@public.cloak)
- # [04:19] * Joins: tantek (~tantek@public.cloak)
- # [04:42] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [04:46] * Quits: ArronEi (~ArronEi@public.cloak) (Ping timeout: 180 seconds)
- # [04:48] * Quits: dauwhe_ (~dauwhe@public.cloak) ("")
- # [05:39] * Joins: thinkxl_ (~thinkxl@public.cloak)
- # [05:39] * Quits: thinkxl (~thinkxl@public.cloak) (Client closed connection)
- # [06:30] * Quits: glenn (~gadams@public.cloak) (Client closed connection)
- # [06:34] * Joins: thinkxl__ (~thinkxl@public.cloak)
- # [06:34] * Quits: thinkxl_ (~thinkxl@public.cloak) (Client closed connection)
- # [06:51] * Joins: dbaron (~dbaron@public.cloak)
- # [06:52] * Quits: thinkxl__ (~thinkxl@public.cloak) (Client closed connection)
- # [06:52] * Joins: thinkxl___ (~thinkxl@public.cloak)
- # [07:13] * Joins: thinkxl____ (~thinkxl@public.cloak)
- # [07:17] * Quits: thinkxl___ (~thinkxl@public.cloak) (Ping timeout: 180 seconds)
- # [08:15] * Joins: thinkxl_____ (~thinkxl@public.cloak)
- # [08:21] * Quits: thinkxl____ (~thinkxl@public.cloak) (Ping timeout: 180 seconds)
- # [08:21] * Quits: thinkxl_____ (~thinkxl@public.cloak) (Client closed connection)
- # [08:35] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [08:42] * Joins: glazou (~glazou@public.cloak)
- # [08:43] * Joins: jdaggett (~jdaggett@public.cloak)
- # [09:12] * Quits: glazou (~glazou@public.cloak) (Client closed connection)
- # [09:12] * Joins: glazou (~glazou@public.cloak)
- # [09:12] * Quits: glazou (~glazou@public.cloak) (Client closed connection)
- # [09:12] * Joins: glazou (~glazou@public.cloak)
- # [09:25] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [09:25] * Joins: zcorpan (~zcorpan@public.cloak)
- # [09:31] * Joins: svillar (~sergio@public.cloak)
- # [09:44] * Joins: antonp (~Thunderbird@public.cloak)
- # [10:02] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [10:22] * Quits: dbaron (~dbaron@public.cloak) (Ping timeout: 180 seconds)
- # [10:34] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [10:42] * Quits: svillar (~sergio@public.cloak) (Ping timeout: 180 seconds)
- # [10:45] * Quits: Ms2ger (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # [11:03] * Joins: lajava (~javi@public.cloak)
- # [11:08] * Joins: Florian (~Florian@public.cloak)
- # [11:31] * Joins: svillar (~sergio@public.cloak)
- # [11:56] * Joins: svillar_ (~sergio@public.cloak)
- # [12:01] * Quits: svillar (~sergio@public.cloak) (Ping timeout: 180 seconds)
- # [12:12] * Quits: darktears (~darktears@public.cloak) (Client closed connection)
- # [12:14] * Joins: darktears (~darktears@public.cloak)
- # [12:53] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [12:57] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [13:33] * Joins: svillar__ (~sergio@public.cloak)
- # [13:34] * Joins: zcorpan (~zcorpan@public.cloak)
- # [13:36] * Quits: svillar_ (~sergio@public.cloak) (Ping timeout: 180 seconds)
- # [13:39] <Florian> Any writing mode expert online? (fantasai, koji ...)
- # [13:40] <zcorpan> do we expect any other group to meet in Sydney the same week we have the css meeting?
- # [13:41] <Florian> I think there was svg as well, but I am not 100% sure
- # [13:42] <Florian> 'cursor: auto' should give a 'text' cursor over horizontal text, and a 'vertical-text' cursor over vertical text. What is the right terminology to hook from for normative text?
- # [13:43] <Florian> computed value of the writing mode property? something else?
- # [13:43] <Florian> 'writing mode' as a properly defined term?
- # [13:43] <Florian> (does that take TCY into account?)
- # [13:45] <ed> zcorpan: yes, svg is scheduled to meet in sydney the same week, and there's some overlap for fx topics
- # [13:52] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [13:53] <SimonSapin_> Florian: http://dev.w3.org/csswg/css-writing-modes/#horizontal-writing-mode is a proper definition (and same for vertical), but it doesn’t account for TCY
- # [13:54] * Joins: jdaggett (~jdaggett@public.cloak)
- # [13:56] <Florian> SimonSapin: Yes, that's my impression
- # [13:57] * Joins: zcorpan (~zcorpan@public.cloak)
- # [14:00] * Joins: plh (plehegar@public.cloak)
- # [14:01] * Quits: plh (plehegar@public.cloak) ("Leaving")
- # [14:03] * Joins: plh (plehegar@public.cloak)
- # [14:11] * Quits: Ms2ger (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # [14:14] * Quits: darktears (~darktears@public.cloak) (Client closed connection)
- # [14:15] * SimonSapin_ is now known as SimonSapin
- # [14:15] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [14:20] * Quits: svillar__ (~sergio@public.cloak) (Ping timeout: 180 seconds)
- # [14:41] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [14:45] * Joins: zcorpan (~zcorpan@public.cloak)
- # [14:47] * Joins: svillar__ (~sergio@public.cloak)
- # [15:01] * Joins: glenn (~gadams@public.cloak)
- # [15:21] * Joins: darktears (~darktears@public.cloak)
- # [15:25] * Joins: dauwhe (~dauwhe@public.cloak)
- # [15:31] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [15:35] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [15:55] * Joins: tantek (~tantek@public.cloak)
- # [15:55] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [16:24] * Joins: tantek (~tantek@public.cloak)
- # [16:25] * Joins: thinkxl (~thinkxl@public.cloak)
- # [16:39] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [16:53] * Quits: darktears (~darktears@public.cloak) (Ping timeout: 180 seconds)
- # [17:01] * Joins: darktears (~darktears@public.cloak)
- # [17:07] * Joins: murakami (~murakami@public.cloak)
- # [17:10] * Quits: glazou (~glazou@public.cloak) (glazou)
- # [17:24] * Quits: Ms2ger (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # [17:31] * Quits: bkardell_ (~uid10373@public.cloak) ("Connection closed for inactivity")
- # [17:39] * Joins: glazou (~glazou@public.cloak)
- # [17:39] * Quits: glazou (~glazou@public.cloak) (glazou)
- # [17:39] * Joins: glazou (~glazou@public.cloak)
- # [17:39] * glazou changes topic to 'logs: http://krijnhoetmer.nl/irc-logs/css/ - 2014-11-26 telcon agenda: http://lists.w3.org/Archives/Public/www-style/2014Nov/0528.html'
- # [17:39] * Joins: Zakim (zakim@public.cloak)
- # [17:39] <glazou> Zakim, this will be Style
- # [17:39] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 21 minutes
- # [17:39] <glazou> RRSAgent, make logs public
- # [17:39] <RRSAgent> I have made the request, glazou
- # [17:39] * Quits: svillar__ (~sergio@public.cloak) (Ping timeout: 180 seconds)
- # [17:41] * Joins: tantek (~tantek@public.cloak)
- # [17:42] * Quits: dwim (~dwim@public.cloak) (Client closed connection)
- # [17:43] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [17:43] * Quits: kangil (~kangil@public.cloak) (Client closed connection)
- # [17:43] * Joins: dwim (~dwim@public.cloak)
- # [17:43] * Joins: kangil (~kangil@public.cloak)
- # [17:49] * Joins: dbaron (~dbaron@public.cloak)
- # [17:52] <glazou> hi dwim
- # [17:54] <glazou> Zakim, code?
- # [17:54] <Zakim> the conference code is 78953 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), glazou
- # [17:56] <Zakim> Style_CSS FP()12:00PM has now started
- # [17:56] <Zakim> +Florian
- # [17:56] * Joins: BradK (~bradk@public.cloak)
- # [17:56] * Joins: dael (~dael@public.cloak)
- # [17:57] <Zakim> +glazou
- # [17:57] * Joins: gregwhitworth (~gregwhitworth@public.cloak)
- # [17:57] <Zakim> +dael
- # [17:57] <dael> ScribeNick: dael
- # [17:58] * Joins: antenna (~antenna@public.cloak)
- # [17:58] * Joins: alex_antennahouse (~458c94ae@public.cloak)
- # [17:58] * Joins: tantek (~tantek@public.cloak)
- # [17:58] <Zakim> +dauwhe
- # [17:59] <Zakim> +gregwhitworth
- # [17:59] * Joins: MaRakow (~MaRakow@public.cloak)
- # [17:59] <Zakim> +BradK
- # [17:59] <Zakim> + +1.631.398.aaaa
- # [17:59] <antenna> that's me 631.398.aaaa no mic
- # [18:00] <Zakim> +??P7
- # [18:00] <tantek> zakim, ??p7 is me
- # [18:00] <Zakim> +tantek; got it
- # [18:00] <glazou> Zakim, aaaa is antenna
- # [18:00] <Zakim> +antenna; got it
- # [18:00] <antenna> <-- angelo @antenna
- # [18:00] <tantek> zakim, angelo is in antenna
- # [18:00] <Zakim> +angelo; got it
- # [18:01] <Zakim> +[Bloomberg]
- # [18:01] <Zakim> + +1.206.992.aabb
- # [18:01] <Zakim> +plinss
- # [18:01] <MaRakow> zakim, aabb is me
- # [18:01] <Zakim> +MaRakow; got it
- # [18:02] * Joins: andreyr (~andreyr@public.cloak)
- # [18:02] <Zakim> +dbaron
- # [18:02] * krit “This passcode is not valid”… hm
- # [18:02] <Zakim> +krit
- # [18:02] <Zakim> +[IPcaller]
- # [18:03] * krit calling in again helped :P
- # [18:03] <Zakim> +TabAtkins
- # [18:03] <Zakim> +astearns
- # [18:03] * dbaron has that happen nearly half the time, but not today
- # [18:03] * Joins: adenilson (~anonymous@public.cloak)
- # [18:03] <fantasai> Zakim, IPCaller is me
- # [18:03] <Zakim> +fantasai; got it
- # [18:04] <Zakim> +??P17
- # [18:04] <Zakim> +[IPcaller]
- # [18:04] * fantasai :)
- # [18:04] <SimonSapin> Zakim, ??P17 is me
- # [18:04] <Zakim> +SimonSapin; got it
- # [18:04] <alex_antennahouse> I'm 2nd ipcaller I think
- # [18:04] <SimonSapin> Hi
- # [18:04] <dael> glazou: I saw a few additions from Florian.
- # [18:04] <dael> Florian: Yep.
- # [18:04] <tantek> Zakim, [IPcaller] is alex_antennahouse
- # [18:04] <Zakim> +alex_antennahouse; got it
- # [18:05] <dael> glazou: Let me get them on my screen. Since we have tantek and Florian we can start there. Are there other extra beyond what Florian sent?
- # [18:05] <dael> Topic: New WD for CSS Transforms
- # [18:05] <Zakim> +??P19
- # [18:05] <dael> TabAtkins: I'm all for it.
- # [18:05] <dael> dauwhe: Sure.
- # [18:05] <dbaron> +1
- # [18:05] <dauwhe> s/dauwhe/???/
- # [18:05] <tantek> +1
- # [18:05] <adenilson> Zakim, ?P19 is me.
- # [18:05] <Zakim> sorry, adenilson, I do not recognize a party named '?P19'
- # [18:05] <Florian> s/???/florian/
- # [18:05] <andreyr> +1
- # [18:05] <dael> krit: Are the obj since we discussed transform styles at the last f2f. We still have issues in the spec. I shouldn't be a huge issue, but people may want to wait. I'd like a new WD to reflect the changes we have.
- # [18:05] <adenilson> Zakim, ??P19 is me.
- # [18:05] <Zakim> +adenilson; got it
- # [18:06] <dael> MaRakow: I'm still concerned about the implications of some changes, but I haven't gotten a chance to look at it
- # [18:06] <dael> fantasai: Do you want to reiew and publish next week?
- # [18:06] <dael> MaRakow: I'd prefer that.
- # [18:06] <Zakim> +[Microsoft]
- # [18:06] <dael> glazou: So any comments becides MaRakow?
- # [18:06] * Joins: Rossen_ (~Rossen@public.cloak)
- # [18:07] <dael> action everyone review for next week
- # [18:07] * trackbot is creating a new ACTION.
- # [18:07] <trackbot> Error finding 'everyone'. You can review and register nicknames at <http://www.w3.org/Style/CSS/Tracker/users>.
- # [18:07] <Rossen_> zakim, microsoft has me
- # [18:07] <Zakim> +Rossen_; got it
- # [18:07] <dael> Topic: Fixed position creating a new stacking context.
- # [18:07] <glazou> http://lists.w3.org/Archives/Public/www-style/2014Nov/0384.html
- # [18:07] <Zakim> +SteveZ
- # [18:08] <dael> gregwhitworth: You can see the link in the agenda. 2 years ago Rossen_ and I talked and we were going to make the change and see if we got egergious issues. We're going to go ahead and make the switch so our enterprise customers will say if there's problems. It would be good to get a resolution.
- # [18:08] <dael> ??: You want a resolution first?
- # [18:08] <dbaron> s/??/Florian/
- # [18:08] <Zakim> + +1.415.231.aacc
- # [18:08] <koji> zakim, +1.415.231.aacc is me
- # [18:08] <Zakim> +koji; got it
- # [18:08] * Joins: SteveZ (~SteveZ@public.cloak)
- # [18:08] <dael> Rossen_: We'll flight the solution...It would be good to discuss and see what the area is where we want to be. We don't want to go back and forth between stacking context and not. It's hard to gauge what blinkand webkit intend to do.
- # [18:09] <dael> TabAtkins: I haven't been able to talk to the implementor, but I suspect we want to have it. I think maybe Jacob Rossi...one of our impl said it makes it easier. I have to check the thread.
- # [18:09] <dael> glazou: smfr sent a message just recently saying webkit has no plan to change in the forseeable future.
- # [18:09] <dbaron> I'd be hesitant to agree firmly to change the spec before you've done the experiment, but I'm fine with you doing the experiment and seeing how it goes, with the idea that we'll change the spec if it goes well.
- # [18:10] <dael> gregwhitworth: I think us flighting will help the discussion. Webkit and blink might not get bugs but we may. We'll flight it and we can come back, I want to get the discussion going. It would be good to look back once we get it tested and get a full solution.
- # [18:10] <dael> gregwhitworth: Does gecko have opinions?
- # [18:11] <dael> dbaron: I just wrote I'm hesitant to agree to change the spec pre-expirament, but I think you should do the experiment and we'll cahnge if it works. We want to know if it's a compat improvement to do it.
- # [18:11] <dael> gregwhitworth: Sounds good.
- # [18:11] <dael> glazou: Anything else on this? Is it done?
- # [18:11] <dael> astearns: gregwhitworth you're talking about changing so the first ex is a blue sq?
- # [18:11] <astearns> s/astearns/tantek/
- # [18:11] <dael> gregwhitworth: Yep. It would create a stacking context essentially.
- # [18:11] <dael> glazou: Can we move on?
- # [18:12] <dael> group: yes.
- # [18:12] <dael> glazou: I suggest we do item 3 before moving on to CSS3 UI
- # [18:12] <dael> Topic: extend :matches() to pseudo elements
- # [18:12] <dael> glazou: This created a long discussion because someone from webkit already implemented. Before we discuss the mobile, I'd like to understand why we would do it.
- # [18:13] <dael> TabAtkins: The use case is like that of matches, but withouth the :matches pseudo it's hard to do. So like with out spec style sheets I can use matches, but I have to repeat it for the before and after.
- # [18:13] <Zakim> + +1.519.208.aadd
- # [18:13] * Joins: vollick (~vollick@public.cloak)
- # [18:14] <dael> fantasai: I think it's effectively a syntatic element. You can write the selectors in such a way that it should work. There's not reason not to make it a pseduo element, but we have to be careful to make sure th syntatic constraints are there fore short hand as well as long hand.
- # [18:14] <dael> fantasai: TabAtkins you were having trouble writing it, it should be hard we can do that together.
- # [18:14] <fantasai> s/a syntactic element/syntactic sugar/
- # [18:14] <dael> glazou: Any other opinions? Everyone okay with extending?
- # [18:14] <dael> TabAtkins: Or having the functionality in some form.
- # [18:14] <fantasai> s/write the selectors/write the selectors longhand/
- # [18:14] <dael> dbaron: I'd want to catch up and see the proposal, but it sounds reasonable.
- # [18:15] <dael> glazou: Okay than.
- # [18:15] <SimonSapin> +1 with what fantasai said, keep the same constraints as when written the long form
- # [18:15] <fantasai> s/writing it/speccing it/
- # [18:15] <dael> RESOLVED: extend :matches() to pseudo-elements
- # [18:15] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [18:15] <dael> glazou: We have two other things on selectors.
- # [18:16] <tantek> let's keep going with selectors
- # [18:16] <dael> Florian: 2 of the things I have are selectors related
- # [18:16] <dael> Topic: specificity of :matches() inside :not()
- # [18:16] <fantasai> s/in such a way/to be equivalent in such a way/
- # [18:16] <glazou> http://lists.w3.org/Archives/Public/www-style/2014Oct/0530.html
- # [18:16] <fantasai> s/should work/should work exactly the same/
- # [18:16] <fantasai> s/make it/make it accept/
- # [18:16] <dael> glazou: So Benjamin asked about this and he has a weird explination. The two definitions colide and it's hard to understand what to do
- # [18:17] <dael> TabAtkins: THe definitnion of matches talks about which sleector matches. If you nest inside a not he's aguaing that none of them match so you can't get any specificity. And wrapping two nots does something really weird with specificity.
- # [18:17] <dael> TabAtkins: So he says when this happens, pretend it's the most specific one.
- # [18:17] <dael> dbaron: This sounds right to me.
- # [18:17] <tantek> this sounds like a good spec clarification
- # [18:17] <dael> fantasai: Also me. It's making :matches() behave like the longhand which is how it should be.
- # [18:18] <SimonSapin> +1 for most specific
- # [18:18] <dael> TabAtkins: Using :matches() like the e0mails doesn't add anything. For continuity, even if you nest inside the large sleector inside a :not we should act similarly.
- # [18:18] <dael> RESOLVED: The specifictiy of a :matches inside a :not is the specificity of the most specific
- # [18:18] <dael> glazou: Can one of the editors replyo n the list?
- # [18:18] <dael> TabAtkins: Yes.
- # [18:19] <dael> glazou: There's the last one, that's Florian. We can go as you wish.
- # [18:19] <dael> Topic: :has() focus
- # [18:19] <dbaron> where's Florian's long list of stuff?
- # [18:19] <Florian> http://lists.w3.org/Archives/Public/www-style/2014Nov/0271.html
- # [18:19] * Joins: SteveZ_ (~SteveZ@public.cloak)
- # [18:20] <dael> Florian: The :hover and :active pseudo match on more them themselves, they also attach to other things and piece shadow. The :fcosu pseudo doesn't do this and we prob can't change for backwards compat.
- # [18:20] <dael> Florian: It would be useful so I suggested a new :has-focus which would propigate through ancestors.
- # [18:20] <fantasai> I think we also don't want to change that, since you want to know exactly what's in focus
- # [18:21] <dael> Florian: There's fairly obvious use cases, if you have a form and want to highlight it you can't do it without JS right now. Same thing if you want to go through a shadow-DOM. Since we can't change focus, I suggest introducing this.
- # [18:21] <dael> fantasai: I think we don't want to change :focus.
- # [18:21] <dael> Florian: We can't, but we want something that does the same with the extention.
- # [18:22] <dael> fantasai: I think there's reasons why you'd want to go up the ancestors and reasons why you wouldn't. I think it's a good idea to add this because it handles a lot of use cases.
- # [18:22] <dael> Florian: Also some people suggested we didn't need it because it was handled by :has, but it doesn't piece shadow barriars unless you specifically make it do so.
- # [18:22] <dael> TabAtkins: Agreed.
- # [18:23] <dael> fantasai: I think :hasfocus, I'm not sure about the label propigation, I'd prefer that via :focus, but if this is an ancestor foa focus eleemnt it matches.
- # [18:23] <Zakim> +vivien
- # [18:23] <dael> Florian: Opening the possibility for the host language to match is appropriate, but if it should do the same is a slightly different conversation. Opening the possiblity is appropraite and we can leave :focus as is since it's got a long history of baskwards compat.
- # [18:23] * Quits: SteveZ (~SteveZ@public.cloak) (Ping timeout: 180 seconds)
- # [18:24] * Bert excuses for being late. Was talking to somebody.
- # [18:24] <dael> tantek: I have a concern about confusion from webdev. You learn about :has, :focus and :has-focus doesn't do what you think it would from the pieces. Having it named like that would be confusing.
- # [18:24] <dael> Florian: I'm happy to bikeshed. It's been called focus-within and others. I'm not attached to the name.
- # [18:25] <dael> fantasai: I think I agree with tantek. It should fucntion like :has and :focus if it that :has-focus as a name.
- # [18:25] <glazou> s/like :has and :focus/:has(:focus)
- # [18:25] <dael> fantasai: I think that it's okay for it to also piece shadows, I don't htink it's okay for the host lang to customize :has except through customizing :focus
- # [18:26] <dael> Florian: I'm a bt confused. Are you saying it should be unfocused directly?
- # [18:26] <dael> fantasai: If the host language want to change it changes through :focus and can't change :has-focus. It's a general prinicpal I'd want, but the name makes it more important.
- # [18:26] <dael> tantek: You want to minimize the number of points between specs. If you use how the host lang uses :focus, that's the hook for the host language.
- # [18:27] <fantasai> s/can't change :has-focus except in that it is defined in terms of :focus/
- # [18:27] <fantasai> s/points/interface points/
- # [18:27] <dael> Florian: So if the host lang can modify :focus, that's get. If not I'd like to introduce it on the new thing, no matter the name. It currently does on :active, not on :focus. :focus just matches the focus thing.
- # [18:27] <dael> Florian: That's why I'm trying to introduce this on the expanded focus.
- # [18:27] * glazou suggest HocusFocus
- # [18:28] <dael> tantek: I'd rather allow a hook on :focus that's reused instead of saying you can hook into :has-focus.
- # [18:28] <dael> Florian: If we can I'd prefer that too.
- # [18:28] <dael> fantasai: Is this the label thing? I think there's no backwards compat issue, just impl issues.
- # [18:28] <dael> tantek: Can we re-use the hook on :active?
- # [18:29] <dael> Florian: We can try and say it's the same hook as :active if there's no backwards compat. If we can do that that's best.
- # [18:29] * glazou Hook and HocusFocus seem perfectly in line to me :-)
- # [18:29] * fantasai lol
- # [18:29] <dael> Florian: Should we try and resolve on that? So we resolve that we use the hook on :Active for :focus and we create a new element that is like :focus but piecerece shadows
- # [18:29] <dael> tantek: If you're looking for a name to use :focus-within works.
- # [18:30] * Quits: andreyr (~andreyr@public.cloak) ("Page closed")
- # [18:30] <dael> Florian: Especially if we're using the hook on :focus.
- # [18:30] <dael> tantek: And we can bikeshed on that.
- # [18:30] * Joins: andreyr (~andreyr@public.cloak)
- # [18:30] <Florian> resolution: reuse the hook from :active on :focus
- # [18:31] <Florian> resolution: define a new :focus-within that matches on the same things as :focus, plus parents, including if there are shadow doms
- # [18:31] <dael> Florian: Alright.
- # [18:31] <tantek> sounds reasonable
- # [18:31] <dael> glazou: No obj on those two resolutions?
- # [18:31] <vollick> sgtm
- # [18:31] <dael> glazou: Adopted! Let's move on.
- # [18:32] <dael> Florian: The other topic is related to this. Cureently the hook on :active and the def of :hover both propigate from the label to the labeled control, but not backward. If the control is active the pseudo won't match on the label. I think it's better to go both ways.
- # [18:33] <dael> Florian: I raised that on whatwg and there were few answers. The answers was that one direction is 1-1, but the other was 1to many.
- # [18:33] <dael> gregwhitworth: We ran internal tests and we've never had issues regarding this. The math works, but in the real world you won't hit this problem. I ran something with 5k div iside a label and it was only milliseconds difference, so I don't think it's a problem
- # [18:34] <tantek> curious what dbaron thinks about this
- # [18:34] <dael> Florian: In gerenal it makes sense in both directions. Now that the hooks are sep we might want to decide sep
- # [18:34] <dbaron> I don't particularly care.
- # [18:34] <dael> glazou: Other thoughts?
- # [18:34] <tantek> then I'm willing to go with consensus as well
- # [18:34] <tantek> no strong bias
- # [18:34] <dael> fantasai: I think having it go in both idrections make sense.
- # [18:34] <dael> TabAtkins: I agree as well.
- # [18:35] <dael> Florian: So we should go back to the whatwg and say the CSS group agrees it should work both ways.
- # [18:35] <Zakim> -adenilson
- # [18:35] <Florian> resolution: both :hover and :active should propagate from the labeled control to the label, in addition to the other direction
- # [18:36] <dael> glazou: no objections?
- # [18:36] <Zakim> +??P19
- # [18:36] <dael> [silence]
- # [18:36] <adenilson> Zakim, ??P19 is me.
- # [18:36] <Zakim> +adenilson; got it
- # [18:36] <dael> action Florian to ping the whatwg on the above resolution
- # [18:36] * trackbot is creating a new ACTION.
- # [18:36] <trackbot> Created ACTION-662 - Ping the whatwg on the above resolution [on Florian Rivoal - due 2014-12-03].
- # [18:36] <dael> Florian: So to css3-ui or finish the agenda?
- # [18:36] <dael> glazou: We finished the reg agenda
- # [18:36] <Florian> http://lists.w3.org/Archives/Public/www-style/2014Nov/0425.html
- # [18:36] <dael> Topic: CSS3-UI issues
- # [18:37] <dael> Florian: This is the first comment, it was half of a change. Did you forget the other half or decide not to do it?
- # [18:37] <dael> tantek: Likely accidental. I was trying to be conservative with the edits, but that was prob unintended.
- # [18:37] <dael> tantek: So this was line-box. I'm reading.
- # [18:37] <dael> Florian: So basically do we overflow onto the float?
- # [18:38] <dael> tantek: The suggestion is reasonable. I can make the change. I guess I just didn't make the edit.
- # [18:38] <dael> Florian: I have no opinion. Just trying to guess why you didn't do it. Browsers are interop along the current spec. The question would be to impl would you make the change if we spec it?
- # [18:38] <dael> Florian: It seems reasonable, but we're interop in another way currently
- # [18:39] <dael> Florian: If you have text overflow ellipsis and we're overflowing onto the float, does the text overlap or do we apply the ellipsis
- # [18:39] <dael> Florian: Currently the spec says you overwrite. Everyone does according to text.
- # [18:39] * krit is there a list of UI issues that we are going to discuss today?
- # [18:40] <dael> tantek: I think gecko would change to have the better. There's aspects that are interop, but things like handlingscrolling aren't. So do we look at this as a forward looking chage, or is it a compat issue?
- # [18:40] <dael> Florian: If browsers will change I'm happy
- # [18:41] <dael> Rossen_: With this edge case, and it's very edge, from a usablility pov, let's say you apply the ellipsis, but if your text is colliding, how would you scroll that? I'm assuming in that test case you can't scroll, so why would you hide?
- # [18:41] <dael> tantek: So that you don't overlap and have it look ugly.
- # [18:41] <TabAtkins> https://bug944200.bugzilla.mozilla.org/attachment.cgi?id=8340052
- # [18:41] <dael> Rossen_: How can youg et to that case? Do you have a test case that shows it? I just can't picture how the text would overlap with the float. Unless this is a bug, the float for the text should be one over the other.
- # [18:41] <Florian> https://bug944200.bugzilla.mozilla.org/attachment.cgi?id=8339998
- # [18:42] <dael> tantek: I think the test case from TabAtkins Is the right.
- # [18:42] <dael> Florian: Yes. We're talking about the third line
- # [18:42] <dael> Rossen_: The one that you just pasted?
- # [18:42] <dael> Florian: The third line in TabAtkins's linked example
- # [18:43] <dael> tantek: In this case the third line, what happening is the text is overriding...normally text would wrap around the float. It's only overlapping because the white-space no wrap.
- # [18:43] <dael> Rossen_: Yes, I see. I missed that part.
- # [18:43] <dael> Florian: So what we're currently seeing is by spec. We're preopsing a change
- # [18:44] <dael> tantek: Rather than drop the visable req, there's something else causing the overflow. That's why we should consider the case. Or the line box has a whitespace that deosn't allow wrapping, we're basically talking about condtions where the text can't overflow.
- # [18:44] <dael> Florian: I think that's already addressed by the spec. I think so.
- # [18:44] <dael> tantek: I didn't think it was but okay.
- # [18:44] <dael> tantek: This seems deeper than we thought it would be. It sounds like the spec change to make this req more itterations.
- # [18:44] <dael> Florian: Take it back to the list?
- # [18:45] <dael> tantek: Does that seem reasonable? The whitespace no-wrap relationship should be well understood.
- # [18:45] <Florian> http://lists.w3.org/Archives/Public/www-style/2014Nov/0445.html
- # [18:45] <dael> Florian: That is, but the float bit needs to be looked at. Back to the list. Next one?
- # [18:45] <dael> tantek: Sorry, I though that would be easy.
- # [18:46] <dael> Florian: Still on overflowing. This is issue 37. We have it speced that the resize applies to non-visable overflow and if that's the case in only one dir it applies in only 1 dir. But you can't have that in only 1 dir because everyone is interop that if you have overflow in 1 dir visable is auto.
- # [18:46] <dael> Rossen_: Anything other than that behavior would be a nightmare to impl.
- # [18:47] <dael> Florian: I'm suggesting we remove that bit since it's trying to hook into something that diesn't happen. If we have visable in only one direction we have auto, so visable in only one direction doesn't happen.
- # [18:47] <dael> fantasai: It's a case that doesn't happen.
- # [18:47] <dael> tantek: So we need to say something else
- # [18:47] <dael> Florian: So I proposed a note that ssyas it's not possible, but if later that becomes possible we'll need to define the behviour
- # [18:47] <dael> tantek: So we apply both directions?
- # [18:48] <dael> Florian: Yes. Currently the spec pretends there's another possibility
- # [18:48] <dael> tantek: I agree with TabAtkins that we drop with no note.
- # [18:48] <dael> fantasai: We have a case that's slightly different where there's regions where you paginate in one dir and scroll in the other. That's a case to think about
- # [18:49] <dael> Florian: For regions the frag isn't on the overflow prop. even if you're fragmenting you only have one direction. There's no need for something special. For overflow fragments, the spec isn't stable and we don't know what will happen.
- # [18:49] <dael> Rossen_: I agree. Regions, the only extra constraint is how much content you have, not what happens with content layout. I don't think we can get in situtuations where one direction overflow is visable and the other one it's not
- # [18:50] <dael> Rossen_: So dropping this?
- # [18:50] <dael> Florian: That's my rec and add a note if someone is concerned
- # [18:50] <dael> Rossen_: I'm up for it.
- # [18:50] <dael> glazou: Everyone agrees?
- # [18:50] <dael> RESOLVED: Drop the text
- # [18:50] <Florian> http://lists.w3.org/Archives/Public/www-style/2014Nov/0449.html
- # [18:51] <SimonSapin> Florian, http://www.w3.org/Style/CSS/Tracker/actions/662 lacks some context
- # [18:51] <dael> Florian: The spec doesn't put any constraints on the outline offset, so you can put it -9000 which isn't interop. There's been discussion, but no conclusion. There's no reason to forbid small negative, it's only a problem when the outline smashes into itself.
- # [18:52] <dael> Florian: The option C in the e-mail isn't great. Another is when it slams into itself, but you preserve 1px or the entire thickness whichi s my favorite.
- # [18:52] <dael> tantek: What do impl do?
- # [18:52] <dael> Florian: Disagree. In Chrome it disappears, in FF if you have 1 px outline it has a large black area. so a 10px high box and a -9000 offset, you get a 1000px black thing. It's not interop
- # [18:53] <fantasai> s/outline it/outline and large negative offset it/
- # [18:53] <dael> Rossen_: The outline offset to me, resonable behavior to expect is if you consider the content box and border box you use padding to offset them and that lets you move the border box from the content. We don't allow negative padding, I don't see a reason that outline offset shouldn't be considered the same way. Once you distance outline box from padding box, I don't think why you'd want to constraing inside.
- # [18:54] <dael> Florian: So no negative value?
- # [18:54] <dael> Rossen_: Yes.
- # [18:54] * fantasai thinks we should constrain the dimensions of the interior area and any subset therein to be always non-negative
- # [18:54] <dael> Rossen_: If you draw parallels between how padding is used, it's an offset for borderbox, so outline-offiset is the same thing. We don't allow negative padding.
- # [18:55] <dael> tantek: It's bcause the use cases for drawing an outline are different than a border. I appriciate simplifying the model, this was deliberatly allowed.
- # [18:55] <dael> fantasai: I think we should say the area contasined byt hte outline is floored at 0 so you can't have overlap no matter the shape. If it's ano hourglass it might turn into a 0 width square.
- # [18:55] <dael> Florian: But if you start non-rectangular and shrink, I would block as soon as two sides hit eachother.
- # [18:56] <dael> dbaron: I'm a little worried that you're getting into defining a complex algo for an obscure case.
- # [18:56] <BradK> +1 on stopping the offsets once two edges touch each other
- # [18:56] <dael> Florian: I'm trying to define and make it not disappear because it's useful for :focus.
- # [18:56] * fantasai happy for UA to have higher limits
- # [18:56] <dael> Rossen_: tantek can you explain the major usecase you're trying to achieve?
- # [18:56] * fantasai e.g. letter-spacing has UA-defined limit on negative values
- # [18:57] <dael> tantek: Thre's UIs that have a glow where you want toverlap. I believe that's why it was introduced. I share the concern about trying to overspec and algo. We might be able to say use the metrics of the borderbox and you can't go negative beyond what would 0 out the border box?
- # [18:57] <dael> tantek: You can go negative intot he border box, but you can't completely elimiante it
- # [18:57] <dael> Rossen_: So you want the inner borderbox edge?
- # [18:57] <dael> tantek: It has diementions, and overall width. You devide that by 2 and that's a clamp.
- # [18:58] <dael> fantasai: Maybe define as not changing the outline set, but changing the outline of the shape being drawn. Right now you have various border boxes and we can say this shrinks the box you're wrapping around. if you have a non-rectangualar, the boxes your'e wrapping around shrink
- # [18:58] <dael> Rossen_: What do youe xactly defne as shrink?
- # [18:58] * glazou only Woody Allen can define a shrink
- # [18:58] <dael> tantek: I was trying to spec in terms of the border box.
- # [18:58] <tantek> computed value
- # [18:59] <dael> Florian: To make it more complex, presto does it diff where if you have a way to flow outside the box you can also get it non-rectangualr. Something sticksout and you draw outside that non-rectangual.
- # [18:59] <dael> tantek: We have no obvious solution. We need someone to make a simple prop on the ML that isn't too algo but also handles it resonably.
- # [19:00] <dael> Florian: So are we looking for perfect interop or just keep boxes from disappearing
- # [19:00] <dael> Rossen_: We want interop and please consider inline andoutline where they overlap
- # [19:00] <dael> Florian: And we don't have interop on outline
- # [19:00] <dael> fantasai: I want interop. We should have to spec limit bad things.
- # [19:00] <dael> Rossen_: And we want interop becuase without that there's no reason.
- # [19:00] * glazou guys, top of the hour, we need to wrap up
- # [19:01] <dael> Florian: Short of defining it, we need to make it so that it works for people trying to do common things.
- # [19:01] <dael> fantasai: Letter-spacing says you can do it but there's UI limits, those just aren't defined.
- # [19:01] <dael> tantek: We need simple limits that don't make it useless.
- # [19:01] <dael> Rossen_: And real examples so that we can see what reasonable means.
- # [19:01] <dael> Florian: I'll give it a shot and get back to the list. Rossen_ I'll send you an e-mail to help me understand IE behavior.
- # [19:02] <Zakim> -dbaron
- # [19:02] <dael> Florian: I have more, but that's next week.
- # [19:02] <Zakim> -[Bloomberg]
- # [19:02] <Zakim> -gregwhitworth
- # [19:02] <Zakim> -adenilson
- # [19:02] <Zakim> -krit
- # [19:02] <Zakim> -dauwhe
- # [19:02] <dael> glazou: Thank you.
- # [19:02] <Zakim> -MaRakow
- # [19:02] <Zakim> -astearns
- # [19:02] <Zakim> -BradK
- # [19:02] <Zakim> -glazou
- # [19:02] * Quits: alex_antennahouse (~458c94ae@public.cloak) ("http://www.mibbit.com ajax IRC Client")
- # [19:02] <Zakim> -tantek
- # [19:02] <Zakim> -Florian
- # [19:02] * Quits: MaRakow (~MaRakow@public.cloak) ("Page closed")
- # [19:02] <Zakim> -[Microsoft]
- # [19:02] <Zakim> -koji
- # [19:02] <Zakim> -plinss
- # [19:02] <Zakim> -alex_antennahouse
- # [19:02] * Quits: glazou (~glazou@public.cloak) (glazou)
- # [19:02] <Zakim> -TabAtkins
- # [19:02] <Zakim> -fantasai
- # [19:02] <Zakim> -vivien
- # [19:02] <Zakim> -dael
- # [19:02] * dauwhe enjoy your turkeys, Americans!
- # [19:02] <Zakim> -antenna
- # [19:02] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [19:02] * Quits: vollick (~vollick@public.cloak) (Client closed connection)
- # [19:02] <Zakim> - +1.519.208.aadd
- # [19:02] * Quits: dael (~dael@public.cloak) ("Page closed")
- # [19:02] * Quits: antenna (~antenna@public.cloak) ("Leaving")
- # [19:05] * Quits: gregwhitworth (~gregwhitworth@public.cloak) ("Page closed")
- # [19:06] * Quits: Rossen_ (~Rossen@public.cloak) ("Page closed")
- # [19:09] <Zakim> -SteveZ
- # [19:11] * Quits: andreyr (~andreyr@public.cloak) ("Page closed")
- # [19:14] <Zakim> disconnecting the lone participant, SimonSapin, in Style_CSS FP()12:00PM
- # [19:14] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:14] <Zakim> Attendees were Florian, glazou, dael, dauwhe, gregwhitworth, BradK, +1.631.398.aaaa, tantek, antenna, angelo, [Bloomberg], +1.206.992.aabb, plinss, MaRakow, dbaron, krit,
- # [19:14] <Zakim> ... TabAtkins, astearns, fantasai, SimonSapin, alex_antennahouse, adenilson, Rossen_, SteveZ, koji, +1.519.208.aadd, vivien
- # [19:14] * Parts: BradK (~bradk@public.cloak) (BradK)
- # [19:22] * Quits: murakami (~murakami@public.cloak) ("Page closed")
- # [19:32] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [19:36] * Joins: Florian (~Florian@public.cloak)
- # [19:36] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [19:36] * Joins: Florian (~Florian@public.cloak)
- # [19:39] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [19:44] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [19:50] * Joins: zcorpan_ (~zcorpan@public.cloak)
- # [20:05] * Quits: glenn (~gadams@public.cloak) (Client closed connection)
- # [20:06] * Joins: adenilson (~anonymous@public.cloak)
- # [20:17] * Quits: thinkxl (~thinkxl@public.cloak) (Ping timeout: 180 seconds)
- # [20:35] <TabAtkins> plinss: Just noticed that <tspan> is being "defined" by every single example that mentions it in SVG1.
- # [20:37] <TabAtkins> plinss: Also, a small handful of HTML elements show up in the definitions, but most don't.
- # [20:39] * Joins: Florian (~Florian@public.cloak)
- # [20:40] <TabAtkins> plinss: (Selectors didn't fail to link most of its element autolinks before.)
- # [20:40] * Quits: shepazu (schepers@public.cloak) (Client closed connection)
- # [20:47] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [20:58] * Joins: Florian (~Florian@public.cloak)
- # [20:58] <plinss> TabAtkins: will take a look after llunch
- # [20:58] <TabAtkins> np, i've force-committed for now.
- # [21:05] * Zakim excuses himself; his presence no longer seems to be needed
- # [21:05] * Parts: Zakim (zakim@public.cloak) (Zakim)
- # [21:06] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [21:07] * Quits: dbaron (~dbaron@public.cloak) ("8403864 bytes have been tenured, next gc will be global.")
- # [21:15] * Joins: adenilson_ (~anonymous@public.cloak)
- # [21:16] * Joins: glenn (~gadams@public.cloak)
- # [21:16] * Quits: adenilson_ (~anonymous@public.cloak) (adenilson_)
- # [21:17] * Joins: adenilson_ (~anonymous@public.cloak)
- # [21:18] * Quits: adenilson_ (~anonymous@public.cloak) (adenilson_)
- # [21:20] * Quits: adenilson (~anonymous@public.cloak) (Ping timeout: 180 seconds)
- # [21:22] * Quits: zcorpan_ (~zcorpan@public.cloak) (Client closed connection)
- # [21:23] * Quits: glenn (~gadams@public.cloak) (Ping timeout: 180 seconds)
- # [21:26] * Quits: plh (plehegar@public.cloak) ("Leaving")
- # [21:28] * Joins: Florian (~Florian@public.cloak)
- # [21:49] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [21:52] * Joins: glenn (~gadams@public.cloak)
- # [21:55] * Joins: Florian (~Florian@public.cloak)
- # [21:55] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [21:55] * Joins: Florian (~Florian@public.cloak)
- # [22:14] * Joins: adenilson (~anonymous@public.cloak)
- # [22:30] * Joins: jdaggett (~jdaggett@public.cloak)
- # [22:46] * Joins: dbaron (~dbaron@public.cloak)
- # [23:17] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [23:22] <Florian> the latest commit I made shows up in the repo (https://dvcs.w3.org/hg/csswg/) but not if you actually look at the spec
- # [23:22] <Florian> also, trying to see the changeset from https://dvcs.w3.org/hg/csswg/rev/836486b48f54 gives an error page
- # [23:22] <Florian> actually, any changeset seems to do that
- # [23:28] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [23:30] * Joins: dauwhe (~dauwhe@public.cloak)
- # [23:30] * Quits: antonp (~Thunderbird@public.cloak) (antonp)
- # [23:36] * Quits: glenn (~gadams@public.cloak) (Client closed connection)
- # [23:45] <plinss> Florian: sometimes dev.w3.org/csswg takes a while to update, it looks ok now
- # [23:46] <Florian> it does
- # [23:46] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [23:46] <plinss> also, dvcs.w3.org/hg isn’t all that stable of a server, if it’s giving errors, check hg.csswg.org/drafts
- # [23:47] <Florian> you mean I can't blame it on mercurial and use that as an excuse to root for git. Damm
- # [23:47] <plinss> We’re probably just going to move to hg.csswg.org/drafts since Mike wants to decomission dvcs.w3.org/hg
- # [23:47] <plinss> ocne we move to hg.csswg.org the updates will happen a bit faster
- # [23:48] <plinss> also note there’s a git mirror at https://github.com/w3c/csswg-drafts, it’s read-only for now, but when I complete the move to hg.csswg.org it will sync bidirectionally
- # [23:52] * Quits: dholbert (~dholbert@public.cloak) (Ping timeout: 180 seconds)
- # [23:56] * Joins: dholbert (~dholbert@public.cloak)
- # Session Close: Thu Nov 27 00:00:00 2014
The end :)