/irc-logs / w3c / #css / 2010-06-02 / end

Options:

  1. # Session Start: Wed Jun 02 00:00:00 2010
  2. # Session Ident: #css
  3. # [00:04] * Quits: miketaylr (miketaylr@38.117.156.163) (Client exited)
  4. # [00:08] * Quits: myakura (myakura@220.104.128.62) (Quit: Leaving...)
  5. # [00:31] * Joins: Lachy (Lachlan@84.215.59.50)
  6. # [02:21] * jdaggett_afk is now known as jdaggett
  7. # [02:23] * Quits: TabAtkins (tabatkins@216.239.45.4) (Quit: Lost terminal)
  8. # [02:28] * Joins: tabatkins (tabatkins@216.239.45.4)
  9. # [02:31] * tabatkins is now known as TabAtkins
  10. # [03:36] * Quits: Curt`` (DorkeyDear@76.241.76.245) (Ping timeout)
  11. # [03:51] <fantasai> dbaron, TabAtkins: Will you be on the call tomorrow?
  12. # [04:18] * Quits: karl (karlcow@128.30.54.58) (Quit: This computer has gone to sleep)
  13. # [04:22] * Quits: dbaron (dbaron@63.245.220.240) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  14. # [04:34] * Joins: miketaylr (miketaylr@24.42.95.108)
  15. # [05:13] * Quits: miketaylr (miketaylr@24.42.95.108) (Connection reset by peer)
  16. # [05:27] * Joins: Curt` (DorkeyDear@76.241.76.245)
  17. # [05:48] * Joins: karl (karlcow@128.30.54.58)
  18. # [06:46] * Quits: Curt` (DorkeyDear@76.241.76.245) (Quit: Leaving)
  19. # [08:19] * Quits: shepazu (schepers@128.30.52.169) (Quit: shepazu)
  20. # [11:21] * jdaggett is now known as jdaggett_afk
  21. # [11:28] * Quits: Lachy (Lachlan@84.215.59.50) (Quit: This computer has gone to sleep)
  22. # [11:45] * Joins: Lachy (Lachlan@213.236.208.22)
  23. # [11:45] * Parts: Lachy (Lachlan@213.236.208.22) (Leaving)
  24. # [11:54] * Joins: CesarAcebal (acebal@193.51.208.72)
  25. # [15:48] * Joins: miketaylr (miketaylr@38.117.156.163)
  26. # [15:49] * Joins: jdaggett (jdaggett@118.243.224.63)
  27. # [15:55] * Joins: ChrisL (ChrisL@128.30.52.169)
  28. # [16:02] * Joins: TabAtkins_ (chatzilla@76.253.3.102)
  29. # [17:00] * Quits: TabAtkins_ (chatzilla@76.253.3.102) (Ping timeout)
  30. # [17:17] * Joins: Curt` (DorkeyDear@76.241.76.245)
  31. # [17:33] * Joins: Zakim (rrs-bridgg@128.30.52.169)
  32. # [17:34] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
  33. # [17:34] <RRSAgent> logging to http://www.w3.org/2010/06/02-CSS-irc
  34. # [17:34] <plinss> zakim, this will be style
  35. # [17:34] <Zakim> ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 29 minutes
  36. # [17:34] <plinss> rrsagent, make logs public
  37. # [17:34] <RRSAgent> I have made the request, plinss
  38. # [17:50] * Joins: oyvind (oyvinds@213.236.208.22)
  39. # [17:58] <TabAtkins> fantasai: Yeah, I'll be on in a few. ^_^
  40. # [17:59] <Zakim> Style_CSS FP()12:00PM has now started
  41. # [18:00] <Zakim> + +1.858.655.aaaa
  42. # [18:00] <plinss> zakim, aaaa is me
  43. # [18:00] <Zakim> +plinss; got it
  44. # [18:00] <Zakim> + +1.650.253.aabb
  45. # [18:00] <TabAtkins> Zakim, aabb is me
  46. # [18:00] <Zakim> +TabAtkins; got it
  47. # [18:02] * Joins: bradk (bradk@67.188.133.45)
  48. # [18:02] <Zakim> +ChrisL
  49. # [18:02] <Zakim> +fantasai
  50. # [18:02] * fantasai changed her flight
  51. # [18:03] <Zakim> + +1.650.275.aacc
  52. # [18:03] <Zakim> +Bert
  53. # [18:03] <bradk> Zakim, aacc is me
  54. # [18:03] <Zakim> +bradk; got it
  55. # [18:04] <Zakim> + +49.238.aadd
  56. # [18:04] <plinss> zakim, aadd is CesarAcebal
  57. # [18:04] <Zakim> +CesarAcebal; got it
  58. # [18:04] <ChrisL> zakim, who is breathing?
  59. # [18:04] <Zakim> I don't understand your question, ChrisL.
  60. # [18:04] * Joins: smfr (smfr@72.25.91.23)
  61. # [18:04] <bradk> I think I am going to hang up and try again to see if I can get a better connection...
  62. # [18:05] <Zakim> +[Microsoft]
  63. # [18:05] <arronei> zakim, microsoft is me
  64. # [18:05] <Zakim> -bradk
  65. # [18:05] <Zakim> +arronei; got it
  66. # [18:05] <Zakim> + +1.408.636.aaee
  67. # [18:05] <smfr> Zakim, aaee is me
  68. # [18:05] <Zakim> +smfr; got it
  69. # [18:05] * ChrisL drops off for a moment to deal with family
  70. # [18:06] <Zakim> -ChrisL
  71. # [18:06] <Zakim> +bradk
  72. # [18:07] * Joins: dbaron (dbaron@98.234.51.190)
  73. # [18:08] <Zakim> +[IPcaller]
  74. # [18:08] <Zakim> +David_Baron
  75. # [18:08] <TabAtkins> ScribeNick: fantasai
  76. # [18:08] <Zakim> +SteveZ
  77. # [18:08] <TabAtkins> Shit.
  78. # [18:08] <TabAtkins> ScribeNick: TabAtkins
  79. # [18:09] <TabAtkins> plinss: Anything to add to the agenda?
  80. # [18:09] <TabAtkins> plinss: Request from Hakon to publish GCPM.
  81. # [18:09] <Zakim> -[IPcaller]
  82. # [18:09] * Joins: howcome (howcome@93.179.13.124)
  83. # [18:09] <TabAtkins> TabAtkins: I have no objection to publishing.
  84. # [18:10] * Joins: szilles (chatzilla@67.180.186.242)
  85. # [18:10] <TabAtkins> plinss: I think we all agreed to publish once he fixed one issue, which I believe he did his best to address.
  86. # [18:10] <TabAtkins> RESOLVED: Publish new GCPM working draft.
  87. # [18:10] <howcome> Correct
  88. # [18:10] <Zakim> +ChrisL
  89. # [18:10] <TabAtkins> plinss: Css 2.1 issues. Anything interesting in the test suite?
  90. # [18:11] <ChrisL> howcome, thanks for clarifying that cmyk is device cmyk. I still think its underspecified but at least it is a little clearer now
  91. # [18:11] <TabAtkins> fantasai: i18n submitted their tests and I've added them. Not sure if I got all the encodings right, so I'll need Richard to check them.
  92. # [18:11] <TabAtkins> fantasai: Taking a while to convert Hixie's tests right now.
  93. # [18:11] * TabAtkins missed something about reftests
  94. # [18:11] <fantasai> I'm about halfway through, but it takes awhile since they often need manual tweaking
  95. # [18:12] <fantasai> Reftests are buildable. I've added bzbarsky's, not yet Mozilla's
  96. # [18:12] <TabAtkins> arronei: There'll be substantial updates from me from feedback on test cases.
  97. # [18:12] <TabAtkins> arronei: No more issues from the repo.
  98. # [18:12] <TabAtkins> plinss: David, any updates?
  99. # [18:12] <TabAtkins> dbaron: Wrote proposal for 66 last night, haven't yet resolved 101 - it's somewhat more involved.
  100. # [18:13] <dbaron> http://lists.w3.org/Archives/Public/www-style/2010Jun/0048.html
  101. # [18:13] <dbaron> http://lists.w3.org/Archives/Public/www-style/2010Jun/0049.html
  102. # [18:13] <Zakim> +??P29
  103. # [18:13] <TabAtkins> dbaron: There was one response on www-style about issue 66.
  104. # [18:13] <dbaron> s/issue 66/issue 26/
  105. # [18:13] <Zakim> -??P29
  106. # [18:13] <TabAtkins> dbaron: I think Peter's first 2 proposed changes we should just take, and the remaining ones should maybe be a separate issue.
  107. # [18:14] <dbaron> the first 2 are the (see above) and the s/specified/computed/
  108. # [18:16] <TabAtkins> plinss: Are we okay with accepting the proposal?
  109. # [18:17] <TabAtkins> arronei: I agree with putting the later points into a separate issue.
  110. # [18:18] <Zakim> +[IPcaller]
  111. # [18:18] <szilles> +1 for the proposal
  112. # [18:18] <TabAtkins> RESOLVED: Accept dbaron's proposal for issue 26, open a new issue for the remaining points from Peter Moulder
  113. # [18:19] * Quits: howcome (howcome@93.179.13.124) (Ping timeout)
  114. # [18:20] <TabAtkins> Bert: For my issues, I'm working on 120. It's difficult. I'm checking if it's possible to resolve.
  115. # [18:20] <TabAtkins> Bert: I've put text for 117 on the list.
  116. # [18:20] <TabAtkins> Bert: I think everything else is just editorial and I'll slowly work through them.
  117. # [18:20] <TabAtkins> plinss: arron?
  118. # [18:21] <TabAtkins> arronei: I finished 134. 107 I'm working on, but the test case is wrong. 154, I have the diagram drawn up, I'm having one of our guys look at it first. It should be pretty close. 165 I haven't gotten to yet.
  119. # [18:21] <TabAtkins> arronei: But I think 165 is actually a css3 issue.
  120. # [18:21] <TabAtkins> arronei: Because it talks about "start" and "end" the entire email.
  121. # [18:22] <dbaron> I think 165 is a CSS 2.1 issue.
  122. # [18:22] <TabAtkins> plinss: Tab?
  123. # [18:22] <dbaron> It's the question of whether the way float placement rules respond to 'direction' is correct.
  124. # [18:22] <dbaron> But it might be pointing to the wrong emails.
  125. # [18:22] <TabAtkins> TabAtkins: Issue 161 is Bert's now to make the edit, the rest I've worked on, but havent' brought anything to the list yet.
  126. # [18:23] <TabAtkins> plinss: 129 is for all of us to discuss and bring to a close.
  127. # [18:23] <plinss> http://lists.w3.org/Archives/Public/www-style/2009Jun/0164.html
  128. # [18:24] <TabAtkins> plinss: What to do about brace matching inside an invalid url.
  129. # [18:24] <TabAtkins> Bert: The question is if you find parens or brackets, is it invalid or something other than a url - something we haven't defined yet.
  130. # [18:24] <TabAtkins> Bert: Currently it's the latter.
  131. # [18:25] <fantasai> http://wiki.csswg.org/spec/css2.1#issue-140 http://wiki.csswg.org/spec/css2.1#issue-129
  132. # [18:25] * fantasai notes we have two issues that seem somewhat related here
  133. # [18:25] <TabAtkins> plinss: Problem with urls is that characters like brackets are valid within urls, but if something happens later that makes it invalid do we have to back up to handle it properly or not.
  134. # [18:25] * fantasai doesn't claim to know much about the grammar, though
  135. # [18:26] <TabAtkins> plinss: fantasai, you're mentioning that issue 140 seems to be related.
  136. # [18:27] <TabAtkins> plinss: It's similar, but it might even be putting us in an opposite direction from the issue 129.
  137. # [18:29] * TabAtkins got too lost to minute that last exchange. ;_;
  138. # [18:29] <TabAtkins> plinss: We seem to be stalled on this. Does anyone have any ideas?
  139. # [18:29] <TabAtkins> Bert: I think it's possible to expand the definition of any* like dbaron says.
  140. # [18:30] <TabAtkins> Bert: Nothing uses that, it's just making something more defined where it is undefined.
  141. # [18:30] <TabAtkins> Bert: I think it's ugly to define a grammar and then say we won't use it, but oh well.
  142. # [18:30] <TabAtkins> Bert: But are braces all that needs to be added, or other tokens as well?
  143. # [18:30] <TabAtkins> dbaron: Possible semicolons.
  144. # [18:31] <TabAtkins> Bert: What about @?
  145. # [18:31] <TabAtkins> dbaron: Isn't a lone @ DELIM?
  146. # [18:31] <TabAtkins> Bert: yes, sorry, I meant @keyword.
  147. # [18:32] <TabAtkins> dbaron: Putting braces in any* is a little problematic for the selector rule, though?
  148. # [18:32] <TabAtkins> Bert: Yes.
  149. # [18:32] <dbaron> and ; is a little problematic for the at-rule part
  150. # [18:32] <smfr> sorry, i have to drop off the call
  151. # [18:32] <TabAtkins> Bert: But if it's only braces it only needs to be changed in 3 places.
  152. # [18:32] <Zakim> -smfr
  153. # [18:33] <TabAtkins> plinss: We seem to have consensus on issue 140 and nothing but silence on issue 129.
  154. # [18:33] <TabAtkins> plinss: Can we even get agreement on what we want the behavior to *be* on 129?
  155. # [18:33] <TabAtkins> Bert: I remain reluctant to change that.
  156. # [18:33] <TabAtkins> Bert: I'm not planning to use parens in urls, but I don't know if someone else does.
  157. # [18:34] <TabAtkins> Bert: The issue with invalid comments is less serious. Afaik there is no way to use the current definition for anything.
  158. # [18:34] <TabAtkins> Bert: It doesn't make sense to only change comments, though, since the goal is to remove all backup.
  159. # [18:35] <Bert> url((http://foo/), (12))
  160. # [18:35] <TabAtkins> TabAtkins: Do we actually think that anyone has invented a new url syntax that uses parens.
  161. # [18:35] <TabAtkins> fantasai: I'm pretty sure there's random urls with parens stuck in them.
  162. # [18:35] <TabAtkins> Bert: As far as I know, though, current impls reject that as they should.
  163. # [18:36] * Joins: howcome (howcome@77.19.160.127)
  164. # [18:36] <TabAtkins> fantasai: If parens are mismatched, then how we resolve this issue will change how the stylesheet is handled.
  165. # [18:36] * Parts: smfr (smfr@72.25.91.23)
  166. # [18:36] <TabAtkins> fantasai: Under the current urls you have to go back and match the parens.
  167. # [18:36] <TabAtkins> ChrisL: There's no requirement in the uri spec to match the parens, though, right?
  168. # [18:36] <TabAtkins> ChrisL: It's a valid url to have mismatched parens.
  169. # [18:37] <TabAtkins> plinss: Our definition of url token doesn't even allow parens in the url.
  170. # [18:37] <TabAtkins> Bert: Right, that's what allows the extension I put into irc.
  171. # [18:37] <fantasai> url([)
  172. # [18:37] <TabAtkins> fantasai: Also brackets cause the issue.
  173. # [18:38] <TabAtkins> plinss: brackets and braces are allowed in our definition of a url token, parens are not.
  174. # [18:38] <fantasai> background: url([) purple;
  175. # [18:38] <fantasai> is it purple?
  176. # [18:38] <TabAtkins> I say: yes.
  177. # [18:38] <TabAtkins> plinss: that is a perfectly valid url.
  178. # [18:39] <TabAtkins> plinss: Now what happens if you put something after that bracket and it's no longer a valid url?
  179. # [18:39] <fantasai> background: url([()) purple;
  180. # [18:39] <dbaron> The current spec says that:
  181. # [18:39] <dbaron> background: url([) purple;
  182. # [18:39] <dbaron> is purple
  183. # [18:39] <dbaron> but
  184. # [18:39] <dbaron> background: url([() purple;
  185. # [18:39] <dbaron> is not
  186. # [18:39] <fantasai> what about url([()) purple?
  187. # [18:39] <dbaron> fantasai, not purple
  188. # [18:39] <TabAtkins> plinss: Correct. Now is that our desired behavior or not?
  189. # [18:40] <fantasai> background: url([()); color: purple;
  190. # [18:40] <dbaron> fantasai, still not purple
  191. # [18:40] <TabAtkins> Bert: We know whether it's purple or not, the question is we want to allow that grammar for other people, even if we didn't use it.
  192. # [18:40] <TabAtkins> fantasai: That's not the issue. The issue is that the parser has to go back and reparse everything in the url token.
  193. # [18:41] <TabAtkins> fantasai: Where it then treats things as random garbage, with matched quotes and brackets and such.
  194. # [18:41] <TabAtkins> fantasai: So we know how to deal with invalid stuff. But an impl said they don't want to have to back up like that.
  195. # [18:42] <TabAtkins> fantasai: So what we want is something that can read until we know it fails, and then just get thrown out without reinterpreting.
  196. # [18:42] <fantasai> backing up anarbitrary amount is the problem
  197. # [18:42] <TabAtkins> szilles: So another way of saying this is, as long as it's a legal uri we'll put it into the token and not reparse it?
  198. # [18:42] <TabAtkins> fantasai: Right.
  199. # [18:42] <TabAtkins> szilles: And this is an error recovery mechanism.
  200. # [18:42] <TabAtkins> plinss: Bert is resistant to change the core grammar.
  201. # [18:43] <TabAtkins> Bert: As far as I can see it's not an error recovery mechanism, it's just one token or another?
  202. # [18:43] <TabAtkins> plinss: But the issue is that you can't tell which token you have until it's either done or you reparse.
  203. # [18:44] <TabAtkins> Bert: You have the same problem with other tokens, such as numbers and dimensions.
  204. # [18:44] <TabAtkins> ChrisL: urls can be bigger, though.
  205. # [18:44] <TabAtkins> Bert: I measured, and couldn't measure the difference until the url hits megabyte lengths.
  206. # [18:44] <TabAtkins> ChrisL: Bert, so you're suggesting close the issue with no change?
  207. # [18:44] <TabAtkins> Bert: Yes.
  208. # [18:45] <TabAtkins> Bert: It's a pity no one noticed this 10 years ago, but I don't like changing things at this late stage.
  209. # [18:45] <TabAtkins> plinss: There is the other proposal, to change the grammar.
  210. # [18:46] <TabAtkins> plinss: There's impls that don't want to backup. I understand Bert's point, but another point is that there's a difference in error recovery, such as what Elika put in IRC. I don't think that our existing specified behavior really makes sense, and is something we want.
  211. # [18:47] <TabAtkins> szilles: I lead toward changing the grammar because it seems to let urls accept anything except that, because we use parens, in a url you have to escape the parens.
  212. # [18:47] <TabAtkins> szilles: And then if it happens to be invalid for some other reasons, that doesn't seem that it should affect the tokenizer.
  213. # [18:47] <TabAtkins> Bert: That case that elika typed into IRC would change.
  214. # [18:47] * fantasai likes szilles term "sufficiently obscure"
  215. # [18:47] <fantasai> :P
  216. # [18:48] <TabAtkins> Bert: So it's clearly a change.
  217. # [18:48] <TabAtkins> szilles: But it's also clearly a legal url.
  218. # [18:48] <fantasai> szilles: I don't see that in a sufficiently obscure case we can't make a change
  219. # [18:48] <TabAtkins> plinss: but it's not legal CSS, becasue you have to escape the parens.
  220. # [18:48] <TabAtkins> fantasai: I typed several things into IRC, and only one of them would change.
  221. # [18:49] <TabAtkins> fantasai: As long as it's a valid url token, there's no change in behavior.
  222. # [18:49] <TabAtkins> szilles: That's what I tried to argue. For simplicity of use, putting any valid uri in there with a simple rule saying that parens need to be escaped is what I would hope for.
  223. # [18:49] <TabAtkins> plinss: That seems to already be in place. The only thing we're changing is the error recovery behavior.
  224. # [18:50] <TabAtkins> szilles: I say consume as much as fits the uri syntax and not go back.
  225. # [18:50] <TabAtkins> TabAtkins: Which of the cases that elika posted would change under the proposal? The url([(), or the url([())?
  226. # [18:51] <TabAtkins> TabAtkins: Right now both kill the entire declaration. Would either of those change?
  227. # [18:51] <TabAtkins> fantasai: It would still kill the declaration, but it wouldn't eat more trying to close the bracket.
  228. # [18:52] <TabAtkins> szilles: Gut feeling, it seems people are more likely to forget to escape a paren, then they're looking to match a bracket or a brace.
  229. # [18:52] <TabAtkins> fantasai: In either case it's invalid, the question is just if we lose the entire rest of the stylesheet or just the declaration.
  230. # [18:52] <TabAtkins> szilles: I'd prefer just lose the declaration.
  231. # [18:52] <TabAtkins> fantasai: Can we take a straw poll on this?
  232. # [18:52] <plinss> zakim, who is on the phone?
  233. # [18:52] <Zakim> On the phone I see plinss, TabAtkins, fantasai, Bert, CesarAcebal, arronei, bradk, David_Baron, SteveZ, ChrisL, [IPcaller]
  234. # [18:53] <TabAtkins> plinss: IN favor of only losing declaration (change grammar).
  235. # [18:53] <TabAtkins> TabAtkins: I prefer to change the grammar.
  236. # [18:53] <TabAtkins> fantasai: Change the grammar.
  237. # [18:53] <TabAtkins> Bert: Keep the grammar.
  238. # [18:53] <TabAtkins> CesarAcebal: Keep the grammar.
  239. # [18:54] <TabAtkins> arronei: Prefer to keep, but I think we have to change. So my vote is to change.
  240. # [18:54] <TabAtkins> bradk: Change, but I don't feel strongly.
  241. # [18:54] <TabAtkins> dbaron: Change the grammar.
  242. # [18:54] <TabAtkins> szilles: Change the grammar.
  243. # [18:54] <TabAtkins> ChrisL: Change the grammar.
  244. # [18:54] * dbaron Zakim, [IPcaller] is howcome
  245. # [18:54] * Zakim +howcome; got it
  246. # [18:54] <TabAtkins> howcome: Keep the grammar, but I don't feel strongly.
  247. # [18:55] <TabAtkins> 8 for change (1 not strong), 3 to keep (1 not strong).
  248. # [18:55] <TabAtkins> plinss: I wonder if we could get the same effect by changing the prose rather than the grammar.
  249. # [18:55] <TabAtkins> ChrisL: You could, but that would just mean you don't implement the grammar anyway, you do something else.
  250. # [18:56] <TabAtkins> fantasai: I think most of our error handling is in the prose anyway, not the grammar.
  251. # [18:57] <TabAtkins> plinss: We have a few existing INVALID tokens, so adding another one or two would be good for clarity.
  252. # [18:57] <TabAtkins> RESOLVED: Change the grammar to avoid backup.
  253. # [18:58] <ChrisL> I offer to take Issue 145 which has no owner. I think the commentor is correct, will discuss with I18n folks
  254. # [18:58] <Zakim> -bradk
  255. # [18:58] <TabAtkins> ChrisL: On issue 114, SVG liked option 1, which is that font names are idents or quoted strings.
  256. # [18:59] <fantasai> i18n has gone back and forth on 145, I don't expect us to get an answer until next week's bidi f2f is over
  257. # [18:59] <TabAtkins> Bert: There's a mistake in the message you sent. It says proposal 2 requires a change in the grammar, but that's not the case.
  258. # [18:59] <TabAtkins> ChrisL: We understood that it did, and because of your reluctance to change the grammar we didn't think it would fly.
  259. # [19:00] <TabAtkins> ChrisL: We thought it was slightly irritating to have to quote fonts starting with a number, but it was ok.
  260. # [19:00] <TabAtkins> ChrisL: What was the accepted proposal for csswg?
  261. # [19:00] <Zakim> +bradk
  262. # [19:00] <Zakim> -bradk
  263. # [19:01] <TabAtkins> fantasai: IDENTs.
  264. # [19:01] * bradk is having phone problems
  265. # [19:01] <fantasai> http://lists.w3.org/Archives/Public/www-style/2010Apr/0275.html look for CSS2.1 Issues
  266. # [19:01] * dbaron wonders what the issue number for the URL issue that we finally resolved was
  267. # [19:01] <TabAtkins> Bert: I have a different memory of the straw poll.
  268. # [19:01] <fantasai> glazou: 7 for 1, 4 for 2, 3 for 3, and almost everyone can live with
  269. # [19:01] <fantasai> everything
  270. # [19:02] <TabAtkins> ChrisL: Since 1 was most popular for CSS and SVG, we can just pick that, close it, and move on?
  271. # [19:02] <TabAtkins> fantasai: Yup.
  272. # [19:02] * oyvind dbaron, 129 I think?
  273. # [19:02] <TabAtkins> arronei: I'll have to change the test cases, right?
  274. # [19:03] <TabAtkins> plinss: I think you may have gotten 1 and 2 mixed up.
  275. # [19:03] <TabAtkins> [discussion]
  276. # [19:03] <TabAtkins> plinss: Okay, so we're going with 1.
  277. # [19:03] <TabAtkins> Bert: A pity.
  278. # [19:04] <ChrisL> resolution: go with option 1 on issue 114
  279. # [19:04] <TabAtkins> fantasai: This is probably better for authors anyway, since current impls are ident+.
  280. # [19:04] <Zakim> -howcome
  281. # [19:04] <TabAtkins> szilles: I believe the goal was to give authors something easy to understand, rather than to omit quotes.
  282. # [19:05] <fantasai> RESOLVED: font-family names are ident+
  283. # [19:05] <TabAtkins> RESOLVED: Accept option 1 (font names are IDENTs or quoted strings) for issue 114.
  284. # [19:05] <TabAtkins> plinss: Did we come to a resolution for issue 129 or 140?
  285. # [19:05] <dbaron> I think plinss just asked about 140.
  286. # [19:05] <dbaron> We did resolve 129.
  287. # [19:05] <TabAtkins> fantasai: Seems that bert and dbaron agreed to change the grammar to handle 129 per dbaron's proposal.
  288. # [19:06] <fantasai> s/129/140/
  289. # [19:06] * TabAtkins has confused himself.
  290. # [19:06] <fantasai> plinss: I suggest whoever does one does both
  291. # [19:06] * TabAtkins splits the difference - we've resolved 149.
  292. # [19:07] * Quits: howcome (howcome@77.19.160.127) (Ping timeout)
  293. # [19:07] <TabAtkins> plinss: Accept in principle to change the grammar for 140 and note that we wont' use the additional capabilities (exact wording tbd).
  294. # [19:07] <fantasai> s/plinss/RESOLVED/
  295. # [19:07] * dbaron thinks Bert would be better :-)
  296. # [19:07] <TabAtkins> RESOLVED: Accept in principle to change the grammar for 140 and note that we wont' use the additional capabilities (exact wording tbd).
  297. # [19:08] <TabAtkins> Bert: I'm going on a holiday soon, so if I work on it'll be in july.
  298. # [19:08] <TabAtkins> fantasai: How about you work on the grammar rather than the block thing, since I can do the block thing in June, but can't do grammar changes.
  299. # [19:08] <TabAtkins> Bert: That'd work.
  300. # [19:08] <Zakim> -ChrisL
  301. # [19:08] <Zakim> -David_Baron
  302. # [19:09] * Quits: bradk (bradk@67.188.133.45) (Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ )
  303. # [19:09] <Zakim> -arronei
  304. # [19:09] <Zakim> -plinss
  305. # [19:09] <Zakim> -Bert
  306. # [19:09] <Zakim> -fantasai
  307. # [19:09] <Zakim> -CesarAcebal
  308. # [19:09] <Zakim> -TabAtkins
  309. # [19:10] <Zakim> -SteveZ
  310. # [19:10] <Zakim> Style_CSS FP()12:00PM has ended
  311. # [19:10] <Zakim> Attendees were +1.858.655.aaaa, plinss, +1.650.253.aabb, TabAtkins, ChrisL, fantasai, +1.650.275.aacc, Bert, bradk, +49.238.aadd, CesarAcebal, arronei, +1.408.636.aaee, smfr,
  312. # [19:10] <Zakim> ... David_Baron, SteveZ, howcome
  313. # [19:10] * Quits: CesarAcebal (acebal@193.51.208.72) (Quit: CesarAcebal)
  314. # [19:12] * Quits: oyvind (oyvinds@213.236.208.22) (Quit: oyvind)
  315. # [19:22] * Quits: ChrisL (ChrisL@128.30.52.169) (Quit: Fire on main board error, client combusted)
  316. # [19:39] <dbaron> So where did the css3-color test suite get moved?
  317. # [19:39] <dbaron> It used to be in dev.w3.org CVS
  318. # [19:39] <dbaron> along with implementation reports
  319. # [19:41] * Quits: szilles (chatzilla@67.180.186.242) (Quit: ChatZilla 0.9.86 [Firefox 3.6.3/20100401080539])
  320. # [19:44] * Quits: arronei (arronei@131.107.0.111) (Client exited)
  321. # [19:44] * Joins: arronei (arronei@131.107.0.94)
  322. # [19:53] <dbaron> Hmmm. It seems the development copy of the css3-color test suite moved from dev.w3.org to some other repository, but I'm not sure where.
  323. # [20:03] <Bert> What makes you think that?
  324. # [20:05] * Joins: TabAtkins_ (tabatkins@216.239.45.4)
  325. # [20:09] <dbaron> http://dev.w3.org/CSS/css3-color-test-suite/src/ is empty
  326. # [20:09] <Bert> Oh I misread what you wrote. Was there ever something there?
  327. # [20:09] <dbaron> http://dev.w3.org/cvsweb/CSS/css3-color-test-suite/src/Attic/ says it moved to test.csswg.org
  328. # [20:10] <dbaron> but http://test.csswg.org/source/approved/css3-color/ is also empty
  329. # [20:10] <dbaron> so I'm not sure where it moved
  330. # [20:11] <plinss> http://test.csswg.org/source/cvs-import/css3-color-test-suite/ ?
  331. # [20:11] <plinss> http://test.csswg.org/svn/cvs-import/css3-color-test-suite/ for svn access...
  332. # [20:14] <dbaron> ah, ok
  333. # [20:17] <plinss> I think that's where fantasai simply moved the cvs files to, the proper tests should be living somewhere else in the repository
  334. # [21:39] <fantasai> hm, looks like I forgot to move them over into approved/
  335. # [21:40] <fantasai> that's where they /should/ be
  336. # [21:40] <fantasai> Ok, I'm heading to the airport. Feel free to text me if you've got further questions, should be on the ground until 5:30pm EDT
  337. # [22:09] * Zakim excuses himself; his presence no longer seems to be needed
  338. # [22:09] * Parts: Zakim (rrs-bridgg@128.30.52.169)
  339. # [23:20] * Quits: miketaylr (miketaylr@38.117.156.163) (Client exited)
  340. # [23:47] * Joins: shepazu (schepers@128.30.52.169)
  341. # Session Close: Thu Jun 03 00:00:00 2010

The end :)