IRC log of css on 2014-10-22

Timestamps are in UTC.

01:18:27 [gsnedders]: Someone should get libxml2 following HTML now the spec is pretty stable
01:48:10 [SimonSapin]: "Someone" :)
01:52:51 [gsnedders]: :)
02:04:01 [jdaggett]: jdaggett has joined #css
02:32:31 [liam]: gn it does follow HTML. Look, it's years behind! :-)
03:40:00 [jet]: jet has joined #css
04:27:50 [tantek]: tantek has joined #css
06:12:18 [jet]: jet has joined #css
07:55:40 [glazou]: glazou has joined #css
08:45:03 [lajava]: lajava has joined #css
09:18:14 [antonp]: antonp has joined #css
09:24:28 [Ms2ger]: Ms2ger has joined #css
11:21:15 [darktears]: darktears has joined #css
12:03:54 [plh]: plh has joined #css
12:30:16 [Ms2ger]: Ms2ger has joined #css
12:34:49 [tantek]: tantek has joined #css
13:32:42 [dbaron]: dbaron has joined #css
15:14:22 [nvdbleek]: nvdbleek has joined #css
15:14:37 [glazou]: glazou has left #css
15:30:07 [ArronEi]: ArronEi has joined #css
15:31:09 [glazou]: glazou has joined #css
15:31:40 [Zakim]: Zakim has joined #css
15:31:55 [glazou]: Zakim, this will be Style
15:31:55 [Zakim]: ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 29 minutes
15:32:02 [glazou]: RRSAgent, make logs public
15:32:08 [jet]: jet has joined #css
15:32:16 [glazou]: glazou has changed the topic to: http://lists.w3.org/Archives/Public/www-style/2014Oct/0375.html
15:55:14 [glazou]: glazou has joined #css
15:55:24 [glazou]: Zakim, code?
15:55:24 [Zakim]: the conference code is 78953 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), glazou
15:56:28 [AH_Miller]: AH_Miller has joined #CSS
15:56:50 [Zakim]: Style_CSS FP()12:00PM has now started
15:56:57 [Zakim]: + +1.253.307.aaaa
15:57:02 [ArronEi]: zakim, aaaa is me
15:57:03 [Zakim]: +ArronEi; got it
15:57:05 [adenilson]: adenilson has joined #css
15:57:06 [dael]: dael has joined #css
15:57:17 [Zakim]: +MikeMiller
15:57:56 [Zakim]: +dael
15:58:12 [Zakim]: + +33.1.39.21.aabb
15:58:20 [Zakim]: -MikeMiller
15:58:24 [glazou]: Zakim, aabb is me
15:58:24 [Zakim]: +glazou; got it
15:58:40 [Zakim]: +MikeMiller
15:59:08 [bradk]: bradk has joined #css
15:59:09 [Zakim]: +[Microsoft]
15:59:18 [Zakim]: +SGalineau
15:59:24 [Zakim]: +??P15
15:59:29 [Zakim]: +??P16
15:59:36 [adenilson]: Zakim, ?P15 is me.
15:59:36 [Zakim]: sorry, adenilson, I do not recognize a party named '?P15'
15:59:47 [Zakim]: -??P16
15:59:49 [adenilson]: Zakim, ??P15 is me.
15:59:49 [Zakim]: +adenilson; got it
15:59:53 [Zakim]: +BradK
16:00:19 [smfr]: smfr has joined #css
16:00:52 [Zakim]: + +1.631.398.aacc
16:01:26 [Zakim]: +smfr
16:01:38 [antenna]: antenna has joined #css
16:01:41 [Zakim]: +??P27
16:02:00 [Zakim]: -[Microsoft]
16:02:24 [glazou]: Zakim, who in on the phone?
16:02:24 [Zakim]: I don't understand your question, glazou.
16:02:28 [Zakim]: +Bert
16:02:32 [glazou]: Zakim, who is on the phone?
16:02:33 [Zakim]: On the phone I see ArronEi, dael, glazou, MikeMiller, SGalineau, adenilson, BradK, +1.631.398.aacc, smfr, ??P27, Bert
16:02:59 [Zakim]: +plinss
16:03:06 [Zakim]: +[IPcaller]
16:03:10 [koji]: koji has joined #css
16:03:11 [fantasai]: Zakim, IPcaller is me
16:03:11 [Zakim]: +fantasai; got it
16:03:15 [gregwhitworth]: gregwhitworth has joined #css
16:03:42 [Zakim]: + +1.281.305.aadd
16:03:50 [Zakim]: + +1.425.301.aaee
16:04:04 [Zakim]: +hober
16:04:20 [dael]: Zakim, aaee is rossen
16:04:20 [Zakim]: +rossen; got it
16:04:30 [dael]: glazou: Let's start. We have a few regrets.
16:04:34 [Zakim]: +koji
16:04:34 [Keshav]: Keshav has joined #css
16:04:38 [dael]: glazou: Are there extra items?
16:04:47 [dbaron]: my SIP client isn't working right now, so unable to join
16:04:48 [dael]: Topic: Animations Issues
16:04:58 [glazou]: dbaron, ACK
16:05:01 [dael]: sylvaing: I want to make sure we have the right people.
16:05:17 [Zakim]: +??P39
16:05:22 [SteveZ]: SteveZ has joined #css
16:05:28 [dael]: sylvaing: During Sophia we agreed to let animation prop effect running animations so if your animation is running and you change the timing or what not it has an immediat effect.
16:05:34 [antonp]: Zakim, ??P39 is me
16:05:35 [Zakim]: +antonp; got it
16:05:45 [dael]: sylvaing: OUtstanting is what happens when you update an anmation in a @keyframe
16:05:47 [Zakim]: +SteveZ
16:06:01 [vollick]: vollick has joined #css
16:06:07 [Zakim]: +[Microsoft]
16:06:13 [dael]: sylvaing: TabAtkins was of the opinion it ignore them and that's fine with me. You end up in a tricky area. I can't find any real minutes or e-mail thread suggesting concensus.
16:06:26 [dael]: sylvaing: If people don't object I'll document it, but I want to double check.
16:06:29 [dael]: glazou: Opinions?
16:06:48 [dael]: sylvaing: So inside a @keyframe the only animation prop that has an effect is timing. The others are ignored.
16:07:01 [dael]: TabAtkins: And it doesn't do what it normally does inside, it's just between keyframes.
16:07:26 [Zakim]: + +1.408.881.aaff
16:07:40 [dael]: ??: So this is prop that effect animations, not changing the keyframes.
16:07:47 [TabAtkins]: s/??/smfr/
16:07:52 [dael]: sylvaing: So it's can a keyframe rule change a running animation property.
16:08:12 [dael]: sylvaing: So we covered what it means to chnge when an animation running, the only leftover part is when you have a @keyframe rule.
16:08:16 [dael]: smfr: Sounds fine.
16:08:24 [dael]: glazou: Seems resolveable.
16:08:48 [dael]: RESOLVED: amination properties don't apply inside keyframe rules except animation timing function (where we have text already)
16:08:55 [dino]: dino has joined #css
16:09:05 [dael]: sylvaing: Next issue
16:09:05 [sylvaing__]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25344
16:09:10 [dael]: sylvaing__: This bug above
16:09:33 [dael]: sylvaing__: It's a non-issue. When you have a keyframes objects for an @rule, today you can set the name of the keyframe rule to none.
16:09:49 [dael]: sylvaing__: THat's not a good keyword. The question was should we throw, I think yes.
16:10:21 [dael]: sylvaing__: This isn't controversial, I think. Unless someone thinks of an exception.
16:10:27 [dael]: smfr: Is none the only special value?
16:10:34 [dael]: sylvaing__: For the name of a keyframes rule?
16:10:47 [dael]: smfr: I can imagine infinate or inheret which would be a bad time
16:10:55 [dael]: sylvaing__: So the usual global keywords would throw.
16:11:01 [dael]: sylvaing__: Fair point.
16:11:13 [dael]: ???: Haven't we in the past req. keyframes to be quoted?
16:11:21 [ArronEi]: ??? is Arronei
16:11:22 [dael]: smfr: The original spec had, but we removed that.
16:11:24 [dino]: s/???/dino/
16:11:31 [dino]: oops!
16:11:47 [dael]: sylvaing__: So you can say if you want to use inheret you can quote it, but if you don't quote it, what happens? You can't set to that.
16:11:57 [dael]: smfr: So is it valid when you're passing the first time?
16:12:05 [dael]: glazou: What about counter names?
16:12:11 [dael]: TabAtkins: Explicitly disallowed.
16:12:16 [dael]: glazou: So I say we do that.
16:12:24 [dael]: TabAtkins: You get that for fre if you ref custom-idents.
16:12:29 [dael]: sylvaing__: Okay. THat works.
16:12:38 [dael]: plinss: Does custom-odent spec the OM?
16:12:42 [smfr]: http://dev.w3.org/csswg/css-values/#custom-idents
16:12:50 [dael]: TabAtkins: No so much, but if you check the grammer for the animation name you get there.
16:13:11 [dael]: sylvaing__: I'll clarify in the prose spec. So if I do @keyframe and "none" does that work?
16:13:20 [dael]: TabAtkins: No, it doesn't match the keyframes grammer
16:13:23 [dael]: sylvaing__: You're right.
16:13:39 [dael]: sylvaing__: So.... when I set it in the OM, the named prop to none, it still throws.
16:13:41 [dael]: TabAtkins: Yeah.
16:13:50 [dael]: TabAtkins: Anything that prevents reserializing it.
16:14:08 [gregwhitworth]: can that be minuted
16:14:18 [TabAtkins]: zakim, who's making noise?
16:14:22 [dino]: that was me!
16:14:25 [dino]: not me though
16:14:31 [Zakim]: TabAtkins, listening for 11 seconds I heard sound from the following: glazou (27%), SGalineau (44%), TabAtkins (14%)
16:14:32 [dino]: colleagues talking about star wars shit
16:14:44 [dbaron]: dbaron has joined #css
16:15:04 [sylvaing__]: RESOLVED: keywords are invalid @keyframes names and will throw when set through the OM
16:15:16 [dael]: sylvaing__: Next one.
16:15:17 [sylvaing__]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25034
16:15:26 [dbaron]: Zakim, code
16:15:26 [Zakim]: I don't understand 'code', dbaron
16:15:27 [dael]: sylvaing__: This came from an e-mail from glazou
16:15:27 [dbaron]: Zakim, code?
16:15:28 [Zakim]: the conference code is 78953 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), dbaron
16:15:48 [dael]: sylvaing__: It was deleteRule/findRule. What happens when milti rules containt the same key?
16:15:57 [Zakim]: +David_Baron
16:16:06 [dael]: sylvaing__: The API today assumes that there is one. In practice browsers apply a rule to the last one
16:16:22 [dael]: glazou: The problem is diff from delete and find. WE may have to change find but fix delete
16:16:25 [dbaron]: network completely stopped working, rebooting didn't fix it, and then it just magically started working again
16:16:31 [dael]: sylvaing__: From my testing they find and delete the last one.
16:16:41 [dael]: glazou: I'mnot sure if this is what the user would expect.
16:17:04 [dael]: sylvaing__: It makes sense before. You would find or delete the last one. Now that there's cascading across rules it may not find or delete everything.
16:17:21 [dael]: sylvaing__: A find rule may give an incomplete desc or you may think you delete everything.
16:17:29 [dael]: sylvaing__: So today it's find and delete the last one
16:17:50 [dael]: glazou: smfr's question in CSS: CSS WG got the OM from DOM long ago. WE were long ago going to add the OM pieces.
16:17:58 [dael]: sylvaing__: And this is the OM in Animations spec.
16:18:19 [dael]: smfr: I guess I understand. I thought we had a longer goal to rewrite the OM, will it still work after we re-write?
16:18:41 [dael]: sylvaing__: I agree we may want to clen in the future. I suggest for lvl 1 we should agree on what to interop on.
16:19:02 [dael]: sylvaing__: I think the behavior is reasonable for find.
16:19:13 [dael]: smfr: It seems to be current functions are insuffiecent.
16:19:20 [dael]: TabAtkins: They are, but that was org spec and impl.
16:19:27 [dael]: smfr: So we're not going to change, just define.
16:19:53 [dael]: sylvaing__: And it used to be reasonable, it's just more awkward now that we cascade across rules. It's not ideal, but we desc what browsers do.
16:20:10 [dael]: sylvaing__: So saying delete/find rule apply to the last of that rule?
16:20:19 [dael]: smfr: So how does that work.??
16:20:44 [dael]: sylvaing__: So right now it is a seperate issue. In browsers today you see the first one as the second is thought of as a sep item.
16:20:52 [dael]: TabAtkins: Original spec OM was a hot mess, basically.
16:21:00 [dael]: sylvaing__: It was oversymplistic
16:21:09 [dael]: smfr: Can we add a note to the spec that desc this issue?
16:21:13 [dael]: sylvaing__: I can do that.
16:21:13 [dino]: more detail: "50%" is different from "50%, 60%" and might even be different from "50%,60%" (no space)
16:21:25 [dael]: smfr: I think it should be for authors so they know we understand there's this issue.
16:21:39 [dbaron]: I don't understand what " RESOLVED: keywords are invalid @keyframes names and will throw when set through the OM" means
16:21:50 [dael]: glazou: I think smfr question is important to add a note. An editor will rely on findRule, so please do the note.
16:22:03 [dael]: TabAtkins: The occational thing where we say it's not great behav but it's legacy.
16:22:18 [dael]: sylvaing__: Let me resolve this and then answer dbaron's IRC question
16:22:25 [sylvaing__]: RESOLVED: findRule/deleteRule return/delete the last rule with the specified key
16:22:30 [dino]: dbaron, i think the resolution was that setting keyframes rule name to "inherit" via the OM will do nothing other than throw an exception
16:22:40 [alex_antennahouse]: alex_antennahouse has joined #css
16:23:01 [dael]: sylvaing__: So dbaron what this means is that if you retreve the keyframes rule for the OM and set it's name prop to a keyword like none, they think it's a name like any other. And this means it should fail.
16:23:06 [dael]: dbaron: And does parsing fail?
16:23:16 [dael]: sylvaing__: Yes. It's a custom-ident based fail.
16:23:27 [dael]: sylvaing__: that's all I had for today.
16:23:53 [dael]: sylvaing__: We'll have more for the F2F and we'll be pretty much done. The one that's left and I would love input is the one from Sophia which had tests everyone ran.
16:23:56 [Zakim]: +[IPcaller]
16:24:03 [dael]: sylvaing__: That one is tricky. Any input is welcome.
16:24:10 [dael]: dbaron: I'm not sure which one you mean..
16:24:18 [alex_antennahouse]: apologies for lateness I'm IPcaller
16:24:24 [tantek]: tantek has joined #css
16:24:43 [dael]: sylvaing__: The one you sent all the alternatives on multiple animations running concerently. You had the list A-G and alpha and beta. WE resolved to G Beta, but what that means in spec prose is trickier.
16:24:45 [glazou]: Zakim, [IPcaller] hax alex_antennahouse
16:24:45 [Zakim]: I don't understand '[IPcaller] hax alex_antennahouse', glazou
16:24:55 [dael]: sylvaing__: That's it for today.
16:25:00 [dael]: Topic: Text
16:25:04 [glazou]: Zakim, [IPcaller] has alex_antennahouse
16:25:04 [Zakim]: +alex_antennahouse; got it
16:25:06 [Zakim]: -dino
16:25:08 [glazou]: https://lists.w3.org/Archives/Member/w3c-css-wg/2014OctDec/0073.html
16:25:20 [dael]: koji: Yeah. fantasai?
16:25:32 [dael]: glazou: Just one thing, I'd like to leave the last 10 minutes for TPAC convo
16:25:55 [dael]: koji: So fantasai and I discussed this and we disagree so we need the WG opinions
16:26:02 [koji]: https://wiki.csswg.org/spec/text-justify-auto#future-possibilities
16:26:08 [dael]: koji: Looking at the table from the last F2F (above)
16:26:48 [dael]: koji: WE have the options listed there. fantasai point is that C option is really bad. She finds it unacceptable and should be avoided at any cost.
16:27:01 [dael]: koji: I don't think it's that bad. I'd rather less docs and authors being affected.
16:27:18 [dael]: fantasai: The issue is Koji wanted clarification on what data we're going to collect and how that impacts our decision
16:27:30 [dael]: fantasai: I thought we look for what can/can't people live with
16:28:02 [dael]: fantasai: I understood that if the Japanese don't want large spaces because it make it ugly. Korean we're not sure about if it's okay to treat Han and Hangul diff. Does that make odd spacing
16:28:10 [dael]: fantasai: Let me paste...
16:28:39 [dael]: fantasai: There was a thing and I can't remember where.
16:28:41 [smfr]: pastebin?
16:29:17 [Zakim]: -glazou
16:29:23 [SteveZ]: s/thng/place for code snippets/
16:29:23 [glazou]: Zakim, code?
16:29:23 [Zakim]: the conference code is 78953 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), glazou
16:29:24 [fantasai]: http://pastebin.mozilla.org/6853299
16:29:28 [dael]: fantasai: Here we are
16:29:33 [Zakim]: -adenilson
16:29:44 [glazou]: Zakim add a hickup
16:29:56 [dael]: fantasai: The question we need to ask is does creating spaces between Han and not Hangul create wierd parsing of Korean or does it look awk.
16:29:59 [Zakim]: +glazou
16:30:08 [dael]: fantasai: The way having large spaces in Japanese would look awk.
16:30:16 [dael]: fantasai: That's my understanding of the key question
16:30:20 [Zakim]: +??P15
16:30:28 [adenilson]: Zakim, ??P15 is me.
16:30:28 [Zakim]: +adenilson; got it
16:30:37 [dael]: koji: I understand that. I think asking if it's acceptable or ugly to end users will fail. How bad is hard to figure out by interviewing users
16:30:57 [dael]: koji: What we're asking is to help us...how do we determine this as a WG?
16:31:51 [dael]: koji: One idea that came from our discussion was would be to ask companies how badly thier product does for justification behavior, but other ideas would be appricitated.
16:32:15 [dael]: ??: I can say that the current webkit behavior is what we've been asked to have and we don't have any bugs from Korean users
16:32:19 [dael]: koji: Okay. Great.
16:32:30 [fantasai]: s/??/hober/
16:33:04 [dael]: hober: It's worth noting that the web corpus for Korean isn't similar to historical. If the default is good for moderna nd there's a way to tag historical, that's the best we can do
16:33:25 [dael]: koji: I understand. A behavior that I'm worrying about isn't webkit. fantasai?
16:34:05 [dael]: fantasai: I'd like to hear from actual Korean people. Cases where this will be noticed isn't really common. You need narrow lines or a large word that wraps. That's going to be more common on mobile, but isn't common in general.
16:34:52 [dael]: fantasai: It's important to understand is it as bad if you put random justification somewhere in the word. Is it going to effect wehre spaces are intp and where word boundries are, that's more important than if a space is slightly bigger than ideal.
16:35:01 [bradk]: bradk has joined #css
16:35:02 [fantasai]: s/justification space/
16:35:08 [fantasai]: s/in the word/in the middle of a word/
16:35:19 [dael]: koji: This issue itself isn't about webcompat only. We're asking authors to explain what to do. If we're not breaking many doc, is that something we would choose?
16:35:39 [koji]: s/webcompat/backward-compat/
16:36:04 [Ms2ger]: Ms2ger has joined #css
16:36:27 [dael]: fantasai: You're like, well, we're only going to break some doc in Korean which is less important than making more doc in Japaense look right. I think we should get a minimum of this isn't broken. Your saying lets break one thing to make other things look better, I'm saying break nothing even if it makes everything look worse overall.
16:36:28 [Zakim]: -rossen
16:36:34 [tantek]: regrets for missing TPAC f2f - I am co-chairing the #social web WG.
16:36:36 [dael]: fantasai: We're supposed to get information
16:36:42 [dael]: koji: Why no webkit compalints?
16:36:50 [dael]: fantasai: Maybe they didn't notice.
16:36:59 [dael]: koji: But if they didn't notice it's not a big problem, is it?
16:37:28 [dael]: fantasai: If I put spaces in the middle of an english word so it looks badly erned, most users won't notice, but it's still very wrong.
16:37:37 [fantasai]: s/erned/kerned/
16:37:46 [dael]: fantasai: If you come up witha case where that space gets larger, it becomes a problem for readability.
16:38:20 [dael]: fantasai: What do you want to know from the WG? I think we need to know from Korean people if this is an okay place to put spaces or is this as bad as putting a space between a suffix and the rest of a word.
16:38:43 [dael]: glazou: I still have a lot of good contacts in Korea. If you want to send me an email I can forward so they can answers.
16:38:46 [dael]: fantasai: OKay.
16:39:13 [dael]: koji: What I'm saying is that if we ask users about how bad this is, is it unaccaptable or just ugly, that's not the right way to investigate.
16:39:29 [dael]: koji: Only could say ugly or inacceptable to the same thing, it's just how they think it.
16:39:53 [Zakim]: +rossen
16:40:01 [dael]: glazou: I don't really understand, Koji. pinging the users about impact is always good.
16:40:23 [dael]: hober: When we discussed in Sophia we ended up in a reasonable place without the feedback. I don't think anything has changed, we want that feedback.
16:40:29 [dael]: glazou: So what are the next steps?
16:40:44 [dael]: fantasai: I have an e-mail I just need to tweek before I send it to you to be forwarded.
16:40:53 [dael]: glazou: I'm not sure I'll get an answer, but I can forward.
16:41:14 [dael]: fantasai: I don't know what koji wants, I think he wants to not ask the uses because he doesn't think they will give good feedback.
16:41:37 [dael]: koji: If the question is yes or no or compared to something it's okay. If it's is this ugly or unacceptable I think it's inaccurate.
16:41:49 [dael]: fantasai: That's why I phrased with comparisions to english and japanese.
16:42:00 [dael]: koji: I got different feelings from that. The difference is subtile.
16:42:09 [fantasai]: s/tile/tle
16:42:27 [dael]: koji: Am I wrong? Regarding investigating?
16:42:33 [fantasai]: 1. Don't ask anyone from Korea to help
16:42:44 [fantasai]: 2. Come up with a question and do our best to get the information
16:42:50 [dael]: fantasai: I think the actions options are (above)
16:43:01 [dael]: fantasai: You're saying do 1 because the best isn't good enough to be worthwhile.
16:43:23 [dael]: koji: ask Korean natives?
16:44:06 [dael]: fantasai: We need to ask someone who isn't Japanese. We have a bias because there's lots of opinions from Japanese speakers, but no Korean. I don't care who we ask, but if you're arguing we don't talk to anybody it doesn't make sense.
16:44:14 [dael]: koji: We had started asking companies.
16:44:38 [dael]: glazou: I'm not sure this is going anywhere. fantasai you send me an e-mail and we give them a week to answer. If we get a useful answer fine. If not we do otherwise.
16:44:45 [dael]: glazou: Anything else on this issue in Text?
16:45:17 [dael]: koji: WE're discussing this for a long time, after this and a few others are resolved, we want to take text to CR, so if there are other concerns they should state them.
16:45:29 [dael]: fantasai: We have to go through LC again, but there should be no changes beyond that.
16:45:34 [dael]: glazou: Okay. Thank you.
16:45:37 [dael]: Topic: TPAC
16:46:12 [dael]: glazou: I don't know if you have seen the request from Janina for a joint meeting Friday morning. That's outside our two days, so anyone willing to attend, please do so
16:46:35 [dael]: glazou: We have a bunch of observer requests. It seems our agenda will be packed with joint meetings, but we don't have a lot of offical items.
16:46:45 [bradk]: bradk has joined #css
16:46:59 [dael]: glazou: It looks like most of us will arrive Sunday evening. So let's have plans together by Sunday evening. ANy questions about TPAC?
16:47:29 [dael]: fantasai: Flexbox LC ends at the end of this week, so if you have feedback please try and put it together. If you need mroe time, please let us know.
16:47:36 [dael]: rossen: Which module?
16:47:44 [dael]: fantasai: Flexbox. So get your feedback together.
16:47:52 [dael]: glazou: Anything else?
16:48:07 [fantasai]: fantasai^: We were looking in particular for compat feedback on the flex-basis: auto/main-size issue
16:48:15 [dael]: SteveZ: Any idea of what topics on what days? I have a Tuesday prob so I'd like layout on Monday.
16:48:53 [dael]: glazou: Given the number of TPAC constraints, I'd appriciate if they can go on the wiki. I'm asking everyone to put their name on the participants list on the wiki. Right now there's only 6 or 8 people. That will help us monitor who is here when.
16:48:56 [dael]: glazou: Anything else?
16:49:05 [Zakim]: -hober
16:49:13 [Zakim]: -SGalineau
16:49:14 [dael]: glazou: OK. I guess this is all today. Safe flight to anyone flying and I'll see you there!
16:49:15 [Zakim]: -smfr
16:49:15 [Zakim]: -David_Baron
16:49:17 [Zakim]: -[Microsoft]
16:49:17 [Zakim]: -ArronEi
16:49:18 [Zakim]: -SteveZ
16:49:18 [Zakim]: -adenilson
16:49:20 [Zakim]: -glazou
16:49:21 [Zakim]: -[IPcaller]
16:49:21 [Zakim]: -fantasai
16:49:22 [Zakim]: -rossen
16:49:22 [Zakim]: -??P27
16:49:23 [Zakim]: -MikeMiller
16:49:23 [Zakim]: -koji
16:49:24 [Zakim]: -dael
16:49:24 [Zakim]: -TabAtkins
16:49:25 [smfr]: smfr has left #css
16:49:27 [Zakim]: -plinss
16:49:29 [Zakim]: - +1.631.398.aacc
16:49:30 [Zakim]: -antonp
16:50:02 [Zakim]: -Bert
16:50:30 [Bert]: -> https://www.w3.org/2002/09/wbs/35125/TPAC2014/registrants#CSS registered particpants
16:51:43 [glazou]: Bert: yes but no hotel/flight info
16:58:19 [adenilson]: plinss: ping?
16:59:46 [plinss]: adenilson: pong
17:00:39 [adenilson]: plinss: hi there. I’m trying to edit the TPAC wiki page to add my name on the participants list but it seems that my user doesn’t have edit access.
17:00:57 [plinss]: reload the page, you should have access now
17:01:08 [adenilson]: Would you mind to check if it is missing the magical edit bit flag?
17:01:12 [adenilson]: ah, coolio. Let me try.
17:01:22 [adenilson]: yay!
17:01:25 [adenilson]: plinss: thanks man.
17:01:28 [glazou]: thanks plinss :)
17:01:29 [plinss]: np
17:05:01 [Zakim]: disconnecting the lone participant, BradK, in Style_CSS FP()12:00PM
17:05:02 [Zakim]: Style_CSS FP()12:00PM has ended
17:05:02 [Zakim]: Attendees were +1.253.307.aaaa, ArronEi, MikeMiller, dael, +33.1.39.21.aabb, glazou, [Microsoft], SGalineau, adenilson, BradK, +1.631.398.aacc, smfr, Bert, plinss, fantasai,
17:05:03 [Zakim]: ... +1.281.305.aadd, +1.425.301.aaee, hober, TabAtkins, rossen, koji, antonp, SteveZ, +1.408.881.aaff, dino, David_Baron, alex_antennahouse
17:47:27 [nvdbleek]: nvdbleek has joined #css
18:30:38 [Zakim]: Zakim has left #css
18:48:48 [liam]: liam has joined #css
18:51:00 [jet]: jet has joined #css
19:13:15 [nvdbleek]: nvdbleek has joined #css
20:00:24 [lajava]: lajava has joined #css
20:03:56 [stryx`]: stryx` has joined #css
20:11:34 [jet]: jet has joined #css
20:38:27 [darktears]: darktears has joined #css
20:45:30 [adenilson]: adenilson has joined #css
20:46:38 [jet]: jet has joined #css
21:35:17 [lajava]: lajava has joined #css
21:39:34 [tantek]: tantek has joined #css
21:53:18 [tantek]: tantek has joined #css
22:08:51 [sylvaing__]: TabAtkins: if I want to link to http://dev.w3.org/csswg/css-values/#common-keywords from css-animations, is there a Bikeshed syntax?
22:18:19 [tantek]: tantek has joined #css
22:18:35 [liam]: liam has joined #css
22:32:58 [ArronEi]: ArronEi has joined #css
22:56:45 [TabAtkins]: sylvaing__: Not *yet*. There will be, and it will look like [[css-values#common-keywords]]. But cross-spec heading linking isn't in yet.
23:01:22 [sylvaing__]: TabAtkins: cool; so <a href>
23:01:28 [TabAtkins]: Yes.
23:01:43 [TabAtkins]: And sorry I haven't gotten to that yet; it'll be cool when I do. ^_^
23:02:12 [sylvaing__]: oh no worries
23:47:42 [sylvaing__]: of course I'll link to the ED #bwahahaha