16:43:51 RRSAgent has joined #css 16:43:51 logging to http://www.w3.org/2014/02/12-css-irc 16:43:57 RRSAgent, make logs public 16:46:00 antonp has joined #css 16:48:46 rhauck has joined #css 16:50:22 rhauck1 has joined #css 16:51:14 MaRakow has joined #CSS 16:53:02 dael has joined #css 16:54:07 dauwhe has joined #css 16:54:34 dwim_home has joined #css 16:54:52 Style_CSS FP()12:00PM has now started 16:54:59 +dael 16:55:24 ScribeNick: dael 16:56:36 Regrets+=zcorpan, florian, mihai, jerenkranz 16:57:08 +??P43 16:57:11 leif has joined #css 16:57:15 glazou: I'm here for the first time :) 16:57:16 Zakim, ??P43 is me 16:57:17 +SimonSapin; got it 16:57:23 gregwhitworth has joined #css 16:57:26 +dauwhe 16:57:27 liam_ has joined #css 16:57:31 +[IPcaller] 16:57:35 dwim_home, hello Dongwoo !!! 16:58:03 it's 2 am here in Korea 16:58:09 dwim_home, 2am for you right ? 16:58:10 yep 16:58:11 tantek has joined #css 16:58:12 urghhh 16:58:13 glazou: good to see you :) 16:58:28 +SylvaIng 16:58:37 dwim_home, can you join the call? 16:58:47 +??P54 16:58:55 Zakim, ??P54 is me 16:58:55 +glazou; got it 16:59:18 +krit 16:59:52 glazou - can we push charter discussion later in the call (not first) ? can't join for a bit. 17:00:00 glazou: I'm joining the call using the number for boston now. 17:00:02 +??P5 17:00:14 Zakim, ??P5 is me 17:00:14 +abinader; got it 17:00:17 +[Microsoft] 17:00:26 also if there's time, for the end of the agenda: http://lists.w3.org/Archives/Public/www-style/2014Feb/0140.html 17:00:38 thanks for your consideration (on both items) 17:00:40 bbiab 17:00:47 +??P38 17:00:52 noted tantek but the agenda is already pretty full... 17:00:55 +glenn 17:00:57 Zakim, I am ??P38 17:00:57 +leif; got it 17:01:05 +rhauck 17:01:22 +Stearns 17:01:28 +plinss 17:01:51 +Bert 17:01:59 +[Bloomberg] 17:02:18 Regrets+=antonp 17:02:23 sgalineau, ROFL 17:02:27 sgalineau: LOL 17:02:34 with or without a napoleon hat ?-) 17:02:50 +BrianKardell 17:03:04 Zakim, who is here? 17:03:05 On the phone I see dael, SimonSapin, dauwhe, [IPcaller], SylvaIng, glazou, krit, abinader, [Microsoft], leif, glenn, rhauck, Stearns, plinss, Bert, [Bloomberg], BrianKardell 17:03:05 On IRC I see tantek, liam_, leif, dwim, dauwhe, dael, MaRakow, rhauck1, antonp, RRSAgent, Zakim, glazou, jet, dbaron, glenn, sgalineau, plh, abinader, arronei, slightlyoff_, 17:03:10 ... lmclister, dfreedm, krijn, achicu, jacobg, cbiesinger, shepazu, ed, paul___irish 17:03:39 c_palmer has joined #css 17:03:54 +Plh 17:03:56 oops 17:03:59 zakim, drop plh 17:03:59 Plh is being disconnected 17:04:00 -Plh 17:04:05 +Plh 17:04:06 +[Bloomberg.a] 17:04:18 Zakim, [Bloomberg.a] is me 17:04:18 +c_palmer; got it 17:04:44 glazou: Let's start 17:04:53 glazou: As usual, any extra items? 17:05:07 ...: It's pretty full, but if you have something we can retain for next week that's fine 17:05:13 ...: We have an item from tantek 17:05:21 +TabAtkins 17:05:24 ???: Is it worth doing a poll on the call? 17:05:29 Andrey has joined #css 17:05:31 s/???/tantek/ 17:05:34 glazou: You mean selectors? I suggest we do that 17:05:41 (hopefully quick, had one positive response from TabAtkins, no objections) 17:05:47 SimonSapin, haha I'm not on the call (yet) 17:05:48 ...: I think the poll is invalid because it was changed. 17:05:58 TabAtkins: As I said we know who saw it before the change. 17:06:02 rhauck has joined #css 17:06:08 oh, s/tantek:/???:/ then 17:06:10 +dbaron 17:06:11 glazou: We're just adding items now, and I responded on the list. 17:06:21 glazou: So first extra item is the poll. Any others? 17:06:25 Topic: Charter 17:06:36 +??P16 17:06:43 glazou: Can we have an update on charter extension. Before you said ready b4 F2F 17:06:54 plh: I think we're on tracka nd don't expect any surprised 17:06:58 glazou: Any questions? 17:07:04 Topic: New Regions WD 17:07:15 (TabAtkins, present it as two polls with separate results) 17:07:22 astearns: Just a new WD. It's been 8 months since last and there's been sub. changes so I'd like to publish 17:07:34 RESOLVED: Publish a new WD of Regions 17:07:42 plh: Is this the split we discussed? 17:07:46 astearns: Yes. 17:07:48 plh: Okay 17:07:51 s/plh/Bert/ 17:07:53 glazou: So you approve? 17:07:56 bert: I do 17:08:11 +MaRakow 17:08:23 glazou: Given that it's a hot topic, let's instert Grid now 17:08:29 Topic: Grid Issues 17:08:38 s/grid/selector poll/ 17:09:03 glazou: So TabAtkins publish a poll about selectors. In short it's a Q, do you prefer !, descriptio or :has 17:09:34 ...: The problem is originally it was ! or has but after 130 resolnces he changed the wording 17:09:45 ...: lots of people rejected ! 17:10:04 ...: I think the new question is different and I don't think that we can infur anything because of that. 17:10:22 ...: SimonSapin suggested a new poll ith three options, ! :has, or ??? 17:10:32 ...: So I think I reject the results of the poll 17:10:48 SimonSapin: I agree results are useless but I think Tab should seperate results of exit poll 17:11:08 TabAtkins: I can do first 130 os ! vs Has and the rest as cercumspect vs has 17:11:15 glazou: I don't think you can do that 17:11:24 TabAtkins: I think we have an ovwhelming result 17:11:31 glazou: This just isn't the same question 17:11:44 TabAtkins: We've had 800 results and most of them picked the same answer as before 17:11:58 +[Apple] 17:11:58 so if you polled two separate questions at different times, just report the results separately? 17:12:06 Zakim, Apple is me 17:12:07 +hober; got it 17:12:11 glazou: Taking my co-chair hat off, as a standards body we aim at doing things right and this isn't done right. We don't change the question in the middle of a vote 17:12:14 sgalineau +1 17:12:23 ...: Even if it's only 10% that disagree with what you say is final results. 17:12:29 dbaron, this is effectively what happened 17:12:40 TabAtkins: We're randomly sampling in the first place, so it just doesn't matter if they're two seperate polls 17:12:51 ???: Since I'm on neither side of the discussion 17:13:07 ...: I think when they put the poll together what they wanted to gage wasn't if ! is confusing 17:13:13 +1 to Tab's position. The results are useful considered separately. And they both point to the same result 17:13:16 ...: But they wanted an indicator like a combinator 17:13:27 ...: Overwhelming people picked the combinator 17:13:37 +[IPcaller.a] 17:13:40 TabAtkins, please give numbers for the separate results on IRC 17:13:51 ...: We mixed two questions and I think TabAtkins was trying to act in good faith to see if we were asking the right question 17:14:05 who is ??? 17:14:07 s/???/briankardell 17:14:12 ...: TabAtkins was saying we can derive people want a combinator and we can do another poll 17:14:32 glazou: Reading the results, i think people were influenced by the ! and they were rejecting the ! 17:14:45 TabAtkins: And that's why the poll was changed to see if that was an issue. 17:14:50 s/briankardell/bkardell/ 17:15:03 bkardell: Do we have a reason for not doing what TabAtkins Is suggesting? 17:15:12 -abinader 17:15:14 -dbaron 17:15:19 -TabAtkins 17:15:28 ???: Is this just avoiding work so we can prove what TabAtkins is saying or have another statement? 17:15:30 lmcliste_ has joined #css 17:15:40 bkardell: I think we can frame that with having just three options and that'll work 17:15:40 +??P5 17:15:48 Zakim, ??P5 is me 17:15:48 +abinader; got it 17:15:53 glazou: I think it's painful that we can't discuss what a member did without him leaving. 17:16:09 ...: I'm going to stop now, but I'm disputing the results which we're going to specify 17:16:15 I'm still here, I just can't stand listening to people pretend that a poll is "biased" because they don't understand population statistics. 17:16:16 ...: This is impossible to discuss. 17:16:31 glazou: We don't have an update on Shadow DOM 17:16:46 glazou: I think saying I don't understand population stats is an insult. 17:16:56 ???: I don' thtink that was the point, though. 17:17:02 +TabAtkins 17:17:03 s/???/plh 17:17:05 glazou: I'm saying the sampling isn't valid due to the change. 17:17:10 -TabAtkins 17:17:37 bkardell: I think there was an issue and we tried to resolve it. We can look at the issue and try and resolve the difference, but I think that we're running in circle and not making progress 17:17:37 Tab ? 17:17:46 Tell me when you're done, plese. 17:17:46 glazou: TabAtkins for Shadow DOM? 17:17:53 s/bkardell/sgalineau/ 17:18:07 +TabAtkins 17:18:18 Topic: Shadow DOM 17:18:24 TabAtkins: Let me pull the info 17:18:34 ...: First I'd like to see if we can finalize a named combinator 17:18:44 ...: I'm assuming that /ident is a decent syntax 17:18:53 ...: It looks good to me and people in the thread. 17:19:14 fantasai: I don't think that /ident is good because that's usually punctuation 17:19:43 ...: It's usually just a character so I think a syntax in that pattern isn't a good idea. We have :ident #ident etc and they're all a compound selector 17:20:03 ...: If we're going to have that it should have punct. at the begining and end and follow the white space rules of combinators 17:20:30 `foo` 17:20:32 dbaron: I think a few people liked the idea of brackets. 17:20:37 /foo/ 17:20:38 /ident/ 17:20:44 fantasai: We can just use that (above) 17:20:47 /ref somethingorother/ 17:20:54 is '/ ident' the same as '/ident' ? 17:20:57 no 17:20:57 TabAtkins: I'm fine with that. I like single slach, but 2 is okay as well. 17:21:01 I'm OK with either as well 17:21:04 well, I guess we could define it either way :) 17:21:18 SimonSapin: No, it's not - ". ident" isnt' the same as ".ident" 17:21:26 ok 17:21:30 bkardell: I realize we don't have single style comments in CSS, but I worry that using something close to C++ is confusing to authors. 17:21:32 SimonSapin: Whitespace is significant in selectors. 17:21:46 fantasai: It's a single slash followed by another slash, though. 17:21:48 was that s/bkardell/hober/ ? 17:21:55 so fantasai would rather have something like /foo/ 17:21:57 ? 17:22:00 TabAtkins: I'm done with that. If the WG qould like to resolve that's fine. 17:22:12 bkardell 17:22:14 s/done/down/ 17:22:17 fantasai: I'm still wondering if it should be combinator instead of pseudoclass, but I haven't read entire thread. 17:22:31 backticks comment was me 17:22:36 TabAtkins: Any other syntax suggestions? 17:22:56 TabAtkins: backticks, slashes or...? 17:23:01 I am good with `foo` or /foo/ 17:23:08 s/.../pseudo-elements/ 17:23:15 ???: This isn't strictly combinator syntax. 17:23:20 s/???/hober/ 17:23:39 hober: I'm just wondering do we want to allow for future CSS to allow author-defined custom items 17:23:50 TabAtkins: Possibly which makes the ident nice. 17:24:11 hober: I'm not sure quite what exlusion there was but I'd rather avoid collisions between the WG and arbitary def. 17:24:18 +dbaron 17:24:30 TabAtkins: The way the F2F discussion was - are technically allowed in HTML, the main space is ident- 17:24:35 ...: In CSS we use _ the same. 17:24:45 ...: So if your media query has _ it's custom 17:24:52 hober: I'm fine with that for now. 17:25:05 TabAtkins: This is a little ugly, but works. We'll avoid collisions. 17:25:26 TabAtkins: Since there's no additional syntax ideas, feel free to butt in. 17:25:35 ...: Are we okay with / on both ends? 17:25:43 TabAtkins: I'd like to resolve on that. 17:25:55 bkardell: If we want a combinator in the future we bring it back 17:26:07 fantasai: I'm not sure if this is right, but if we're going this way this is good. 17:26:08 /ref(foo)/ or /ref foo/ or whatever 17:26:17 Also, I'm minuted above as saying something at a point when I wasn't on the call. 17:26:20 s/this/using a combinator rather than pseudo-class/ 17:26:29 +[Microsoft.a] 17:26:30 +1 to what hober said 17:26:31 -??P16 17:26:31 bkardell: I'd like to authorize TabAtkins to do what he needs, but I'm not sure I want to say this is the right thing to do. 17:26:31 s/this way/with a combinator/ 17:26:38 s/this is good/this syntax is good/ 17:26:41 rhauck has joined #css 17:26:42 s/bkardell/hober/ 17:26:43 ...: Would a watered down resolution to allow you to spec be okay? 17:26:56 TabAtkins: I speced it. I want to know if the WG is okay 17:27:04 fantasai: Is this in selectors or shadow DOM? 17:27:12 TabAtkins: Putting it in sleectors 17:27:28 fantasai: I'd pref Shadow DOM and let sleectors stabalize before shifting things into it. 17:27:46 dbaron: Is that b/c you're not settled on named combinators? 17:27:53 s/dbaron/bkardell/ 17:27:55 s/dbaron/dauwhe/ 17:27:59 heh 17:28:29 +1 to what fantasai is saying 17:28:29 fantasai: I'm not objecting per se but I'm not sure if this is the right idea. Selectors is almost implemented and this isn't qualified. I'd rather leave it in shadow DOM so that it can be discussed more. 17:28:46 ...: I don't want to mix this unstable thing with selectors where we're trying to take unstable things out. 17:28:59 TabAtkins: As long as no one is actively obj to syntax it can stay 17:29:26 TabAtkins: In other words it sounds like we can move on 17:29:26 s/it can stay/it is good enough for me for now/ 17:29:31 glazou: Excellent 17:29:39 Topic: Counter Styles API 17:29:55 TabAtkins: Xidorn brought up interesting CSSOM questions 17:30:24 ...: If you don't spec a descriptor in the style sheet, what rule should appear? Null, empty string, or initial value? 17:30:36 ???: Any impl consistancy? 17:30:45 s/???/glenn/ 17:30:49 TabAtkins: None I've seen. Thoughtbase (?) has it implemented 17:31:04 -abinader 17:31:15 dbaron: In many ways this is similar to properties, but there's not difference between original and unset 17:31:29 +??P5 17:31:29 s/original/initial value/ 17:31:31 ...: My feeling is leave it the same as there's not semeantic difference 17:31:36 s/Thoughtbase/@font-face/ 17:31:37 Zakim, ??P5 is me 17:31:37 +abinader; got it 17:31:38 ... as the empty string 17:31:46 zakim, microsoft has me 17:31:46 +Rossen_; got it 17:31:53 fantasai: Interesting question is if you're doing the OM, do you want to rest, or preserve what the editor put in? 17:32:09 ...: If there's no semantic difference it seems like things that are initial should stay set that way. 17:32:23 jrossi2 has joined #css 17:32:23 TabAtkins: Sep but related question. You need to spec how these things serealize. 17:32:35 ...: If you omit everything you would omit anything set to inital value too 17:33:02 TabAtkins: I think I like having it reflect initial value and on the serialization side specify you omit the scriptor is it's they're inital value 17:33:07 ...: How does that sound? 17:33:19 dbaron: On q is what do they do for @font-face 17:33:36 TabAtkins: I'm not sure. If we want to move on and come back to me I can test for 5 min and come back with data 17:33:58 TabAtkins: So let's do that. I'm come back in a few to tell you what font-face does in chrome and firefox 17:34:02 glazou: So we can move on? 17:34:09 Topic: Concept of Baselines 17:34:19 dbaron: I don't think this needs telecon time 17:34:26 glazou: Okay, good. 17:34:34 Topic: ::first-letter 17:34:44 dbaron: We had a long debate about what goes in ::first-letter. 17:35:00 ...: spec if specfic when punc. extends first letter, but not what a first letter is. 17:35:19 ...: First letter apllies to first letter and also applies to digits, but doesn't mention anything else. 17:35:43 ...: I think Echo is the only one that does letter or digits and we occ. get bugs were people expect it to apply to symbols 17:35:48 ...: I remember + and $. 17:35:59 ...: It would be nice if spec said what the first letter applied to 17:36:26 ...: There's one other quirk with this where we reference character classes we need to say what version of unicode we're referencing 17:36:31 s/Echo/Gecko/ 17:36:56 dbaron: Do people think symbols should be a first letter? Is that a bug in other impl? 17:37:03 +??P14 17:37:15 Zakim, ??P14 is tantek 17:37:15 +tantek; got it 17:37:19 fantasai: I think it's fine. The interesting q is do we just include symbol, or symbol and next thing 17:37:25 ??: I would expect on ly the symbol. 17:37:31 bert: That's not what I would expect 17:37:31 s/??/astearns/ 17:37:40 ooh are we debating syntax live on the call? nice. ;) 17:37:41 ???: Is this based on unicode catagories? 17:37:47 TabAtkins: That would be nice. 17:37:58 s/???/SimonSapin/ 17:38:04 s/TabAtkins/dbaron/ 17:38:04 ??? So we would blacklist a bunch of catagories it doesn't apply to? 17:38:11 s/???/hober:/ 17:38:13 TabAtkins: That may work, things like white space 17:38:19 s/TabAtkins/dbaron/ 17:38:56 fantasai: There's some general classes in unicode, like high level ones. 17:39:08 ...: I think we're only interested in doing high level ones 17:39:18 s/general/two levels of general/ 17:39:30 s/like high/higher and lower/ 17:39:38 astearns: Suppose unicode decided to add a new top level class. I'd rather have that included. I don't anticipate them adding white space. 17:39:44 spacy, is that like falsy? 17:39:49 TabAtkins: I think if they add a new class, we want the old rules to apply. 17:39:54 spacy characters? 17:40:03 s/TabAtkins/dbaron/ 17:40:12 and s/astearns/hober/ (I think) 17:40:14 dbaron: Unless someone else wants to, I guess I should write a proposal? 17:40:37 hober: I think we're all agreeing 17:40:44 dbaron: Sounds like we're done. 17:40:47 s/hober/Rossen_/ 17:40:47 s/hober/Rossen/ 17:40:57 TabAtkins: can we jump back? 17:41:14 ...: In both chrome and firefox, font-face is the empty string. 17:41:23 ...: I'll find a place to spec that. 17:41:29 dbaron: Sounds good to me. 17:41:33 TabAtkins: Cool. 17:41:42 s/to me/to me, given that it's what we do for properties/ 17:41:46 s/font-face/unspecified descriptors in @font-face/ 17:42:13 TabAtkins: Can we get a resolutions? 17:42:16 glazou: Comments? 17:42:38 TabAtkins: For any unspec descriptors in @ rules that font-face and counter style, they're in the OM as the empty string 17:42:45 hober: And this is what they do? 17:42:52 TabAtkins: In chrome and fireforx. 17:42:58 s/hober/rossen/ 17:43:04 17:43:04 17:43:04 rossen: Can you post that test? 17:43:21 TabAtkins: I did that and poked around for font weights. 17:43:43 glazou: To be sure, it's qhen you query the explicit value of a descriptor? 17:43:47 TabAtkins: That's a good question. 17:43:56 glazou: I don't want to see it effecting a group. 17:44:05 TabAtkins: CSSOM defines that and impl differ. 17:44:20 ...: Right now in chrome you see every prop that could apply to any element show up. 17:44:28 ...: That's likely because we're using the same impl. 17:44:34 glazou: Then I have no obj. 17:44:51 rossen: Just a second, I'm getting on my comp to test it. 17:45:51 TabAtkins: Do you want us to wait, or should we move on and you can report back. 17:46:00 Rossen_: It'll take me two minutes. 17:46:07 glazou: We'll come back when Rossen_ is ready 17:46:12 TopicL Grid Issues 17:46:29 SimonSapin: Biggest issue is how we define size of grid item and grid container 17:46:38 ...: Did I miss that in the spec, or is it not written? 17:46:52 -abinader 17:46:55 TabAtkins: I'm not ready to handle the issues. We're working on it and will answer as we get there. 17:47:08 ...: We haven't made it there quite yet. fantasai and I are working together. 17:47:27 ...: As soon as I can I'll do it, but if you want to message me privatly with a time line, that's okay 17:47:35 SimonSapin: We don't need more time for any grid issues. 17:47:52 http://lists.w3.org/Archives/Public/www-style/2014Feb/0356.html 17:47:56 Topic: inline box, atomic inline-level box, and transformable elements 17:48:11 glazou: I saw some ML answers on this 17:48:34 TabAtkins: I think he has asking about the earlier descion that inline-elements being able to be transformed 17:48:57 ...: and dbaron had a seperate question that was tangentally related about the spec only applying to elements related to CSS. 17:49:05 ...: But that's different than the orignal 17:49:25 dbaron: My q was that the spec isn't saying what we want it to and we should check that before we nit-pick. 17:49:34 ...: so we said it shouldn't aplly to transofrms 17:49:37 many: yes 17:49:55 ??: I think we want to say we can transform a box, not a collection of elements. 17:50:09 TabAtkins: We only transform fragments that are the sole fragment created by a box. 17:50:21 ...: they're the sole fragment by decision not happenstance. 17:50:30 dbaron: Didn't we dicuss this at the F2F? 17:50:47 ??: We did, but we didn't agree. The agreement was it shouldn't apply. 17:50:50 s/dicuss this/have a long discussion about how transforms apply to fragmented blocks/ 17:50:58 dbaron: Seems bad it stops applying as soon as you print. 17:51:03 ??: That's a good question. 17:51:21 dbaron: I'm okay with not applying ti inline, but I'm not okay that it stops as soon as it fragments. 17:51:39 TabAtkins: Starting with the base question, is the test wrong b/c spec says it shouldn't apply to inline. 17:51:57 ...: IN other words, the test is wrong. It currently assumes that fragments apply to inline. 17:52:21 TabAtkins: Cool. So Gerard is right. We can take this later to decide what the definition os transformable elements should be. 17:52:29 s/os/of 17:52:31 -[Bloomberg] 17:52:41 TabAtkins: So it sounds like that finishes the issue. 17:52:47 glazou: Okay. 17:52:56 glazou: tantek you still there? 17:52:58 tantek, PING :-) 17:52:59 seems like the spec ought to exclude non-replaced inlines rather than imply that any new formatting primitives (flexbox, grid, etc.) aren't transformable 17:53:11 +! 17:53:20 Topic: Line box edge 17:53:29 tantek: I made a proposal to change that based on impl. 17:53:34 ? 17:53:41 tantek, link? 17:53:44 ...: I got one positive reply, but I wanted to run it by the group before I edited. 17:54:02 ??: It sounded good to me. 17:54:05 http://lists.w3.org/Archives/Public/www-style/2014Feb/0140.html 17:54:10 glazou: Can you post the link? 17:54:42 +1 from me 17:54:56 tantek: Thanks fantasai 17:55:00 glazou: Other optinions? 17:55:11 fantasai: I think you want to run it by Robert Callahan 17:55:25 tantek: I already pinged him. I want to hear from other impl. 17:55:35 s/Callahan/O'Callahan/ 17:55:42 ...: We (firefox) want to match webkit and want to make sure other impl find it acceptable 17:56:00 rossen: It will mean a change for us, but I agree auto behaviour makes more sense 17:56:08 +1 from me, too 17:56:11 glazou: Anyone from webkit? 17:56:24 ???: webkit will change when microsoft changes. 17:56:40 s/???: webkit will change when microsoft changes.// 17:56:50 tantek: There's wo changes, one webkit already does, one that's a logical consiquence of the change. 17:57:07 tantek: I don't think anyone does the second behaviour yet, but it makes sense. 17:57:16 Rossen_: I think that's fine. We can revisit later. 17:57:25 glazou: No objections? You've got it tantek 17:57:31 glazou: We've got more time. Anything else? 17:57:36 tantek: Did you do charteR? 17:57:47 glazou: Yes. It'll be under review shortly 17:57:56 tantek: I think the super-group discussion needs to continue. 17:58:13 glazou: Yes, from time to time it's extremely beurocratic. 17:58:30 ...: It lacks a bit, but I don't think all exisiting super-groups will be in the same catagory. 17:58:45 ...: They'll be quite different and I'm not sure the current prose will work for everything. 17:58:59 tantek: I think glazou is having a positive impact and you should keep going. 17:59:08 glazou: We needed something different. This isn't working. 17:59:12 glazou: Anything else? 17:59:16 -hober 17:59:17 -SylvaIng 17:59:17 -krit 17:59:18 glazou: Thank you and talk to you next week. 17:59:18 -Plh 17:59:18 -[Microsoft.a] 17:59:18 -dbaron 17:59:20 -BrianKardell 17:59:20 -dauwhe 17:59:21 -glazou 17:59:21 -c_palmer 17:59:21 -fantasai 17:59:21 -SimonSapin 17:59:22 -Stearns 17:59:23 -Bert 17:59:24 -TabAtkins 17:59:26 -MaRakow 17:59:26 -tantek 17:59:30 -dael 17:59:31 -plinss 17:59:37 -leif 17:59:38 -rhauck 18:02:01 -[IPcaller] 18:02:54 rhauck1 has joined #css 18:03:46 rhauck has joined #css 18:05:13 -glenn 18:06:48 rhauck1 has joined #css 18:07:47 rhauck2 has joined #css 18:10:13 disconnecting the lone participant, [Microsoft], in Style_CSS FP()12:00PM 18:10:16 Style_CSS FP()12:00PM has ended 18:10:16 Attendees were dael, SimonSapin, dauwhe, [IPcaller], SylvaIng, glazou, krit, abinader, glenn, leif, rhauck, Stearns, plinss, Bert, [Bloomberg], BrianKardell, Plh, c_palmer, 18:10:17 ... TabAtkins, dbaron, MaRakow, hober, fantasai, Rossen_, tantek 18:11:12 are the results of TabAtkins's poll visible somewhere? 18:11:39 https://docs.google.com/spreadsheet/ccc?key=0AmRB4Bq4bNRBdHdCcDJJZWxEaEhLU20yOGo1ZVBvT2c&usp=sharing 18:11:48 I'm writing up an email with the results now. 18:11:58 It's so lopsided I dont' think I need to continue the poll. 18:12:21 glazou has joined #css 18:12:49 adenilson has joined #css 18:13:39 TabAtkins, was there any other summary of the results that led to people's reactions? 18:14:08 I hadn't given a summary yet, no. Just what was in the thread. 18:19:04 I was surprised by the poll change, but it seemed entirely reasonable 18:19:19 another day of "! means not!" responses wouldn't have been as useful 18:19:28 Yeah, we'd gotten a lot of comments int he initial results like that. 18:19:29 agreed 18:20:27 I think having 10 minutes of the call being the chair complaining (with "chair hat off", maybe?) about Tab's predicted future actions was not a good use of telecon time. 18:20:29 rhauck has joined #css 18:20:54 agreed 18:21:03 that's why I hung up 18:21:11 Me too. 18:23:14 (above, on IRC, I was just trying to figure out if there was something I'd missed that led to that) 18:24:28 I don't think so 18:25:41 Hah, though someone in the comments points out that ^ has negation implications too (from regex character classes) ^_^ 18:25:59 rhauck has joined #css 18:26:12 Naming is hard, but giving arbitrary meaning to ASCII characters is harder :) 18:26:26 Yup. 19:03:07 glenn has joined #css 19:25:26 Ms2ger has joined #css 19:28:59 glazou has joined #css 19:31:38 dauwhe has joined #css 19:50:04 leif has left #css 20:02:40 Zakim has left #css 20:04:34 TabAtkins: what’s the preferred way to track Selectors issues? 20:06:38 or fantasai? 20:13:06 glenn_ has joined #css 20:15:04 SimonSapin: Mailling list, or in spec. 20:32:42 Rossen_f2f has joined #css 20:32:43 lmclister_ has joined #css 20:32:44 dfreedm has joined #css 20:32:46 jacobg_ has joined #css 20:32:46 bkardell_ has joined #css 20:32:47 jet has joined #css 20:32:48 achicu_ has joined #css 20:32:49 jrossi21 has joined #css 20:32:49 slightlyoff_ has joined #css 20:32:54 amtiskaw__ has joined #css 20:32:55 decadance has joined #css 20:32:56 arronei has joined #css 20:32:57 abinader has joined #css 20:32:57 glenn has joined #css 20:32:57 shepazutu has joined #css 20:32:58 projector has joined #css 20:32:59 krijnh has joined #css 20:32:59 dauwhe has joined #css 20:33:03 astearns has joined #css 20:33:04 mihnea_ has joined #css 20:33:07 gsnedders has joined #css 20:33:08 birtles has joined #css 20:33:10 lmclist__ has joined #css 20:33:10 abucur has joined #css 20:33:12 cabanier_ has joined #css 20:33:12 alexmog_away has joined #css 20:33:12 sylvaing_away has joined #css 20:33:14 plh3 has joined #css 20:33:16 adenilson has joined #css 20:33:17 TabAtkins_ has joined #css 20:33:22 Teoli has joined #css 20:33:37 logbot has joined #css 20:33:39 SimonSapin has joined #css 20:33:51 shans_away has joined #css 20:33:52 mvujovic_ has joined #css 20:33:58 antonp has joined #css 20:34:18 dbaron has joined #css 20:34:18 ed has joined #css 20:34:23 leaverou_away has joined #css 20:34:28 cbiesinger has joined #css 20:34:41 krit_ has joined #css 20:34:48 fantasai has joined #css 20:37:35 glenn has joined #css 20:38:15 Bert has joined #css 20:39:47 SimonSapin: I'm going to spend the rest of this week porting Bikeshed to Python3. Any immediate pitfalls you know of? 20:43:25 Are you dropping 2 ? 20:44:03 TabAtkins: ^ 20:44:18 Planning to, but I'm doing the work in a branch first so I can play with it. 20:44:35 I've informed Peter about it, so I'll keep Bikeshed's p2 support until he's done, at least. 20:44:55 Another option is to write code that runs on both 20:45:03 same code base 20:45:34 http://python3porting.com/toc.html is a good guide 20:45:39 either way 20:45:53 The main reason I'm doing it is to simplify unicode handling, because I *still* run into encoding errors. 20:46:08 So maintaining a compatible codebase seems unlikely. 20:46:30 ok 20:46:37 then you can start with 2to3 20:46:46 a tool that does automatic conversion, to some extent 20:46:47 Yeah, playing with that now. 20:47:21 and generally, know if any piece of data is supposed to be bytes or unicode 20:47:40 and try to only deal with bytes when doing I/O 20:48:08 It's not that I don't know, it's that Python2's insistence on the u prefix for all real strings is apparently impossible for me to enforce on myself. 20:49:01 ah 20:49:19 from __future__ import unicode_literals on 2.x may help 20:49:37 ...why am I not already using that? 20:49:43 it makes u the default 20:49:47 b'foo' if you want bytes 20:49:54 Yeah, that would be *awesome*. 20:50:02 All right, fuck all this shit forever, let's try just doing that. 20:50:07 try with that before porting 20:50:48 # coding: utf8 20:50:50 from __future__ import division, unicode_literals 20:50:54 all my files start basically like this 20:51:50 you may want 'from __future__ import absolute_import' too, but I find it less essential 20:53:09 http://docs.python.org/2/library/__future__.html 20:54:38 All right, so all input from file reading is bytes until I explicitly decode, right? 20:57:12 eh, depends 20:57:33 if you want bytes, use open(name, 'rb') 20:58:21 you can also get unicode-mode files: import io; io.open(name, encoding='utf-8') 20:58:52 MaRakow has joined #CSS 20:58:59 Sorry, didn't actually mean "bytes" there, just "Python 2 normal strings". 20:59:10 But I didn't know about unicode-mode files! 20:59:12 define normal? :) 20:59:20 MaRakow has joined #CSS 20:59:55 hober has joined #css 21:00:01 On 2.x, the default string type 'str' contains bytes, 'unicode' is code points 21:00:09 Yeah. 21:00:48 on 3.x, 'str' is code points and there is a new 'bytes' type that’s an immutable array of 8bit integers 21:00:59 on 2.x, 'bytes' is an alias for 'str' 21:01:15 yeah, it’s a mess 21:02:52 Okay, that is waht I was saying, then. 21:02:57 unicode_literals doesn't change the behavior of open(), right? You still get a str object when you do a read()? 21:03:05 it doesn’t 21:03:18 k, switching to io.open as well, then. 21:04:04 open() on 3.x is io.open 21:04:09 Yeah. 21:04:30 on 2.x, open() without 'b' in the mode converts various newlines to '\n' 21:07:08 jet has joined #css 21:07:09 rhauck has joined #css 21:09:48 rhauck has joined #css 21:26:46 liam_ has joined #css 21:30:28 dauwhe has joined #css 21:38:38 dauwhe has joined #css