Options:
- # Session Start: Wed Nov 30 00:00:00 2011
- # Session Ident: #css
- # [00:11] * Quits: arno (arno@192.150.10.200) (Ping timeout)
- # [00:18] * Joins: arno (arno@192.150.10.200)
- # [00:41] * Quits: drublic (drublic@93.132.250.133) (Client exited)
- # [01:08] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [01:09] * Joins: arno (arno@192.150.10.200)
- # [01:13] * Quits: miketaylr (miketaylr@24.42.93.245) (Quit: miketaylr)
- # [01:26] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [01:45] * Quits: plinss (plinss@98.176.133.137) (Ping timeout)
- # [01:57] * Quits: dbaron (dbaron@159.63.23.38) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [02:31] * Quits: pjrm (pmoulder@130.194.69.10) (Ping timeout)
- # [02:31] * Quits: stearns (anonymous@192.150.22.5) (Ping timeout)
- # [02:32] * Joins: pjrm (pmoulder@130.194.69.10)
- # [02:36] * Joins: ksweeney (Adium@74.72.160.128)
- # [02:52] * Parts: ksweeney (Adium@74.72.160.128)
- # [03:04] * Joins: plinss (plinss@98.176.133.137)
- # [03:35] * Quits: plinss (plinss@98.176.133.137) (Ping timeout)
- # [03:35] * Joins: plinss (plinss@98.176.133.137)
- # [03:40] * Quits: karl (karlcow@128.30.54.58) (Quit: Freedom - to walk free and own no superior.)
- # [04:24] * Quits: plinss (plinss@98.176.133.137) (Ping timeout)
- # [04:24] * Joins: plinss (plinss@98.176.133.137)
- # [04:26] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [04:28] * Joins: plinss_ (plinss@98.176.133.137)
- # [04:29] * Quits: plinss (plinss@98.176.133.137) (Ping timeout)
- # [04:29] * plinss_ is now known as plinss
- # [04:29] * Joins: stearns (anonymous@50.132.63.33)
- # [04:59] * Quits: plinss (plinss@98.176.133.137) (Ping timeout)
- # [04:59] * Joins: plinss (plinss@98.176.133.137)
- # [05:47] * Joins: dbaron (dbaron@173.228.28.129)
- # [06:05] * Joins: danielfilho_ (danielfilh@187.31.77.7)
- # [06:06] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [06:06] * danielfilho_ is now known as danielfilho
- # [08:42] * Quits: dbaron (dbaron@173.228.28.129) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [09:40] * Quits: brianman (brianman@131.107.0.94) (Ping timeout)
- # [09:41] * Joins: brianman (brianman@131.107.0.126)
- # [10:26] * Joins: drublic (drublic@77.2.144.198)
- # [10:36] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [10:59] <drublic> anyone of you responsible for the css validator? http://jigsaw.w3.org/css-validator/ if you try to validate `box-shadow: 0 1px 2px #000` there is an error: 0 is not a valid value, you might check this fiddle: http://fiddle.jshell.net/drublic/WM2eL/5/show/light/
- # [11:00] <drublic> to me this seems to be a bug
- # [11:09] * Joins: florianr (florianr@213.236.208.22)
- # [11:25] * Parts: anne (annevk@83.85.115.123)
- # [11:51] * Joins: karl (karlcow@128.30.54.58)
- # [13:54] * Joins: arronei_ (arronei@131.107.0.113)
- # [13:55] * Quits: arronei (arronei@131.107.0.83) (Ping timeout)
- # [14:10] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [14:10] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [14:15] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [14:15] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [15:06] * Joins: miketaylr (miketaylr@206.217.92.186)
- # [15:44] * Quits: drublic (drublic@77.2.144.198) (Client exited)
- # [15:44] * Joins: drublic (drublic@77.2.144.198)
- # [16:41] <fantasai> drublic: Post in http://lists.w3.org/Archives/Public/www-validator/2011Nov/ ? We don't maintain the validator here, just the specs. :)
- # [16:42] <drublic> fantasai: thank you
- # [16:42] <paul_irish> s/www-validator/ccc-validator
- # [16:43] <fantasai> drublic: Sorry, http://lists.w3.org/Archives/Public/www-validator-css/ is the right address
- # [16:44] <fantasai> drublic: and here's the bug tracker... http://www.w3.org/Bugs/Public/buglist.cgi?product=CSSValidator
- # [16:46] <drublic> fantasai: great. i'll file this laiter. thx again!
- # [16:46] <fantasai> thanks!
- # [16:52] * Joins: evan_ (qw3birc@128.30.52.28)
- # [16:53] * Parts: evan_ (qw3birc@128.30.52.28)
- # [17:04] * Joins: kojiishi (kojiishi@222.158.227.129)
- # [17:36] * Joins: glazou (glazou@82.247.96.19)
- # [17:36] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [17:36] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
- # [17:36] <RRSAgent> logging to http://www.w3.org/2011/11/30-css-irc
- # [17:37] <glazou> Zakim, this will be Style
- # [17:37] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 29 minutes
- # [17:37] <glazou> RRSAgent, make logs public
- # [17:37] <RRSAgent> I have made the request, glazou
- # [17:43] * Joins: arno (arno@192.150.10.200)
- # [17:43] * Joins: jdaggett (jdaggett@180.235.9.33)
- # [17:50] * Joins: sylvaing (sylvaing@131.107.0.82)
- # [17:52] * Joins: ericm (qw3birc@128.30.52.28)
- # [17:56] * Joins: dbaron (dbaron@173.228.28.129)
- # [17:56] * Joins: dstorey (qw3birc@128.30.52.28)
- # [18:00] * Joins: danielweck (danielweck@81.157.14.54)
- # [18:02] <Zakim> Style_CSS FP()12:00PM has now started
- # [18:02] <Zakim> +??P37
- # [18:02] * Joins: divya (qw3birc@128.30.52.28)
- # [18:02] <jdaggett> zakim, ++P37 is me
- # [18:02] <Zakim> sorry, jdaggett, I do not recognize a party named '++P37'
- # [18:02] <divya> are we on?
- # [18:03] <jdaggett> zakim, +??P37 is me
- # [18:03] <Zakim> sorry, jdaggett, I do not recognize a party named '+??P37'
- # [18:03] <Zakim> +??P39
- # [18:03] <glazou> Zakim, ??P39 is me
- # [18:03] <Zakim> +glazou; got it
- # [18:03] <jdaggett> zakim, ??p37 is me
- # [18:03] <Zakim> +jdaggett; got it
- # [18:03] <Zakim> +??P43
- # [18:04] <Zakim> +plinss
- # [18:04] <florianr> Zakim, I am ??P43
- # [18:04] <Zakim> +florianr; got it
- # [18:04] * Joins: antonp (50a94e63@64.62.228.82)
- # [18:04] <Zakim> +[Microsoft]
- # [18:04] <Zakim> +divya
- # [18:05] <sylvaing> Zakim, [Microsoft] has sylvaing
- # [18:05] <Zakim> +sylvaing; got it
- # [18:05] <glazou> Zakim, who is noisy?
- # [18:05] <Zakim> glazou, listening for 10 seconds I heard sound from the following: 6 (58%), divya (14%)
- # [18:05] <Zakim> +antonp
- # [18:05] * Joins: lhnz (lhnz@188.223.83.48)
- # [18:06] <Zakim> +stearns
- # [18:06] <Zakim> +[Microsoft.a]
- # [18:06] * Joins: TabAtkins_ (qw3birc@128.30.52.28)
- # [18:06] <Zakim> +kimberly
- # [18:06] * Joins: JohnJan (johnjan@131.107.0.81)
- # [18:06] * Joins: smfr (smfr@173.228.90.57)
- # [18:06] <Zakim> + +1.510.364.aaaa
- # [18:06] <JohnJan> zakim, microsoft has johnjan
- # [18:06] <Zakim> +johnjan; got it
- # [18:06] <fantasai> zakim, kimberly has fantasai
- # [18:06] <Zakim> +fantasai; got it
- # [18:06] <Zakim> +tabatkins_
- # [18:06] <Zakim> +Bert
- # [18:06] * Joins: kimberly (Kimberly@69.241.19.12)
- # [18:06] <Zakim> +dbaron
- # [18:07] <Zakim> +smfr
- # [18:07] * Bert aha, zakim knows me again :-)
- # [18:07] <Zakim> +??P70
- # [18:07] <danielweck> Zakim, ??P70 is me
- # [18:07] <Zakim> +danielweck; got it
- # [18:07] <glazou> Bert: welcome back :-D
- # [18:08] * Joins: oyvind (oyvinds@213.236.208.22)
- # [18:08] <Zakim> +howcome
- # [18:08] * Joins: vhardy (vhardy@192.150.10.201)
- # [18:08] * Joins: howcome (howcome@88.89.78.85)
- # [18:08] <Zakim> +Oliver_Goldman
- # [18:09] <plinss> zakim, who is noisy?
- # [18:09] <glazou> Zakim, who is noisy?
- # [18:09] <Zakim> plinss, listening for 10 seconds I heard sound from the following: 18 (8%)
- # [18:09] <Zakim> glazou, listening for 10 seconds I heard sound from the following: 18 (47%), glazou (18%), plinss (5%), tabatkins_ (90%)
- # [18:10] <divya> hahahah
- # [18:10] <Zakim> +[IPcaller]
- # [18:10] <Zakim> +??P22
- # [18:10] <kojiishi> zakim, ??p22 is me
- # [18:10] <Zakim> +kojiishi; got it
- # [18:10] <tantek> Zakim, IPcaller is tantek
- # [18:10] <Zakim> +tantek; got it
- # [18:10] <glazou> wow, this becomes impossible to listen too :-D
- # [18:10] <tantek> Zakim, mute tantek
- # [18:10] <Zakim> tantek should now be muted
- # [18:11] <danielweck> WTF ?
- # [18:11] * tantek will be away from IRC for a bit
- # [18:11] * sylvaing "I can hear dead people..."
- # [18:11] <danielweck> :)
- # [18:11] <divya> :D
- # [18:11] <TabAtkins_> ScribeNick: TabAtkins_
- # [18:12] <TabAtkins_> Topic: Unicode TR50 update
- # [18:12] * Quits: ed (ed@88.131.66.80) (Quit: ZNC - http://znc.sourceforge.net)
- # [18:12] <TabAtkins_> jdaggett: There was an item on Ed and Sylvain to report back.
- # [18:12] <TabAtkins_> smfr: Ted can't make it today.
- # [18:12] <TabAtkins_> jdaggett: But he said he would have an update by next week.
- # [18:13] <TabAtkins_> sylvaing: And I'm a bit busy with the next preview, but I'm hoping to have it soon.
- # [18:13] <TabAtkins_> plinss: Okay, defer to next week.
- # [18:13] <TabAtkins_> Topic: Remaining CSS3 Speech issues
- # [18:13] <danielweck> http://wiki.csswg.org/spec/css3-speech#issue-1
- # [18:13] <TabAtkins_> danielweck: This issue is contentious.
- # [18:13] <TabAtkins_> danielweck: Last I heard form the commenter was 29 Sep.
- # [18:14] <TabAtkins_> danielweck: I've sent two heads-up.
- # [18:14] <danielweck> http://www.w3.org/TR/css3-speech/#cue-props
- # [18:14] <Zakim> +SteveZ
- # [18:14] <TabAtkins_> danielweck: As far as I understand, the normative text regarding the use of decibels - I agreed we have an issue with normative vs informative text here.
- # [18:14] <TabAtkins_> danielweck: However, because of the lack of further discussion from the commenter, I'm not entirely sure what the correct position is regarding which statements are normative.
- # [18:15] * Joins: SteveZ (chatzilla@24.6.120.172)
- # [18:15] <TabAtkins_> danielweck: There are some problems with the informative statements we're making about the decibel levels from the output of speech synthesizers, so we need to remove that.
- # [18:15] <TabAtkins_> danielweck: So two question.
- # [18:15] <TabAtkins_> danielweck: One, what do we do if we don't get feedback?
- # [18:15] <TabAtkins_> danielweck: Two, in terms of the process, what happens if we decide to mark this particular issue part of the syntax at-risk? Not the entire property, just the decibel part.
- # [18:15] <TabAtkins_> danielweck: Does that require going back to WD, or what? How fixable are we?
- # [18:16] <TabAtkins_> fantasai: I'd say to do your best to address the person's feedback. Then record in the disposition of comments the comments and the changes you've made, and record that you haven't gotten a response from them.
- # [18:16] <TabAtkins_> fantasai: You've given them plenty of time and reminders. If they don't respond by the time we take the DoC to the director, he can still review their comments and check that you've addressed them.
- # [18:16] <danielweck> http://wiki.csswg.org/spec/css3-speech#issue-18
- # [18:17] <TabAtkins_> fantasai: Regarding marking something as at-risk, you can do that now. It doesn't require going back to WD.
- # [18:17] <TabAtkins_> danielweck: Second issue, issue 18. Not a blocking issue, just waiting for confirmation.
- # [18:17] <TabAtkins_> danielweck: I don't think they'd raise an objection if we completed without a confirmation.
- # [18:18] <TabAtkins_> danielweck: So in terms of timeframe, what's a reasonable or typical timeframe when writing the call for implementation?
- # [18:18] <TabAtkins_> fantasai: The timeframe for CR is generally taken as a minimum. Usually a six-month minimum, but usually it takes longer than that to get the testsuite and the impl reports, etc.
- # [18:19] <TabAtkins_> fantasai: With regards to the transition, the comment period has closed. If you don't get a response at all in a week or two, I think it's fair to say that's long enough to either respond or request additional time for investigation.
- # [18:19] <TabAtkins_> danielweck: Okay.
- # [18:20] <TabAtkins_> danielweck: My status as a contributor to the spec in the coming year - we want to work with the spec through CR, including making the testsuite, etc.
- # [18:20] <TabAtkins_> danielweck: But I'm not entirely sure who'll be handling the impl reports, liaising with browsers, etc.
- # [18:20] <TabAtkins_> fantasai: I think that's fine. We should probably ask the epub folks to look for somebody to own the testsuite.
- # [18:20] <TabAtkins_> danielweck: I'm in the epub and that's our plan too.
- # [18:21] <plinss> http://lists.w3.org/Archives/Public/www-style/2011Nov/0735.html
- # [18:21] <TabAtkins_> Topic: New draft of Japanese Text Layout spec
- # [18:21] <TabAtkins_> plinss: If you have any interest, please look at it and give feedback. They're looking for comments by the end of the year.
- # [18:21] <TabAtkins_> jdaggett: Is there a list of changes?
- # [18:21] <TabAtkins_> florianr: Agreed, it's a long document.
- # [18:22] <TabAtkins_> [several]: No clue what the changes are.
- # [18:22] <TabAtkins_> jdaggett: I sent a message to Richard asking for that.
- # [18:22] <TabAtkins_> kojiishi: I talked to Richard and not sure how that went.
- # [18:22] <TabAtkins_> plinss: Perhaps reply online?
- # [18:22] <glazou> Zakim, who is noisy?
- # [18:22] <TabAtkins_> szilles: Even a diff against the old one, since it's structured the same.
- # [18:22] <Zakim> glazou, listening for 12 seconds I could not identify any sounds
- # [18:22] <fantasai> !?
- # [18:23] <glazou> thank you Zakim to let me know my ears get older
- # [18:23] <fantasai> http://wiki.csswg.org/ideas/radial-gradient-readability
- # [18:23] <TabAtkins_> Topic: Radial Gradient Readability
- # [18:23] <TabAtkins_> fantasai: At TPAC Tab and I decided to investigate the issue of making radial gradient syntax more readable, and more extnesible as a side-effect.
- # [18:24] <TabAtkins_> fantasai: We worked with other WG members to come up with a syntax which we posted to the blog, per our action item.
- # [18:24] <TabAtkins_> fantasai: We got some feedback, it was somewhat mixed.
- # [18:24] <TabAtkins_> fantasai: One of the things we noted was that the proposed syntax used the "to" keyword to distinguish the size from the position, but that seemed confusing/awkward to people.
- # [18:24] <TabAtkins_> fantasai: So we tweaked the proposed syntax a bit to remove that. The new version is up on the wiki.
- # [18:24] <TabAtkins_> fantasai: It's simpler than before.
- # [18:25] <TabAtkins_> fantasai: The only thing needed is to distinguish the size from the position, but only one of them needs a special marker to resolve the parsing/reading ambiguity.
- # [18:25] <TabAtkins_> fantasai: So the proposal is "radial-gradient( [<shape> || <size> ] [at <position>]?, <color-stops> )"
- # [18:26] <TabAtkins_> fantasai: In the old syntax, you couldn't specify *just* an explicit size, because of the parsing ambiguity. That's gone now. It's also clearer that the number after "at" are a position.
- # [18:26] <TabAtkins_> fantasai: An example would be "radial-gradient(5em circle at top left, ...)"
- # [18:27] <TabAtkins_> jdaggett: You just put this proposal on the wiki today?
- # [18:27] <TabAtkins_> fantasai: I put the latest version up yesterday, and rearranged the text today.
- # [18:28] <TabAtkins_> florianr: The polls were inconclusive. I support the readability initiative, but if it's not a big change, I'm not sure it's worthwhile, given the cost of syntax changing.
- # [18:29] <TabAtkins_> howcome: I have a comment in general on replacing commas with keywords, such as "as" in attr(). I don't think it's worthwhile if we already ahve something working. But I don't have a comment on gradients specifically.
- # [18:30] <TabAtkins_> kimberly: I think the old syntax is only really useful with generating tools; it's too hard to write by hand. The newer syntax can actually be remembered.
- # [18:30] <TabAtkins_> florianr: I agree that it's more readable, but I'm not convinced it's particular more rememberable to be more writeable.
- # [18:31] <TabAtkins_> sylvaing: Readability isn't just reading a stylesheet, it's also "does it make sense?". If you see the gradient and some possible forms for it, can you pick the right one?
- # [18:31] <dbaron> q+
- # [18:31] * Zakim sees dbaron on the speaker queue
- # [18:31] <TabAtkins_> glazou: We already have four syntaxes in the wild. This will be a fifth one. Will impls drop the old ones rapidly?
- # [18:32] <TabAtkins_> glazou: For editting tools, this will be hell.
- # [18:32] <TabAtkins_> smfr: Webkit won't change its prefixed syntax.
- # [18:32] <Bert> q+ to to ask [but feel free to ignore]: Would it help to pull the <shape> out of the parentheses and put it in the function name? radial-gradient(...) vs circle-gradient(...).
- # [18:32] * Zakim sees dbaron, to on the speaker queue
- # [18:33] <Bert> q- to
- # [18:33] * Zakim sees dbaron on the speaker queue
- # [18:33] <TabAtkins_> sylvaing: And MS might even keep its prefixed one around for a while, since it's compatible with existing content.
- # [18:33] <Bert> q+ to ask [but feel free to ignore]: Would it help to pull the <shape> out of the parentheses and put it in the function name? radial-gradient(...) vs circle-gradient(...).
- # [18:33] * Zakim sees dbaron, Bert on the speaker queue
- # [18:33] <TabAtkins_> divya: [didn't capture it well]
- # [18:33] <glazou> Zakim, ack dbaron
- # [18:33] <Zakim> I see Bert on the speaker queue
- # [18:33] <TabAtkins_> dbaron: I heard people comparing it to "the old syntax", but there's not one single old syntax.
- # [18:34] <TabAtkins_> dbaron: I think the stuff that led to this change was several feature additions, and if we keep the "old syntax", we should reverse those feature changes as well.
- # [18:34] <dbaron> Tab: that's the explicit sizing
- # [18:34] <fantasai> q+
- # [18:34] * Zakim sees Bert, fantasai on the speaker queue
- # [18:35] <Zakim> -tantek
- # [18:35] <florianr> q+
- # [18:35] * Zakim sees Bert, fantasai, florianr on the speaker queue
- # [18:36] <TabAtkins_> plinss: There's been discussion of prefixes around. The *entire reason* we have prefixes is so we don't have to worry about legacy content here. So I'm not going to accept any arguments about not changing something because there is prefixed content.
- # [18:36] <TabAtkins_> sylvaing: There is a *lot* of content out there already in a particular syntax.
- # [18:37] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [18:37] <Zakim> -danielweck
- # [18:37] * Joins: arno (arno@192.150.10.200)
- # [18:37] <Zakim> +??P12
- # [18:37] <danielweck> Zakim, P12 is me
- # [18:37] <Zakim> sorry, danielweck, I do not recognize a party named 'P12'
- # [18:37] <danielweck> Zakim, ??P12 is me
- # [18:37] <Zakim> +danielweck; got it
- # [18:37] <dbaron> dbaron: I don't think relevant topics should be ruled out-of-order.
- # [18:37] <glazou> SOUNDS LIKE A PLAN :-)
- # [18:38] <dbaron> ack Bert
- # [18:38] <Zakim> Bert, you wanted to ask [but feel free to ignore]: Would it help to pull the <shape> out of the parentheses and put it in the function name? radial-gradient(...) vs
- # [18:38] <Zakim> ... circle-gradient(...).
- # [18:38] * Zakim sees fantasai, florianr on the speaker queue
- # [18:38] * sylvaing editor killing himself is the new Last Call
- # [18:38] <plinss> q?
- # [18:38] * Zakim sees fantasai, florianr on the speaker queue
- # [18:38] <TabAtkins_> TabAtkins_: The shape is the *least* confusing part of the syntax. Pulling it out wouldn't actually help.
- # [18:39] <antonp> @sylaing: :-D
- # [18:39] <TabAtkins_> fantasai: This isn't just about radial gradients, or just about *today's* radial gradients. This "more readable" or "more CSS-y" syntax also lets us expand this more easily in the future, such as adding in the features present in the original webkit gradients.
- # [18:40] <TabAtkins_> fantasai: This also applies for more than radial gradients. The attr() function is an example. It originally took only one argument. Now it takes 3. Perhaps it will take 4 in future (a selector for which children to take the attr from?). As more args get added, it becomes more confusing.
- # [18:40] <glazou> q+
- # [18:40] * Zakim sees fantasai, florianr, glazou on the speaker queue
- # [18:40] <TabAtkins_> fantasai: What we're trying to do here is to take the CSS value syntax and the fundamental properties we use to develop that, and move that into functions as well, since we seem to have a good handle on extensibility in normal properties.
- # [18:40] <glazou> Zakim, ack fantasai
- # [18:40] <Zakim> I see florianr, glazou on the speaker queue
- # [18:41] <TabAtkins_> fantasai: If we stick with comma-separated, this limits our ability to extend not only radial gradients, but also other functions in the future.
- # [18:41] <TabAtkins_> howcome: The current syntax still uses commas, though, right?
- # [18:41] * sylvaing prefixed commas!
- # [18:42] <TabAtkins_> fantasai: Yes, but in the traditional CSS meaning, separating a list of similar values.
- # [18:42] * jdaggett sylvaing behave!
- # [18:42] <TabAtkins_> florianr: I'm receptive to fantasai's argument regarding extensibility. I have nothing against it.
- # [18:42] <TabAtkins_> florianr: So for the sake of extensibility, I'm rather in favor of this wiki proposal.
- # [18:42] <plinss> ack florianr
- # [18:42] * Zakim sees glazou on the speaker queue
- # [18:42] <TabAtkins_> florianr: For readability, I'm less convinced in this particular case.
- # [18:43] <TabAtkins_> florianr: Regarding prefixing, I agree we shouldn't consider it forbidden to change prefixed things. But we also shouldn't pretend the cost is zero.
- # [18:43] <jdaggett> ack glazou
- # [18:43] * Zakim sees no one on the speaker queue
- # [18:43] <plinss> ack glazou
- # [18:43] * Zakim sees no one on the speaker queue
- # [18:43] <TabAtkins_> glazou: Agree, and clarify what I said earlier. I said it's hell for editors, but [something I missed].
- # [18:44] <TabAtkins_> glazou: smfr said that webkit won't drop its prefix, so what will you do, use a second prefix?
- # [18:44] <Zakim> +[IPcaller]
- # [18:44] <TabAtkins_> glazou: Unfortunately, because this is so successful, it has left the field of "experimental feature".
- # [18:44] <tantek> Zakim, IPcaller is tantek
- # [18:44] <Zakim> +tantek; got it
- # [18:44] * stearns notices we have 20 minutes left on the call
- # [18:45] <TabAtkins_> fantasai: No, webkit is not going to use a second prefix. They'll switch to the new syntax when the drop prefixes.
- # [18:45] <sylvaing> if I'm hearing this right, it sounds like prefixes are meant to enable us to fix success
- # [18:45] * tantek thinks there will be an overlap time when both prefixed and unprefixed versions are implemented.
- # [18:45] <TabAtkins_> fantasai: So there will be no new prefixed versions. They'll just implement the new syntax, unprefixed.
- # [18:45] <TabAtkins_> glazou: Is that the case for everyone?
- # [18:45] <TabAtkins_> fantasai: For Moz, yes.
- # [18:45] <TabAtkins_> sylvaing: For MS, yes.
- # [18:46] <TabAtkins_> florianr: Opera hasn't made a decision, but will likely do the same.
- # [18:46] <TabAtkins_> plinss: Prefixes become more painful the longer we keep them around. So the best solution to the entire prefix mess is for us to do our job and move things quickly.
- # [18:46] * tantek agrees with Peter.
- # [18:47] <TabAtkins_> fantasai: So in that vein, Tab and I propose to resolve on this syntax and publish a WD.
- # [18:47] * oyvind remembers this being said before...
- # [18:48] <TabAtkins_> jdaggett: I want to reiterate that this syntax was just put up on the wiki yesterday?
- # [18:48] * Bert (If the # of commas is a problem: you can also extend by changing the name: old radial(a b c) and new radial4(a,b,c,d).)
- # [18:48] <TabAtkins_> TabAtkins_: Yes, but it's identical to the old syntax except for the removal of "to", because the blog post comments pretty consistently found it confusing.
- # [18:48] <divya> agreed with fantasai for new syntax
- # [18:48] <divya> agreed
- # [18:48] <TabAtkins_> plinss: There are some general objections, but nothing specific to this. I hear general consensus.
- # [18:48] <TabAtkins_> RESOLVED: Accept the new gradient syntax on the wiki.
- # [18:49] <TabAtkins_> RESOLVED: Publish a new WD of Image Values.
- # [18:49] * kimberly watching fantasai do a happy dance :)
- # [18:49] * sylvaing push, push, push...it's a....DRAFT!
- # [18:49] <fantasai> ScribeNick: fantasai
- # [18:49] <fantasai> TabAtkins: I've been resolving issues or logging them on CSS3 Lists
- # [18:50] <fantasai> TabAtkins_: If ppl who have issues want to bring them up, bring them up. I'll respond; not leading right now.
- # [18:50] <fantasai> howcome: I reviewed this over several months now, and I do think it has basically the toolkit it's offering authors is good.
- # [18:50] <fantasai> howcome: They can create their own counter styles, and use them as if they were native to CSS.
- # [18:50] <fantasai> howcome: I think Tab's done a great job of expressing commonly expressed list types
- # [18:51] <fantasai> howcome: The draft has 2 parts I don't think fit in there.
- # [18:51] <fantasai> howcome: First is pre-defined counter styles
- # [18:51] <fantasai> howcome: They may or may not be correct
- # [18:51] <fantasai> howcome: They may or not be used.
- # [18:51] <fantasai> howcome: I believe most will not be used
- # [18:51] <fantasai> howcome: And there may or may not be thousands of other list styles we should have in there.
- # [18:51] <fantasai> howcome: I propose for now that we don't do pre-defined counter styles
- # [18:51] <fantasai> howcome: So that's for Chapter 10
- # [18:52] <fantasai> howcome: We can keep it in an informative appendix, or have W3C host a stylesheet authors could @import
- # [18:52] <fantasai> jdaggett: I think that's a really good idea.
- # [18:52] <fantasai> jdaggett: I like that idea because it allows for shared usage, allows ... implementations
- # [18:52] <fantasai> jdaggett: Also makes it so the definitions are malleable
- # [18:52] <glazou> q+
- # [18:52] * Zakim sees glazou on the speaker queue
- # [18:52] <fantasai> jdaggett: There's a lot less burden to adding things.
- # [18:52] * fantasai can't hear
- # [18:53] <fantasai> jdaggett: ... haven't totally verified the correctness of
- # [18:53] <fantasai> florianr: I think there was a clear benefit to coming up with all these styles initially, to ensure the generic mechanism can represent them alll
- # [18:53] <fantasai> florianr: But I agree that it's overhead to verify that they're right, to implement, to test, etc.
- # [18:53] <fantasai> florianr: For not much benefit, since they can be written in a stylesheet
- # [18:53] <fantasai> florianr: I would keep them as an example of how to do it
- # [18:54] <fantasai> glazou: Hosting the stylesheet at W3C will generate a lot of traffic, and W3C pays for that.
- # [18:54] <fantasai> glazou: Validator for instance already generates a lot of traffic.
- # [18:54] <fantasai> glazou: it's very expensive
- # [18:54] <fantasai> howcome: We host the Core Stylesheets, and bandwidth was more expensive then.
- # [18:54] * fantasai notes that almost nobody uses the Core Stylesheets
- # [18:54] <fantasai> jdaggett: Requiring it means we have to verify that it's right.
- # [18:55] <glazou> let's move the whole WG under chapter 11 :-p
- # [18:55] <fantasai> TabAtkins_: Proposal: we take Chapter 10, maybe 11 etc, put them into a separate spec
- # [18:55] <Zakim> -tantek
- # [18:55] <fantasai> TabAtkins_: They could remain informative, or be normative. Either way the status of the predefined styles won't hinder or affect the status of the overall Lists spec
- # [18:55] <fantasai> jdaggett: I would be fine moving these out to a different spec
- # [18:56] <fantasai> jdaggett: I think the proposal we were talking about would be better here [...
- # [18:56] <fantasai> jdaggett: This is where we're defining the counter styles
- # [18:56] <Bert> q+ to suggest making the chapter 10 into a Note.
- # [18:56] * Zakim sees glazou, Bert on the speaker queue
- # [18:56] <fantasai> TabAtkins: The problem with keeping them here is that it's harder to rev the entire Lists spec than to rev a separate Lists document.
- # [18:56] <fantasai> glazou: I have compromise. There's a tool we never use: W3C Note
- # [18:56] <fantasai> glazou: They are much simpler than specs, almost informative.
- # [18:57] <fantasai> glazou: We could release somethng there, it's visible and usable
- # [18:57] <dbaron> Today that would be called a "Working Group Note", I think.
- # [18:57] <Zakim> +[IPcaller]
- # [18:57] <fantasai> glazou: Maybe not 100% correct, but if you find a mistake, please help us.
- # [18:57] <fantasai> q+
- # [18:57] * Zakim sees glazou, Bert, fantasai on the speaker queue
- # [18:57] <tantek> Zakim, IPcaller is tantek
- # [18:57] <Zakim> +tantek; got it
- # [18:57] <glazou> Zakim, ack glazou
- # [18:57] <Zakim> I see Bert, fantasai on the speaker queue
- # [18:57] <dbaron> Also, we should keep the CSS2 styles in the spec.
- # [18:57] <Bert> q-
- # [18:57] * Zakim sees fantasai on the speaker queue
- # [18:57] <fantasai> florianr: But it would be just informative for authors, not asking UA styles to implement them.
- # [18:58] <Zakim> -tantek
- # [18:58] <fantasai> howcome: I think we could make rapid progress on Lists if this issue goes away
- # [18:58] <fantasai> dbaron: Which parts of Chapter 11 are you removing?
- # [18:58] <tantek> CSS2.1
- # [18:58] <fantasai> TabAtkins_: Everything except the CSS2.1 styles
- # [18:58] <fantasai> TabAtkins_: But parts about the longhand chinese styles would go with Chapter 10, and Chapter 12 as well
- # [18:58] <fantasai> dbaron: 2.1 had one of the CJK styles, and I think we should keep the stuff that was in 2.1 in CSS3 Lists
- # [18:59] <fantasai> howcome: I agree, but Tab can express it up to 1000 with @counter-style
- # [18:59] <fantasai> florianr: I'm not convinced the predefined styles need to go with the new things.
- # [18:59] <fantasai> jdaggett: Why don't we resolve to take them out, and then figure out how to parcel them out at a later point
- # [18:59] * Quits: glazou (glazou@82.247.96.19) (Client exited)
- # [18:59] <fantasai> dbaron: I'd still like to know what we're taking out and what we're keeping
- # [19:00] <fantasai> TabAtkins_: I would keep the ones defined in 2.1, defining them in @counter-style is possible and easy
- # [19:00] * tantek is now getting "This passcode is not valid."
- # [19:00] * Joins: glazou (glazou@82.247.96.19)
- # [19:00] <fantasai> TabAtkins lists styles in 2.1
- # [19:00] <tantek> when trying to rejoin the call
- # [19:00] <fantasai> TabAtkins notes they're very badly specified in 2.1
- # [19:00] <jdaggett> we're talking about moving out section 10, 11, 12 but keeping things from 2.1
- # [19:00] <fantasai> TabAtkins: In 2.0 we had ideographic, not in 2.1
- # [19:00] <fantasai> dbaron: The stuff in 2.0 is widely implemented, we should keep it.
- # [19:01] <fantasai> fantasai: It's also required for EPUB
- # [19:01] <fantasai> q+
- # [19:01] * Zakim sees fantasai on the speaker queue
- # [19:01] <fantasai> howcome: I don't think we should do that, we took them out of 2.1
- # [19:01] <fantasai> howcome: We found a better way for ppl to create these types themselves.
- # [19:01] <fantasai> dbaron: *Can* they create them themselves?
- # [19:01] <Zakim> +[IPcaller]
- # [19:02] <tantek> hence keep stuff that was in 2.1 rather than 2.0
- # [19:02] <tantek> Zakim, IPcaller is tantek
- # [19:02] <Zakim> +tantek; got it
- # [19:02] <fantasai> TabAtkins: The chinese-informal styles can be expressed using hacks around fallback. I put an example of how to do it
- # [19:02] <fantasai> TabAtkins_: I can do it up to 999 by creating 11 counter styles
- # [19:02] <fantasai> TabAtkins_: Might be able to drop it to 3 styles
- # [19:02] <fantasai> TabAtkins_: I could copy-paste it, wouldn't expect an average author to do.
- # [19:03] <fantasai> florianr: Can we say we remove everything except what was in 2.1 and maybe in addition to that what was in 2.0 and is also interoperably implemented?
- # [19:03] * fantasai still hasn't gotten to speak :(
- # [19:03] <plinss> q?
- # [19:03] * Zakim sees fantasai on the speaker queue
- # [19:04] <fantasai> :( :( :(
- # [19:04] <glazou> howcome: http://weasyprint.org/
- # [19:05] <tantek> plinss, remaining agenda items getting pushed to next week presumably?
- # [19:05] * plinss yes, it's more of a backlog than a target for one call...
- # [19:05] <Zakim> -danielweck
- # [19:05] * Joins: danielweck_ (danielweck@86.155.167.189)
- # [19:05] * Quits: danielweck (danielweck@81.157.14.54) (Ping timeout)
- # [19:05] * danielweck_ is now known as danielweck
- # [19:05] <Zakim> -stearns
- # [19:06] <tantek> millions of authors? are there that many that want/need the extra features?
- # [19:06] <fantasai> fantasai say something and nobody minutes it
- # [19:06] <fantasai> other people say stuff and fantasai didn't minute it either
- # [19:07] * tantek agrees with HÃ¥kon, fancy list-styles are similar to fancy fonts.
- # [19:07] <divya> :)
- # [19:07] <divya> sorry fantasai
- # [19:07] <smfr> gtg
- # [19:07] <jdaggett> the problem with predefined lists is that
- # [19:07] * Quits: smfr (smfr@173.228.90.57) (Quit: smfr)
- # [19:07] <glazou> tantek: I disagree, numbering is part of culture, it should just work
- # [19:07] <Zakim> -smfr
- # [19:07] <fantasai> howcome: The problem we'll have is we're surely going to find errors in that list, and if we hard-code it into the UA we're going to be stuck with those errors.
- # [19:07] <jdaggett> 1) we have to assure the list is correct
- # [19:07] * Quits: ericm (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:07] <tantek> glazou - that's a reasonable distinction.
- # [19:07] <jdaggett> 2) we need to decide the priority
- # [19:07] <Zakim> - +1.510.364.aaaa
- # [19:08] <fantasai> florianr: People will rely on it being wrong
- # [19:08] <jdaggett> and that's hard because stylistic variations occur
- # [19:08] <fantasai> fantasai: Won't rely on it being wrong, will rely on it being correct and occasionally be disappointed
- # [19:08] <jdaggett> which is more important?
- # [19:08] <fantasai> TabAtkins: I can take either way.
- # [19:08] <fantasai> FWIW, I have no objection to pulling them into a separate spec
- # [19:08] <dbaron> I thought this was the main thing in the lists spec.
- # [19:08] <fantasai> just to foisting the entire responsibility onto the authors
- # [19:09] <fantasai> howcome: If we put it in a new spec, it shouldn't be necessarily predefined
- # [19:09] <vhardy> sorry, need to drop off.
- # [19:09] <Zakim> -Oliver_Goldman
- # [19:09] <tantek> I'm in favor of whatever helps the editor move more quickly.
- # [19:09] <dbaron> I tend towards agreeing with fantasai; I also need to leave.
- # [19:09] * fantasai would like to hear dbaron's opinion on this
- # [19:10] <fantasai> plinss: I'm hearing no objection to splitting out the predefined counter styles into a separate spec
- # [19:10] <fantasai> howcome: this resolves a bunch of my objections
- # [19:10] <Zakim> -dbaron
- # [19:10] * fantasai can we just publish a WD and split it later?
- # [19:11] * Quits: JohnJan (johnjan@131.107.0.81) (Quit: JohnJan)
- # [19:11] <Zakim> -glazou
- # [19:11] <Zakim> -kimberly
- # [19:11] <fantasai> RESOLVED: split predefined counter styles into a separate spec
- # [19:11] <Zakim> -howcome
- # [19:11] <Zakim> -jdaggett
- # [19:11] <Zakim> -antonp
- # [19:11] <Zakim> -divya
- # [19:11] <Zakim> -[Microsoft]
- # [19:11] <Zakim> -SteveZ
- # [19:11] * Quits: antonp (50a94e63@64.62.228.82) (Quit: http://www.mibbit.com ajax IRC Client)
- # [19:11] <Zakim> -[Microsoft.a]
- # [19:11] <Zakim> -florianr
- # [19:11] <Zakim> -kojiishi
- # [19:11] <Zakim> -Bert
- # [19:11] <Zakim> -plinss
- # [19:11] <Zakim> -tabatkins_
- # [19:11] <Zakim> -tantek
- # [19:11] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:11] <Zakim> Attendees were glazou, jdaggett, plinss, florianr, divya, sylvaing, antonp, stearns, [Microsoft], +1.510.364.aaaa, johnjan, fantasai, tabatkins_, Bert, dbaron, smfr, danielweck,
- # [19:11] <Zakim> ... howcome, Oliver_Goldman, kojiishi, tantek, SteveZ
- # [19:11] * Quits: danielweck (danielweck@86.155.167.189) (Quit: danielweck)
- # [19:11] * Quits: kimberly (Kimberly@69.241.19.12) (Quit: ChatZilla 0.9.87 [Firefox 9.0/20111122192043])
- # [19:11] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
- # [19:11] * Quits: dstorey (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:12] * Quits: kojiishi (kojiishi@222.158.227.129) (Quit: Leaving...)
- # [19:12] <fantasai> Meeting closed.
- # [19:13] * Quits: divya (qw3birc@128.30.52.28) (Ping timeout)
- # [19:19] * Parts: oyvind (oyvinds@213.236.208.22)
- # [19:24] * Quits: florianr (florianr@213.236.208.22) (Quit: Leaving.)
- # [19:26] * Quits: SteveZ (chatzilla@24.6.120.172) (Connection reset by peer)
- # [19:26] * Joins: SteveZ_ (chatzilla@24.6.120.172)
- # [19:26] * SteveZ_ is now known as SteveZ
- # [19:26] * Quits: dbaron (dbaron@173.228.28.129) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [19:27] * Quits: TabAtkins_ (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:33] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [19:53] * Quits: stearns (anonymous@50.132.63.33) (Quit: stearns)
- # [20:03] * Quits: brianman (brianman@131.107.0.126) (Ping timeout)
- # [20:04] * Joins: brianman (brianman@131.107.0.81)
- # [20:06] * Quits: vhardy (vhardy@192.150.10.201) (Quit: vhardy)
- # [20:07] * Quits: drublic (drublic@77.2.144.198) (Client exited)
- # [20:18] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:18] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:20] * Joins: arno (arno@192.150.10.200)
- # [20:21] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:22] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:26] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:26] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:28] * Quits: sylvaing (sylvaing@131.107.0.82) (Client exited)
- # [20:29] * Joins: sylvaing (sylvaing@131.107.0.82)
- # [20:29] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:29] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:32] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:33] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:33] * Quits: sylvaing (sylvaing@131.107.0.82) (Ping timeout)
- # [20:35] * Joins: stearns (anonymous@192.150.22.5)
- # [20:36] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:36] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:39] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:40] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [20:51] * Joins: drublic (drublic@77.2.156.89)
- # [20:55] * Joins: sylvaing (sylvaing@131.107.0.70)
- # [20:59] * Joins: danielfilho_ (danielfilh@187.31.77.7)
- # [20:59] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [20:59] * danielfilho_ is now known as danielfilho
- # [21:09] * Quits: tantek (tantek@98.119.126.225) (Quit: tantek)
- # [21:15] * Quits: drublic (drublic@77.2.156.89) (Client exited)
- # [21:18] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [21:19] * Joins: arno (arno@192.150.10.200)
- # [21:38] * Zakim excuses himself; his presence no longer seems to be needed
- # [21:38] * Parts: Zakim (rrs-bridgg@128.30.52.169)
- # [22:44] * Joins: dbaron (dbaron@63.245.220.240)
- # [22:51] * Joins: TabAtkins (tabatkins@216.239.45.4)
- # [23:06] * Quits: miketaylr (miketaylr@206.217.92.186) (Quit: miketaylr)
- # [23:08] * Quits: sylvaing (sylvaing@131.107.0.70) (Ping timeout)
- # [23:09] * Joins: sylvaing (sylvaing@131.107.0.70)
- # [23:18] <TabAtkins> fantasai: Just hit an interesting use-case where using :matches() and the subject indicator is much more difficult than using :has().
- # [23:18] <TabAtkins> You want to select the preceding tr to the scope, even if it's in a preceding tbody.
- # [23:18] <TabAtkins> With has, this is:
- # [23:19] <TabAtkins> :matches(tr:has(+tr:scope), tbody:has(+tbody>tr:first-child:scope) > tr:last-child)
- # [23:19] <TabAtkins> With matches+subject indicator, this is:
- # [23:20] <TabAtkins> :matches( tr! + tr:scope, :matches(tbody! + tbody > tr:first-child:scope) > tr:last-child )
- # [23:20] <TabAtkins> I think the use of :matches() solely to scope the subject indicator is confusing there.
- # [23:20] <TabAtkins> It took me a little bit of thinking to come up with it, at least.
- # [23:26] * Joins: drublic (drublic@77.2.156.89)
- # Session Close: Thu Dec 01 00:00:00 2011
The end :)