15:12:46 RRSAgent has joined #css 15:12:46 logging to http://www.w3.org/2015/03/18-css-irc 15:12:51 Zakim, this will be Style 15:12:51 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 48 minutes 15:12:58 rrsagent, make logs public 15:13:40 glazou has changed the topic to: Agenda confcall 2015-03-18 https://lists.w3.org/Archives/Public/www-style/2015Mar/0285.html 15:50:18 antenna has joined #css 15:55:52 kwkbtr has joined #css 15:56:12 flabbergaster has joined #css 15:56:33 Style_CSS FP()12:00PM has now started 15:56:40 + +1.631.398.aaaa 15:56:58 dael has joined #css 15:57:03 +??P16 15:57:09 Zakim, ??P16 is me 15:57:09 +glazou; got it 15:57:12 AH_Miller has joined #css 15:57:29 adenilson has joined #css 15:57:35 +plinss 15:57:39 +dael 15:57:42 sanja has joined #css 15:58:13 +Florian 15:58:24 +sanja 15:58:34 bkardell_ has joined #css 15:58:46 +MikeMiller 15:58:49 +??P53 15:58:55 murakami has joined #css 15:59:09 Zakim, ?P53 is me. 15:59:09 sorry, adenilson, I do not recognize a party named '?P53' 15:59:18 Zakim, ??P53 is me. 15:59:18 +adenilson; got it 15:59:21 bcampbell has joined #css 16:00:06 +[IPcaller] 16:00:07 I'll be IRC only today :( 16:00:15 IPCaller is me 16:00:18 +??P2 16:00:21 vollick has joined #css 16:00:21 +??P33 16:00:24 Zakim, ??P2 is me 16:00:24 +kwkbtr; got it 16:00:35 zakim, ??P33 is me 16:00:35 +murakami; got it 16:00:42 smfr has joined #css 16:00:54 ScribeNick: dael 16:00:58 +??P56 16:01:11 BradK has joined #CSS 16:01:14 +[IPcaller.a] 16:01:14 bkardell_: ok 16:01:20 Zakim, mute me. 16:01:20 sanja should now be muted 16:01:26 +BradK 16:01:31 zakim, ??P56 is me 16:01:31 +vollick; got it 16:01:35 +[Microsoft] 16:01:37 alex_antennahouse has joined #css 16:01:38 +smfr 16:01:41 zakim, IPcaller.a is me 16:01:42 +tgraham; got it 16:01:49 +dauwhe 16:02:04 zakim, microsoft has me 16:02:05 +Rossen; got it 16:02:10 Zakim, mute me 16:02:10 dauwhe should now be muted 16:02:18 +[IPcaller.a] 16:02:20 +fantasai 16:02:22 +dbaron 16:02:23 I'm ipcaller.a 16:02:38 Zakim, [IPcaller.a] is alex_antennahouse 16:02:38 +alex_antennahouse; got it 16:02:40 zakim, IPcaller.a is alex_antennahouse 16:02:40 sorry, dael, I do not recognize a party named 'IPcaller.a' 16:02:44 +??P7 16:03:28 IPcaller is me 16:03:32 +??P20 16:03:36 Zakim, ??P20 is me 16:03:36 +SimonSapin; got it 16:03:38 [IPcaller] 16:03:41 Zakim, [Ipcaller] is bcampbell 16:03:41 +bcampbell; got it 16:04:16 glazou: We have regrets from chris, TabAtkins will be running late, and poss tantek 16:04:20 glazou: Anything to add? 16:04:46 https://lists.w3.org/Archives/Public/www-style/2015Feb/0445.html 16:04:57 Florian: I'd like to add underlining spaces. Also, impl had two weeksot review box sizing. There's one week left, but I haven't heard anything. 16:05:12 glazou: We'll add underlining spaces at the end of the agenda. 16:05:15 glazou: Anything else? 16:05:30 Topic: mandating some cursor formats 16:05:43 glazou: This will be difficult without ChrisL or tantek 16:05:54 +Lea 16:05:56 Florian: Can we take this a bit later once we have TabAtkins ? 16:05:58 glazou: Yes. 16:05:59 Florian: shh 16:06:06 Topic: the 'all' issue 16:06:17 glazou: Is Cameron on? Prob not because of time 16:06:33 glazou: Item 3 is removed from the agenda. Let's do #6 16:06:36 https://lists.w3.org/Archives/Public/www-style/2015Mar/0161.html 16:06:42 Topic: Generalizing region-fragment 16:07:08 Florian: I sent a long e-mail a while ago dealing with fragments. I won't re-summerize, but what's tricky is naming the exact values. 16:07:32 +[Microsoft.a] 16:07:38 Florian: This isn't a great topic for the call, but there hasn't been much on the list. The idea is you have one value to overflow as usual. There's another where if you overflow you do it as a frag container. 16:07:54 Florian: Another is picking up the idea from Opera about gen pages. Another is discarding a frag break. 16:08:03 Florian: Another is go to the next region in the chain if there is one. 16:08:42 Florian: So this general set is easy to define, but some don't make sense in some places. So if you say go to the next region and you're not in a region chain, what does it mean. So they need to relate to each other. I'm trying to figure out what computes to what. 16:09:07 +[Bloomberg] 16:09:09 Florian: I've realized the initial of 'auto' and the value for go to the next region are the exact same. I don't think auto is a great name for something that computes to. 16:09:36 gregwhitworth has joined #css 16:09:43 arybka has joined #css 16:09:46 Florian: If we look at how things should be called, 'next' is a good name. IN terms of initial value 'auto' is a good name. I picked auto becuase it's more natual, but I'm still a bit unhappy about the names. 16:10:18 Florian: This isn't just bikeshedding. So an alternative is instead of having a next value, we could have break that gos to the next or discards if there isn't one, so we wouldn't need discard. 16:11:13 Florian: The 'break' value it was pointed out that discarding should be more explicit. So discard is a seperate thing. But I'm not entirely happy with it so I'd love more input and I'd like to find better values with more appropriate names. 16:11:22 Zakim, who is on the phone? 16:11:23 On the phone I see +1.631.398.aaaa, glazou, plinss, dael, Florian, sanja (muted), MikeMiller, adenilson, bcampbell, kwkbtr, murakami, vollick, tgraham, BradK, [Microsoft], smfr, 16:11:23 ... dauwhe (muted), alex_antennahouse, fantasai, dbaron, Bert, SimonSapin, Lea, [Microsoft.a], [Bloomberg] 16:11:23 [Microsoft] has Rossen 16:11:24 the current conclusion seems like the best of the options presented so far 16:11:27 Florian: I don't know who can resolve it, but it's awareness about there being an issue. 16:11:35 glazou: It was certainly worth the presentation 16:11:57 Zakim, Microsoft.a is me 16:11:57 +gregwhitworth; got it 16:12:02 Rossen: Starting with the continue prop, it's fairly awk. Continue what? Continue the playback, the streaming of the video, the layout? 16:12:18 Florian: My org prop was to call it fragmentation which makes more sense for spec people, but less for everyone else. 16:12:44 Florian: I'm not extatic about the naming. I think continue isn't righta nd fragmentation too obscure. If you have a better name, go for it. 16:12:51 Florian: It can work, but it's not ideal. 16:13:17 Rossen: The way I've understood this is it's all about layout, right? It's about layout and how the content inside an element behaves when it crosses a fragmentation boundry 16:13:52 Florian: There will be one valuet hat doesn't cause it to be a frag cont and all the others will with diff behaviors as to where the content goes. THere's just one value that says don'tbecome a fragmentainor. 16:14:12 Florian: How we call the prop and what is the set of values, what's in the spec is poss, but I'm not terribly happy about how they're called. 16:14:39 Rossen: The previous, for me, naming consistancy was a bit better. When basically this spec piggy-backed the overflow prop. Making framents or page, etc 16:14:59 +TabAtkins 16:15:06 Florian: Overflow and frag aren't the same. Frag is triggered by overflow a lot, but if you have text shadow bleeding out it won't cause frag. 16:15:27 Rossen: That's not true. In borders you can define what happens in borders. So overflowing and frag are tightly coupled. 16:15:42 Florian: There are interactions, but you still want overflow control sep from frag control. 16:15:48 'continue' is awkward as a CSS property name since it's a verb, whereas most property names are nouns. (I feel like 'continue-in' might be a little more specific, but it still has that problem.) 16:15:54 Rossen: So how do you have overflow: visable and overflow: fragment 16:16:00 +SteveZ 16:16:16 Florian: What's the problem with that. If you have position relative or text shadow it blleds out of the content area. This is what you get on an article today. 16:16:39 Rossen: You're talking about different things. Your'e talking about monolythic things that don't fragment and weither or not something fragments. 16:17:19 Florian: So the 'continue' prop determes if you're a fragmeentaor or not. If you are a fragmentaior, there are still places that have overflow. And where that overflow occurs it's perfectly described by the overflow prop 16:18:14 dbaron: The conceptual difference is overflow is painting and layout isn't. You can have overflow in this painting context. It does make sense to have two different things. I'm not crazy about continue. The other problem is it's a verb and most of our names are nouns or adj. 16:18:25 Florian: Unless we like the fragmentation name, this is the best name we have 16:18:31 ??: I think fragmentation is a better name 16:18:34 s/??/bradk/ 16:18:45 fantasai++ 16:18:53 spill-over: 16:18:58 Yeah, I agree that fragmentation is not a good name. 16:19:18 fantasai: No one outside the CSS WG knows what fragemntation is. We want to use a name that authors would understand. So how would they explain my content goes to another page if it doesn't fit. If they have a vocab there great. If they don't we need to have a new name. 16:19:25 TabAtkins: Do we want to do a poll tomorrow? 16:19:26 It's not great, but 'continue' doesn't seem better 16:20:03 glazou: Find what the photoshop users and inDesign users use. I'm pretty sure this kind of thing exists and if we can re-use that word that would be good. It can be from outside CSS, but if it's known we have to use that. 16:20:10 glazou: I suggest me move on. Is that okay? 16:20:24 Florian: Sure. I'm not looking for a solution now, I'm looking to raise awareness. 16:20:40 https://lists.w3.org/Archives/Public/www-style/2015Mar/0253.html 16:20:40 Topic: the 'all' issue 16:21:41 TabAtkins: The all prop is a shorthand that resets everything except the unicode bidi. This is a problem in a few cases. The one brought up is all kills the focus outline on an element. It's hard to do manual because even if you use auto style it might not give you the right color. I know on mac it's blue or gray, but auto is always gray 16:22:01 all: initial; outline: unset; 16:22:25 er, no, I guess we'd want default, which we dropped 16:22:26 dbaron, that won't work 16:22:28 TabAtkins: This is problem b/c a11y. I'm not sure how or if we can solve this. But it's difficult to tell between a prop for all states of an element and one that applies to just the normal state. So it's the same selecor for focused and unfocused unless you go out of your way. 16:22:30 yeah 16:22:59 TabAtkins: I don't know how to fix this. Any suggestions would be great. Maybe we can do something clever about sperating it out and it can go somewhere good with all. 16:23:17 Florian: Maybe I'm naive about what all is being used for, but would they actually want to say reset to UA? 16:23:30 TabAtkins: Doesn't matter. You're still going to override the focused value. 16:23:33 q+ to comment on use cases for all 16:23:59 fantasai: Florian is correct. We have all: default which the authors get what they want. If they're trying to reset everything on their on they have to use a selector that's more specific. 16:24:21 TabAtkins: That does not apply. All: default doesn't work here. Ther selector that applies is usually .focus 16:24:34 fantasai: But it doesn't matter across levels 16:24:47 glazou: Wait. We've got dbaron on the cue. 16:24:51 s/.focus/:focus/ 16:24:52 s/cue/queue 16:25:19 q+ 16:25:35 s/it doesn't/specificity doesn't/ 16:25:47 dbaron: I think some of these things are things that aren't where people should use all. I think people would want to use all when you have an element you want to mostly disappear in terms of default styles. So you want to rely on a block with no styles is almost invisable. But you prob don't want to apply all to anything where youw ant initial behaviors 16:26:00 sonja: I think that authors want to use this to reset all 16:26:05 dbaron: I don't think that would work. 16:26:14 s/sonja/leaverou 16:26:17 TabAtkins: Neither of the things helps the default selector. 16:26:29 ack dbaron 16:26:29 dbaron, you wanted to comment on use cases for all 16:26:31 I don’t think so. I know it :) I recently tweeted about it and got many replies along these lines 16:26:33 ack leaverou 16:26:35 Florian: I was expecting default would be the thing in the UA stylesheet for the same selector. 16:27:05 TabAtkins: It will run the selectors, but it won't fine the focus rule. And because button: foo is more specific it will over-ride the UA stylesheet. 16:27:18 dbaron: I think everyone disagrees with you about how default works. 16:27:21 TabAtkins: Please expalin 16:27:27 fantasai^: Tab, you're making no sense 16:27:59 dbaron: Default says this declaration overrides the other stuff in this level of the cascade and causes it to fallback to lover levels. So if you have all: default in the author level, you fall back to the winner in the user level. 16:28:20 lover -> lower? 16:28:21 TabAtkins: I was thinking run the cascade with the user level and whatever falls out at the author level. 16:28:28 fantasai: That's how we defined it. 16:28:33 TabAtkins: We hadn't defined it. 16:28:41 s/user level/user or UA levels/ 16:28:45 fantasai: We had it in the spec and removed it. What we had is what dbaron explained. 16:28:55 TabAtkins: Okay. If that works, fine. Let's put it back in the spec. 16:28:59 -adenilson 16:28:59 TabAtkins: Sound good? 16:29:12 dbaron: There were issues with default as to why we removed it. We should look at that. 16:29:25 fantasai: We had impl not see why it was useful and didn't want to impl b/c it was hard. 16:29:28 s/at that/at what they were before we resolve to put it back/ 16:29:29 TabAtkins: That's what I recall. 16:29:40 +??P8 16:29:42 I'm fine with adding 'default' back 16:29:46 fantasai: So instead we created this keyword and they were happy with that. 16:29:48 Zakim, ??P8 is me. 16:29:48 +adenilson; got it 16:29:59 TabAtkins: We can see if there were further issues and resolve to put it back next week. 16:30:05 If we add default, this would also be useful on a per-property level too 16:30:08 TabAtkins: It sounds like a proper def will solve the issue. 16:30:13 fantasai: I can do that tomorrow. 16:30:16 s/I/We/ 16:30:26 glazou: Is tantek on? 16:30:39 Topic: Mandating some cursor formats. 16:30:40 -kwkbtr 16:30:46 https://lists.w3.org/Archives/Public/www-style/2015Mar/0199.html 16:31:06 +??P2 16:31:12 Zakim, ??P2 is me 16:31:12 +kwkbtr; got it 16:31:18 glazou: There was some discussion on this and it's quite important. As you prob all know the current only interop for cursor are .cur and .ico. They're interop impl and they're the defacto standard. 16:31:38 glazou: Unfortinily there is no open spec on them. There's a few doc, but no open spec. 16:31:49 Florian: I think there's a fairly complete desc on the old new blog. 16:32:43 glazou: First, my opinion is it would be really useful if we can't madate without a spec, we should add a note saying the two main things are .ico and .cur. Second, we could mandate PNG and Chris, leaverou and I have been for it. 16:33:30 Florian: On that, there were two things. One were to mandatine PNG and SVG if you support SVG. Elsewise we can say anything used by image it must be support here. It would do the same thing mostly with one level of indirection. So why don't we do that and say in image we require PNG. 16:33:39 SimonSapin: Do we spec a format for fallback? 16:33:51 Florian: There are many where we don't, but where we can it would be useful 16:33:51 s/fallback/background-image/ 16:34:03 fantasai: We don't specify, but we can put a note this is what's used. 16:34:21 s/specify/specify formats anywhere in CSS/ 16:34:41 Florian: For images we don't b/c when they were new we couldn't. Now pretty much everyone supports. For cursor there isn't interop, but there aren't the issues we had 15 years afo with GIF and JPEG. 16:34:52 estellevw has joined #css 16:34:58 q+ to suggest that MS open the ICO spec. 16:35:36 q+ 16:35:37 glazou: I agree with everything from both sides. tantek made it clear you can't ref a non-open format. We haven't before referenced a format, but SVG ref PNG. So in theory we shoudln't, but there is precident. And not mandating formats is why webfonts failed. 16:35:59 Bert: I think you said it on the ML, but why don't we ask MS to open the spec? 16:36:06 glazou: I was about to ask that. 16:36:50 glazou: Since we have MS people on the call, I know you cannot answer right now and you'll have to escalate, but these two formats are old and vigorously impl. It would be so good if you could submit them to the concorcium or open them. 16:37:00 Rossen: We'll have to go through some hoops, we'll take an action. 16:37:27 action Rossen see about .cur and .ico 16:37:27 Created ACTION-676 - See about .cur and .ico [on Rossen Atanassov - due 2015-03-25]. 16:37:31 ack Bert 16:37:31 Bert, you wanted to suggest that MS open the ICO spec. 16:37:34 ack SimonSapin 16:37:49 SimonSapin: For these two formats, are there any patterns, or intellectual prop issues? Or are they we don't have a spec? 16:37:57 TabAtkins: I think they're old enough patents have expired. 16:38:26 Rossen: I don't they've expired. I don't believe there are technical issues. I don't know if the people involved are still witht he company, but there should be documenation. 16:38:37 Rossen: We'll talk about it and get you back an answer. 16:39:15 Florian: I'd like to try and take a few direction. Org go witht he note and add to the note with things from MS if we can. The other is if we can require PNG and SVG. 16:39:50 glazou: I suggest asking if there's agreement or obj on go witht he note saying .ico and .cur are the standards and they will be expected in new products. It's an informative note 16:39:59 dbaron: I'd also like to see images. 16:40:02 Florian: Of course. 16:40:05 glazou: No obj? 16:40:20 dbaron: No, but there's a bunch of varients of this where we might have to discuss which we're referring to. 16:40:31 s/varients of this/variants of these formats/ 16:40:33 glazou: It will be up to the person writing the note as to what exactly goes inside. 16:40:42 glazou: In principle do you agree. 16:40:44 TabAtkins: Yeah. 16:41:03 RESOLVED: go with the note saying .ico and .cur are the standards and they will be expected in new products. It's an informative note. It will be up to the person writing the note as to what exactly goes inside. 16:41:12 glazou: Second thing, with PNG and SVG 16:42:02 Florian: The way I think I'd like to go, #1 on the image value type, there mandate PNG and if the impl supports SVG it must support there. For the cursor level what it supports in static images it must be supported. If they support graphic it should be supported. 16:42:09 Florian: That matches everyone by IE. 16:42:19 Florian: There are other ways to do it, but this makes sense to me. 16:42:29 glazou: It's the most beautiful approach, I agree. 16:42:33 TabAtkins: I'm fine with this. 16:42:37 glazou: Other comments? 16:42:41 glazou: obj? 16:43:02 glazou: If you have a comment, please make it. This is a big change in our history. 16:43:14 TabAtkins: HTML mandates a few formats. 16:43:23 Rossen: ANd an impl can always not conform. 16:43:30 Florian: But if you have reason it's worth hearing. 16:44:02 Rossen: I don't have any offhand before we take it up with the people involved. It would be perhaps worht waiting on this, even if it's a week, before we find out if we'll have any hard reasons not to do it. 16:44:14 TabAtkins: So the thing you're poss obj to is the image formats? 16:44:38 This means we can have a gradient as a cursor? 16:44:40 Rossen: Yes. But you can always not impl. That's why it's not a hard obj, but always why I'm not completely agreeing. If you give us a week we can have a more def answer. 16:44:51 Florian: I can write the chane and come back to you before we impl. 16:44:58 -adenilson 16:45:03 glazou: So there's no obj on the second item, but MS is asking for a week to review. 16:45:05 Rossen: Okay. 16:45:40 bcampbell: It appears to me that adding SVG as a cursor image it might improve high contrast cursors. I would assume SVG would scale better. 16:45:45 Florian: There's nothing preventing that. 16:45:51 tantek has joined #css 16:45:57 Rossen: You were saying SVG will give you higher fidelity and better a11y? 16:46:10 +??P3 16:46:17 Zakim, ??P3 is me. 16:46:17 +adenilson; got it 16:46:25 bcampbell: Yeah, I'm speculating. If you're in high contrast and your cursor grows, I'm going to assume it will scale better. 16:46:29 was there about to be a resolution that got interrupted? 16:46:32 Rossen: I don't disagree on a technical level. 16:46:32 -SteveZ 16:46:57 Rossen: I jsut need to talk to the people wil law degrees. 16:47:09 glazou: So no resolution, we'll revisit next week with Rossen input. 16:47:15 https://lists.w3.org/Archives/Public/www-style/2015Mar/0237.html 16:47:17 Topic: logical overflow 16:47:17 +SteveZ 16:47:38 glazou: BradK can you detail the prop? 16:48:39 BradK: It was that we have an switch that allows overflow-x and -y to turn into -inline and -stacking in terms of behavior, but not in terms of computed values or anything like that. It's just an effect. and we can call that prop what we want. Two values, one 'logaical' and one 'physical' 16:49:32 fantasai: Other prop that have this kind of phsyical, we're creating logical versions. So we should have overflow-line and -block and it will be longhand 16:49:48 I think fantasai said it would be reset by the 'overflow' shorthand? 16:49:49 BradK has joined #CSS 16:50:36 Florian: There's two reasons to do this. One is with borders and padding. The other reason is if the frag things we discussed earlier are attached to overflow, they only make sense in the block direction. So the longahnds being physical is inconvenient. But since I don't think it's a good home for the frag, I don't think that's a good point. So I'm all with fantasai 16:50:45 Yeah, I agree with continuing the pattern we've been using rather than using a different pattern for overflow 16:51:06 BradK: So even if the frag stuff, you still want to know what direction that overflow is in so you can set the overflow in the opposite direction of block overflow 16:51:21 Rossen: Can you elaborate on your use case? Why logical wouldn't work as well? 16:51:29 BradK: In terms of the frag being an on screen page. 16:51:56 BradK: Suppose the frag creating new pages is in vertical direction. You may have long lines you want to overflow: auto prob. 16:52:14 Rossen: Can we take frag off this. So we have one element with a bunch of text and may have vertical flow. 16:52:25 Florian: I don't think we can take frag off. 16:52:43 Rossen: You have have overflow on both sides if you have monolithic elements. 16:53:02 BradK: Even if I have columns you might want vertical overflow to be visable but horz to use a scroll bar 16:53:06 Rossen: We don't have that. 16:53:22 Florian: So if overflow-x and -y is something else, they would both compute to auto. 16:53:25 BradK: Yeah. 16:54:11 Florian: In general I think this idea of having cases where you need overflow in inline and block is valid. With the same priority we want to do the same thing on overflow. THe extra reason with frag, I don't think it applies anymore. 16:54:44 BradK: I think the more common way of having two things where we have overflow: auto...you wouldn't know what way you're going. 16:54:47 Zakim, mute glazou 16:54:47 glazou should now be muted 16:54:52 zakim, mute me 16:54:53 TabAtkins was already muted, TabAtkins 16:54:54 Zakim, unmute glazou 16:54:54 glazou should no longer be muted 16:54:57 Rossen: I'f you're to spec logical prop it would work. 16:55:02 I think the echo is coming from florian 16:55:05 Florian: It wouldn't work now b/c we don't have logical varience. 16:55:12 zakim, unmute me 16:55:12 TabAtkins should no longer be muted 16:55:18 Rossen: But when we have the which is coming in logical rop spec it would work. 16:55:27 So what are we still disagreeing on? 16:55:33 BradK: You would have an initial value that's based on the...not the direction 16:55:42 Rossen: It can be the logical one, not the physical one. 16:55:56 BradK: We could have two diff initial values depending on horz or vert 16:56:01 If transforms weren't invented, I'd be suggesting we make overflow-x/y and repeat-x/y logical and skip having physical ones, but train left the station already on that one 16:56:04 dbaron: What is it you're prop to have two diff values? 16:56:17 Rossen: I don't think that's it. There's the prop of logical or physical 16:56:26 +1 16:56:30 http://dev.w3.org/csswg/css-logical-props/ 16:56:50 dbaron: I think most people, though maybe not everybody, agrees we should overflow the same way we're doing other logical properties. And whichever is decalred later wins the cascade. 16:57:12 BradK: I'm not totally opposed. It seemed there were complication, I'll put something on the ML to see if I can clarify my thoughts. 16:57:29 -SteveZ 16:57:33 glazou: So I guess we'll move to the ML. We only have two minutes remaining on the call. Anything we can discuss in 2 min? 16:57:45 Florian: Transforms won't fit. 16:58:42 Florian: There's the underline I asked to add. fantasai pointed out the change we agreed to on text decorations cannot go into 3, it needs to be 4. I think the entire prop should be level 4. What do we do about the initial value? object or object together with spaces or some kind of auto depending on how they impl prewrap. 16:58:48 fantasai: I think that's more than 2 min. 16:58:58 Florian: Prob. I just wanted to bring it up for awareness. 16:59:05 fantasai: I think the show one is #3 16:59:10 Florian: That was resolved. 16:59:11 s/show/short/ 16:59:29 glazou: So there is removing the prop to level 4. Given that it's at risk and there's no impl it could be moved. 17:00:28 fantasai: What I've heard is apple impl at least one value as how they handle default. So we might need to use it. Also how the behavior of underline is is in that spec. And we don't have a complete publishable level 4. If we're getting to wrap up 3 and have a solid 4, that's fine, but it's not quite ready to be kicked out. 17:00:39 Florian: I just don't like two levels defining the same thing differently. 17:00:54 -vollick 17:01:11 fantasai: I'd rather we figure out what we want it to be in level 4 and have that idea and then move it down. The ideas you have, you have a prop but it's not very solid and until it's solid I don't want ot merge it in. 17:01:24 Florian: So you think of trying to define it in lvl 4 and once it's solid we move it? 17:01:29 fantasai: Yeah. 17:01:33 -kwkbtr 17:01:35 -adenilson 17:01:42 -Lea 17:01:47 fantasai: If we end up witht he solution that changes the original values we can deal with it then. 17:01:55 -[Microsoft] 17:01:57 Florian: Okay. Whatever we do we can do it in level 4 for now. 17:01:57 -smfr 17:01:57 -gregwhitworth 17:02:00 -alex_antennahouse 17:02:01 -dbaron 17:02:01 -BradK 17:02:01 -glazou 17:02:02 -bcampbell 17:02:02 -TabAtkins 17:02:03 -[Bloomberg] 17:02:03 -SimonSapin 17:02:04 -tgraham 17:02:04 -dauwhe 17:02:04 -Florian 17:02:06 -MikeMiller 17:02:06 -Bert 17:02:07 -murakami 17:02:09 -fantasai 17:02:09 glazou: And that closes our conversation for today. Thank you very much. 17:02:15 -dael 17:02:21 - +1.631.398.aaaa 17:02:24 -plinss 17:07:25 disconnecting the lone participant, sanja, in Style_CSS FP()12:00PM 17:07:26 Style_CSS FP()12:00PM has ended 17:07:26 Attendees were +1.631.398.aaaa, glazou, plinss, dael, Florian, sanja, MikeMiller, adenilson, kwkbtr, murakami, BradK, vollick, smfr, tgraham, dauwhe, Rossen, fantasai, dbaron, 17:07:26 ... alex_antennahouse, SimonSapin, bcampbell, Bert, Lea, [Microsoft], [Bloomberg], gregwhitworth, TabAtkins, SteveZ 17:10:26 BradK has left #css 17:14:28 tantek has joined #css 17:20:33 apologies for not being able to participate in the telcon per regrets 17:20:43 was there a resolution re: cursor formats? or just suggestions? 17:20:59 if there's a proposal for an informative note - please let me know so I may look at it for adding it to the spec 17:21:11 there was a proposed resolution, and we're mending feedback from MS before we act on it 17:21:21 the proposed resolution is 3 fold 17:21:50 1 - put a note about .ico and .cur about being the compatible format despite the lack of a spec 17:22:35 2 - mandate PNG as a supported format of the css value, as well as SVG if the implementation supports SVG 17:23:24 that sounds roughly like what I suggest in my last email on the subject 17:23:25 3 - say for cursor that all non animated formats supported for MUST be supported in cursor, and that all animated formats supported in SHOULD be supported in cursor 17:23:41 3 - sounds like your proposal which I said sounded reasonable 17:23:42 Rossen wanted a week to consult people inside MS all all 3 points 17:23:57 the proposed resolution is to do all 3 17:23:58 any other objections? 17:24:19 no, everybody else is cool with it, including Rossen on technical grounds, but he wants to consult legal 17:24:22 fantasai, Rossen, ping? 17:24:40 Also, MS took an action to also review with legal if they can produce an open spec for .ico and .cur 17:24:51 ok then I'll go ahead and make edits for 2 and 3 and wait on 1 17:25:19 Actually, Rossen also wants to check about 2 and 3, so we didn't resolve on these either 17:26:34 that's fine, I can make some edits for 2 and 3 optimistically since they don't mention .cur or .ico 17:26:51 he explicitely requested that we wait, even when not about .cur and .ico 17:26:53 and if he comes back with new information or objections we can evaluate them accordingly 17:26:56 ok 17:27:07 I'll make edits locally then 17:27:10 +1 17:27:36 well, for 3 at least. 2 goes into backgrounds and borders, and then we just depend on it. 17:28:04 oh that requirement on means to edit the value type definition itsefl 17:28:07 ok 17:28:13 yes 17:54:14 adenilson has joined #css 18:25:13 zcorpan has joined #css 18:30:21 ed has joined #css 18:31:17 dauwhe has joined #css 18:38:57 javifgb has joined #css 18:40:25 Florian has joined #css 18:55:37 dbaron has joined #css 18:55:57 ed has joined #css 18:58:53 Zakim has left #css 19:35:19 zcorpan has joined #css 19:38:24 plh has joined #css 20:10:24 Florian has joined #css 20:14:14 TabAtkins: ping 20:14:18 pong 20:15:21 there seems to be some confusion about what it means for a selector to be in the context of a shadow toree 20:15:55 Yeah, dbaron bugged me about that earlier this week. Gonna do some defining today for it. 20:18:00 I'm trying to figure out how chrome is interpreting it, and I've only gotten it to work when :host is the left most selector with nothing to the left of it. 20:18:35 Well yeah, the host element is the root of a shadow tree; anything to the left of :host in a selector will cause :host to try (and fail) to match against non-host elements. 20:18:44 Unless I'm missing something? In which case a specific example would be good. 20:23:47 TabAtkins: so there is a difference between *:host-context and :host-context? 20:24:50 or rather *:host and :host 20:24:57 Yes. The host element is featureless, so it doesn't match any feature selectors (including the universal selector). 20:25:12 So *:host doesn't match the host element, because * doesn't match the host element. 20:25:21 (This is a little weird, but intentional.) 20:26:08 I thought the spec defined featureless elements as having no tag name, classes, attributes, etc., and being in all namespaces... which would mean that they'd match *? 20:26:29 No, the universal selector is a type selector. 20:26:53 maybe it was defined that way because the distinction didn't matter 20:26:55 (Whether to call it that is arguable, of course, but it's intentional that the host element doesn't match *, so I made the definitions fit.) 20:27:04 but if you're making the distinction matter now, I think you should revisit the prose in the definition 20:27:04 Nah, I did that intentionally. 20:27:22 What's unclear in the definition? I purposely wrote those to handle this case. 20:27:38 I haven't looked at the definition of * for a decade or so. 20:28:21 "The universal selector is a special type selector", and universal selector is defined as a "feature selector". Featureless elements "[do] not match any feature selector, or any selector that resolves based on features". 20:28:44 dbaron: Well if you haven't seen the prose since I adjusted it to make this case clear, no wonder you think this case isn't clear. ^_^ 20:29:53 I think it's pretty odd to distinguish between explicit * and implicit * given that implicit * picks up the namespace that's associated with the implicit * and that's the mechanism through which implicit * has namespaces. 20:30:03 There's no longer any implicit * 20:30:12 And there's a note about why that is, in the spec. 20:31:51 it's sometimes nice to run basic changes like this by the working group 20:38:59 wchen, I guess I should re-review your patch, then 20:39:43 dbaron: I did run it by the WG - seee the Aug '14 thread titled "[selectors][css-namespaces][css-scoping] Clash between Namespaces and Scoping regarding implied universal selector" 20:40:34 bz and bkardell commented. 20:40:53 dbaron: thanks :) 20:41:05 TabAtkins, ok, sorry 20:41:11 dbaron: It's fine. ^_^ 20:41:37 I definitely don't always do that, so your complaint had a decent chance of being well-founded. 21:02:06 jcraig has joined #css 21:11:07 Florian has joined #css 21:25:07 zcorpan has joined #css 21:40:16 Please kill me next time I try to name a property something as unsearchable as "all". 21:40:54 It was a clever pun, and reasonably clear, so I'm still happy we took that name, but man, it's impossible to find anything in my mail about it. 21:45:05 zcorpan has joined #css 21:51:36 dbaron has joined #css 21:55:06 TabAtkins: How stable is MQ4? 21:55:29 Aside from maybe some unimplemented MQs, stable. Syntax is def stable. 21:55:37 cool 21:55:50 Someone is implementing it for Servo :) 21:56:01 Basically I think only overflow-block/inline are possibly unstable. The rest is set. 22:32:21 SimonSapin: I haven't reviewed it yet 22:32:57 fantasai: do you think we should impl it behind a flag? 22:33:02 SimonSapin: So, that might mean it's less stable than Tab thinks 22:33:26 SimonSapin: I think so 22:33:29 (though it’s not like we have users who will start writing websites that rely on Servo-only features) 22:33:35 heh 22:33:37 that's true 22:33:57 ok, fair enough 22:43:16 TabAtkins: Did you put will-change into the CR pipeline yet? 22:43:23 Nope. 22:43:49 Trying to actually keep a todo list now; I've dropped a whole bunch of things. Noted. 22:44:00 cool 22:44:17 we should probably go through the entire list of specs tomorrow morning and see what needs to get kicked forward 22:44:22 Sure. 22:44:28 V&U is on that list, we're so close to republishing 22:44:35 just one stupid fix 22:44:39 that I can't remember what it is 22:44:41 >_< 22:46:03 calc 22:46:17 calc()? 22:46:22 sorry, wrong window ^_^; 22:46:40 different calc 22:47:12 heh, nice coincidence 22:47:22 actually now I think about it, I should uninstall it and just alias calc to python 22:47:50 ...maybe? it's a slightly different thing. 22:48:15 it starts a calculator 22:48:28 ah yeah, is ee. 22:48:37 sorry, thought it was a quick input/output calculator. 22:48:44 if it boots up a repl, yeah, just use python 22:49:26 alias i="ipython --no-banner" 22:49:39 although maybe calc is better 'cuz I don't have to import math libraries 22:50:05 You can put the imports into your python call, I think? 22:50:06 or maybe I just can't install anything anymore 22:50:08 -m flag? 22:50:18 eh, whatever, I mostly just use it for lazy arithmetic 22:50:25 yeah 22:50:36 i use either google or the live dom viewer for that a lot. ^_^ 22:56:07 zcorpan has joined #css 22:56:39 tantek has joined #css