/irc-logs / w3c / #css / 2011-09-21 / end

Options:

  1. # Session Start: Wed Sep 21 00:00:00 2011
  2. # Session Ident: #css
  3. # [00:15] <fantasai> TabAtkins: What was the name of your text editor
  4. # [00:15] <fantasai> ?
  5. # [00:18] <stearns> I think he was gushing about Sublime Text 2
  6. # [00:19] <fantasai> lol, ok
  7. # [00:19] <fantasai> I still haven't found one I really like, so I might give that a try
  8. # [00:20] <stearns> I like it, except for the shortcut differences between platforms (which could be fixed, I suppose)
  9. # [00:26] <fantasai> I've been using a combination of Geany and Kate, depending on the situation.
  10. # [00:27] <fantasai> Kate's great misfortune is that tab insertion is broken, and for whatever reason, copy/paste outside the application is broken. :(
  11. # [00:28] * fantasai couldn't convince the developers that having the Tab key insert tabs without triggering Mixed Spaces And Tabs Indentation Mode was a requirement of sane text editors
  12. # [00:30] <stearns> I'm still mainly using BBEdit, but I'm trying to wean myself off it with Sublime Text. The main thing I miss is BBEdit's file comparison tool
  13. # [00:40] * Joins: homata (homata@58.158.182.50)
  14. # [01:32] * Joins: myakura (myakura@203.136.181.177)
  15. # [01:36] * Quits: myakura (myakura@203.136.181.177) (Ping timeout)
  16. # [01:39] * Joins: karl (karlcow@128.30.54.58)
  17. # [01:49] * Quits: karl (karlcow@128.30.54.58) (Quit: This computer has gone to sleep)
  18. # [02:27] * Quits: dsinger (dsinger@216.178.108.111) (Quit: dsinger)
  19. # [02:57] * Quits: stearns (anonymous@192.150.22.5) (Ping timeout)
  20. # [03:27] * Quits: dbaron (dbaron@63.245.220.240) (Ping timeout)
  21. # [03:28] * Joins: karl (karlcow@128.30.54.58)
  22. # [03:39] * Joins: stearns (anonymous@50.132.9.217)
  23. # [04:27] * Joins: dbaron (dbaron@173.228.28.227)
  24. # [05:03] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
  25. # [05:04] * Quits: dbaron (dbaron@173.228.28.227) (Ping timeout)
  26. # [05:31] * Joins: homata_ (homata@58.158.182.50)
  27. # [05:32] * Quits: homata (homata@58.158.182.50) (Ping timeout)
  28. # [05:49] * Joins: homata (homata@58.158.182.50)
  29. # [05:50] * Quits: homata_ (homata@58.158.182.50) (Ping timeout)
  30. # [05:53] * Joins: dbaron (dbaron@173.228.28.227)
  31. # Session Close: Wed Sep 21 05:59:38 2011
  32. #
  33. # Session Start: Wed Sep 21 05:59:38 2011
  34. # Session Ident: #css
  35. # [05:59] * Disconnected
  36. # [06:00] * Attempting to rejoin channel #css
  37. # [06:00] * Rejoined channel #css
  38. # [06:00] * Topic is 'cool synchronized swimming'
  39. # [06:00] * Set by dsinger_ on Wed Sep 14 17:58:01
  40. # [07:22] * Quits: stearns (anonymous@50.132.9.217) (Quit: stearns)
  41. # [07:54] * Joins: arronei_ (arronei@131.107.0.111)
  42. # [07:55] * Quits: arronei (arronei@131.107.0.112) (Ping timeout)
  43. # [08:03] * Quits: homata (homata@58.158.182.50) (Ping timeout)
  44. # [08:27] * Quits: Florian (Florian@58.1.224.28) (Quit: Leaving.)
  45. # [08:35] * Quits: dbaron (dbaron@173.228.28.227) (Ping timeout)
  46. # [08:47] * Joins: dbaron (dbaron@173.228.28.227)
  47. # [08:52] * Quits: dbaron (dbaron@173.228.28.227) (Ping timeout)
  48. # [09:07] * Joins: dbaron (dbaron@173.228.28.227)
  49. # [09:11] * Quits: dbaron (dbaron@173.228.28.227) (Ping timeout)
  50. # [09:44] * Quits: arronei_ (arronei@131.107.0.111) (Ping timeout)
  51. # [10:33] * Joins: arronei (arronei@131.107.0.126)
  52. # [10:40] * Joins: Ms2ger (Ms2ger@91.181.20.245)
  53. # [11:39] * Joins: myakura (myakura@203.136.181.177)
  54. # [11:53] * Quits: myakura (myakura@203.136.181.177) (Client exited)
  55. # [11:54] * Joins: myakura (myakura@203.136.181.177)
  56. # [11:57] * Quits: myakura (myakura@203.136.181.177) (Ping timeout)
  57. # [12:48] * Joins: mollydotcom (mollyh@68.225.54.111)
  58. # [12:56] * Joins: myakura (myakura@203.136.181.177)
  59. # [13:25] * Quits: karl (karlcow@128.30.54.58) (Quit: Freedom - to walk free and own no superior.)
  60. # [14:01] * Quits: lhnz (lhnz@188.223.83.48) (Ping timeout)
  61. # [14:02] * Joins: lhnz (lhnz@188.223.83.48)
  62. # [14:19] * Quits: lhnz (lhnz@188.223.83.48) (Ping timeout)
  63. # [14:23] * Joins: lhnz (lhnz@188.223.83.48)
  64. # [14:59] * Joins: jdaggett (jdaggett@118.243.230.56)
  65. # [15:07] * Joins: karl (karlcow@128.30.54.58)
  66. # [15:31] * Joins: stearns (anonymous@50.132.9.217)
  67. # [16:16] * Parts: mollydotcom (mollyh@68.225.54.111)
  68. # [17:01] * Quits: anne (annevk@83.85.115.123) (Client exited)
  69. # [17:02] * Joins: anne (annevk@83.85.115.123)
  70. # [17:03] * Joins: florian (florianr@114.181.159.79)
  71. # [17:05] * Quits: stearns (anonymous@50.132.9.217) (Ping timeout)
  72. # [17:21] * Joins: arno (arno@192.150.10.200)
  73. # [17:33] * Joins: dbaron (dbaron@173.228.28.227)
  74. # [17:54] * Joins: oyvind (oyvinds@213.236.208.22)
  75. # [17:59] * Joins: Zakim (rrs-bridgg@128.30.52.169)
  76. # [17:59] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
  77. # [17:59] <RRSAgent> logging to http://www.w3.org/2011/09/21-css-irc
  78. # [17:59] <plinss> rrsagent, make logs public
  79. # [17:59] <RRSAgent> I have made the request, plinss
  80. # [17:59] <plinss> zakim, this will be style
  81. # [17:59] <Zakim> ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 6 minutes
  82. # [17:59] <Zakim> Style_CSS FP()12:00PM has now started
  83. # [17:59] <Zakim> +??P1
  84. # [17:59] <florian> Zakim, I am ??P1
  85. # [17:59] <Zakim> +florian; got it
  86. # [18:00] <Zakim> +plinss
  87. # [18:01] * Joins: Martijnc (Martijnc@84.192.44.100)
  88. # [18:01] <Zakim> +??P6
  89. # [18:01] <Zakim> + +1.206.552.aaaa
  90. # [18:01] * Joins: stearns (anonymous@50.132.9.217)
  91. # [18:02] <nimbupani> Zakim, aaaa is me
  92. # [18:02] <Zakim> +nimbupani; got it
  93. # [18:02] * Joins: antonp (4de003c4@64.62.228.82)
  94. # [18:03] * Joins: johnjansen (qw3birc@128.30.52.28)
  95. # [18:04] * Joins: jarek (jarek@83.27.243.103)
  96. # [18:04] <Zakim> + +34.93.329.aabb
  97. # [18:05] <Zakim> +dbaron
  98. # [18:05] <Zakim> +[Microsoft]
  99. # [18:05] <Zakim> +stearns
  100. # [18:05] <johnjansen> zakim, microsoft has johnjansen
  101. # [18:05] <Zakim> +johnjansen; got it
  102. # [18:05] <Zakim> +??P19
  103. # [18:06] <dbaron> Zakim, ??P19 is fantasai
  104. # [18:06] <Zakim> +fantasai; got it
  105. # [18:06] * Joins: smfr (smfr@17.212.152.232)
  106. # [18:06] * dbaron Zakim, who is on the phone?
  107. # [18:06] * Zakim sees on the phone: florian, plinss, ??P6, nimbupani, +34.93.329.aabb, dbaron, [Microsoft], stearns, fantasai
  108. # [18:07] * Zakim [Microsoft] has johnjansen
  109. # [18:07] <Zakim> +[Apple]
  110. # [18:07] <smfr> Zakim, Apple has smfr
  111. # [18:07] <Zakim> +smfr; got it
  112. # [18:07] <Zakim> + +1.415.832.aacc
  113. # [18:07] <antonp> Hi everyone, I'm one of those on the call
  114. # [18:07] <arno> Zakim, aacc is arno
  115. # [18:07] <Zakim> +arno; got it
  116. # [18:07] <antonp> I guess I would be +34.93...
  117. # [18:08] * dbaron Zakim, aabb is antonp
  118. # [18:08] <Zakim> +Bert
  119. # [18:08] * Zakim +antonp; got it
  120. # [18:08] <plinss> zakim, aabb is antonp
  121. # [18:08] <Zakim> sorry, plinss, I do not recognize a party named 'aabb'
  122. # [18:08] * Joins: howcome (howcome@88.89.78.85)
  123. # [18:09] * Joins: dsinger (dsinger@12.201.85.70)
  124. # [18:09] * Bert thinks it's very quiet on the phone...
  125. # [18:09] * Joins: Cathy (qw3birc@128.30.52.28)
  126. # [18:09] <johnjansen> Bert, you can always say something :-)
  127. # [18:09] * florian thinks a little quiet after today's typhoon doesn't hurt
  128. # [18:09] <smfr> is anyone else getting a nasty whine, or is it my phone?
  129. # [18:09] <dbaron> smfr, just you, I think
  130. # [18:10] <smfr> my phone whines when on mute! go figga
  131. # [18:10] <Zakim> +howcome
  132. # [18:10] <johnjansen> smfr, I had it for about 3 seconds, then it stopped
  133. # [18:10] * Joins: TabAtkins_ (qw3birc@128.30.52.28)
  134. # [18:10] <Zakim> +cathy
  135. # [18:11] * howcome : typhoon?
  136. # [18:11] <Zakim> + +1.281.305.aadd
  137. # [18:11] <TabAtkins_> Zakim, aadd is me
  138. # [18:11] <stearns> howcome: http://www.cbsnews.com/stories/2011/09/21/501364/main20109337.shtml
  139. # [18:11] <Zakim> +TabAtkins_; got it
  140. # [18:11] * Joins: szilles (chatzilla@24.6.120.172)
  141. # [18:12] * dsinger no typhoon here in LA...
  142. # [18:12] <smfr> plinss: you were very faint
  143. # [18:12] <smfr> still faint
  144. # [18:12] <smfr> Zakim, who's noisy?
  145. # [18:13] <Zakim> smfr, listening for 10 seconds I heard sound from the following: plinss (15%), [Apple] (38%), Bert (32%)
  146. # [18:13] * Bert imagines what the guy is saying into his phone: "Hi boss, a little accident, I think the rear tyre is gone, oh, and the rest of the car, too."
  147. # [18:13] <TabAtkins_> ScribeNick: TabAtkins_
  148. # [18:13] <Bert> zakim, mute me
  149. # [18:13] <Zakim> Bert should now be muted
  150. # [18:14] <TabAtkins_> plinss: Last minute addition - View Mode Media spec is at PR, and is blocked on MQ.
  151. # [18:14] <TabAtkins_> plinss: They want to know our status.
  152. # [18:14] <TabAtkins_> howcome: Is it blocking that MQ is not a Rec?
  153. # [18:14] <Zakim> +SteveZ
  154. # [18:14] <TabAtkins_> plinss: Yes, we're at CR. They can only refer to specs one level down from them.
  155. # [18:14] * dbaron Zakim, who is noisy?
  156. # [18:14] * Zakim dbaron, listening for 10 seconds I heard sound from the following: florian (60%), antonp (9%), plinss (14%), TabAtkins_ (54%)
  157. # [18:15] <florian> http://lists.w3.org/Archives/Public/www-style/2011Sep/0182.html
  158. # [18:15] <TabAtkins_> florian: If we have time, there was a mail about css-conditional we could discuss.
  159. # [18:15] <TabAtkins_> howcome: For MQ, annevk is not here right now.
  160. # [18:15] <TabAtkins_> fantasai: My understanding is that we're blocked on impls passing the test suite.
  161. # [18:16] <TabAtkins_> howcome: It may be that some of the deficit in impl is due to the more "exotic" features, like color-index.
  162. # [18:16] <TabAtkins_> fantasai: No, it's actually parsing issues. More serious.
  163. # [18:16] <TabAtkins_> dbaron: Arron pointed out some problems at the last F2F, which I fixed.
  164. # [18:17] <TabAtkins_> howcome: I suggest we ask annevk to be in here next week for this.
  165. # [18:17] <TabAtkins_> plinss: Sounds like we just need to get impls, then.
  166. # [18:17] <TabAtkins_> dbaron: Sounds like we should publish a new snapshot, since it fixed some issues.
  167. # [18:18] <TabAtkins_> plinss: Also, we have a new member now, Anton Prowse.
  168. # [18:18] <TabAtkins_> antonp: Thanks, glad to be here.
  169. # [18:18] <dbaron> welcome!
  170. # [18:18] <TabAtkins_> Topic: column-span and margin-collapsing
  171. # [18:18] <antonp> thanks!
  172. # [18:18] <TabAtkins_> florian: Last week we got to the point where we needed feedback from impls, and that's been sent.
  173. # [18:19] <TabAtkins_> howcome: It seems there's consensus to have collapsing when the column-spans have identical values, except for MS.
  174. # [18:19] <TabAtkins_> alexmog: I talked to our team, and it seems the use-cases that benefit from collapsing are kinda rare and you can do it in other ways.
  175. # [18:20] <TabAtkins_> alexmog: Last week we came up with several complicated scenarios, and I'd like to avoid complicating it more.
  176. # [18:20] <dbaron> johnjansen, do you happen to know if Arron had any other bug reports with the MQ test suite?
  177. # [18:21] <johnjansen> dbaron, I'm following up today on that.
  178. # [18:22] <TabAtkins_> alexmog: Say you're writing a document with a variable number of columns. When the element shrinks to a single column, does a column-span:all element collapse with surrounding elements?
  179. # [18:23] <TabAtkins_> alexmog: The idea of column-span is something that *can* span multiple columns, but you don't actually have a "separation" from the rest of the document, given the single-column case above. It's kinda more like floats.
  180. # [18:23] <TabAtkins_> fantasai: In response to the "single column col-spanning element", we already had a very specific proposal last week.
  181. # [18:24] <TabAtkins_> fantasai: It was that you only collapse columns if the specified value of column-span is the same. A column-span:all doesn't collapse with column-span:1 when the element is single-column.
  182. # [18:25] <TabAtkins_> fantasai: The question I had was about collapsing colspan element children's margins with the colspan's own margins.
  183. # [18:25] <TabAtkins_> fantasai: We were discussing whether the children's margins collapse with margins outside the colspan, but a related question is about whether they collapse with things outside of it.
  184. # [18:25] <TabAtkins_> howcome: In today's email, I included the children.
  185. # [18:25] <TabAtkins_> alexmog: Can't it be the same as floats?
  186. # [18:26] <TabAtkins_> fantasai: If they're block formatting roots, the margins don't collapse with anything.
  187. # [18:26] <TabAtkins_> florian: Conceptually, these aren't really related to floats.
  188. # [18:26] <TabAtkins_> alexmog: If you use column-span with a number, like originally specified, these are very similar to floats.
  189. # [18:26] <TabAtkins_> howcome: Agreed that they become more float-like with explicit span values.
  190. # [18:27] <TabAtkins_> howcome: I think we're in a gray area here. So I won't insist very hard on my solution, even if I support it.
  191. # [18:28] <TabAtkins_> florian: Another point - as long as we don't have css-conditional, if they want the equivalent of multicol without collapsing, they have to simulate it themselves.
  192. # [18:28] <TabAtkins_> howcome: That's a good argument. But I'd rather have MS pass the testsuite eventually than have this feature be slightly more perfect.
  193. # [18:29] <TabAtkins_> alexmog: We're not really concerned with how difficult this may be (it might be more difficult to *not* collapse).
  194. # [18:29] <fantasai> The two proposals are: 1) each column-spanning element is a BFC 2) each consecutive sequence of elements with the same 'column-span' value is wrapped in an anonymous BFC
  195. # [18:29] <TabAtkins_> alexmog: Our concern is that colspan may evolve into something more powerful, and if we make the behavior more complicated we can get into a very complicated situation with collapsing. And I think the use-cases aren't particularly convincing.
  196. # [18:29] <dbaron> fantasai, thanks, that's useful :-)
  197. # [18:30] <TabAtkins_> howcome: The situation on the table is the natural fallout from two implementations (Opera and FF).
  198. # [18:31] <TabAtkins_> howcome: If you're saying it's impossible to change the implementation, we can probably more easily change our impl.
  199. # [18:31] <TabAtkins_> howcome: But if we're talking about what we want, I want collapsing.
  200. # [18:31] <TabAtkins_> fantasai: The two proposals, really, are that (1) each colspan element is a BFC, and (2) each consecutive sequence of elements with the same column-span is wrapped in an anonymous BFC.
  201. # [18:32] <TabAtkins_> fantasai: Given that we have code to do this for tables, I don't think #2 is particularly difficult.
  202. # [18:32] <TabAtkins_> fantasai: It could be more difficult in some ways based on implementation [gives example in FF], but it's doable and not absurdly complicated.
  203. # [18:33] <TabAtkins_> fantasai: [further explains the implications of the two models]
  204. # [18:33] <TabAtkins_> howcome: Agreed, and I think both are achievable.
  205. # [18:34] <TabAtkins_> florian: I think it's difficult to say which way authors would want, but I personally think I would want collapsing.
  206. # [18:34] <TabAtkins_> fantasai: [brings up example with <h1 column-span:all>..</h1><p>...</p>, where the paragraph still wont' collapse.)
  207. # [18:34] * Quits: szilles (chatzilla@24.6.120.172) (Ping timeout)
  208. # [18:35] <TabAtkins_> alexmog: Do we want multiple consecutive elements with columns-span:all to act like they're in a single-column block?
  209. # [18:35] <TabAtkins_> TabAtkins_: That's basically the effect, yeah.
  210. # [18:35] <TabAtkins_> alexmog: Do we want to say that column-span floats collapse with sibling col-spans? And do margins collapse through colspans?
  211. # [18:36] <TabAtkins_> zakim, who is noisy?
  212. # [18:36] <Zakim> TabAtkins_, listening for 11 seconds I heard sound from the following: florian (56%)
  213. # [18:37] <TabAtkins_> alexmog: I'm hearing that if there are multiple consecutive column-spans, they should act like a normal single-column flow.
  214. # [18:37] <TabAtkins_> alexmog: And if that's a layout mechanism that's *kinda like* normal flow, but only looks like it at first glance, I think that's a confusing model.
  215. # [18:39] <TabAtkins_> fantasai: It's not creating something "kinda like" normal flow - you'd be creating a BFC wrapper, within which it's perfectly normal block layout.
  216. # [18:40] <TabAtkins_> alexmog: So with margin-collapsing enabled, the column-span is no longer a BFC itself.
  217. # [18:40] <TabAtkins_> florian: Right. A group of them is, but not each one individually.
  218. # [18:40] <TabAtkins_> alexmog: So margins do collapse through empty colspans, and floats within one colspan will affect other colspans.
  219. # [18:41] <TabAtkins_> fantasai: If the two colspans are in the same group, yeah.
  220. # [18:41] <TabAtkins_> alexmog: Okay. I'm not sure when we're going to implement that. Is that what Opera does (with floats affecting across colspans)?
  221. # [18:42] <TabAtkins_> howcome: I don't know.
  222. # [18:42] <TabAtkins_> florian: In theory it sounds reasonable, but I don't know what our implementation does.
  223. # [18:42] <TabAtkins_> alexmog: So I'm not sure we're coming to a consensus yet.
  224. # [18:43] <TabAtkins_> fantasai: I think we need an action item to poke around in FF and Webkit and see what they actually do.
  225. # [18:43] <TabAtkins_> fantasai: Also, asking authors what they actually think about this problem may be useful.
  226. # [18:43] <TabAtkins_> johnjansen: I'm trying to figure out scenarios where I use colspans and wanting margin-collapsing.
  227. # [18:43] <TabAtkins_> johnjansen: I don't think I want it.
  228. # [18:44] <nimbupani> fantasai: i am here
  229. # [18:44] <TabAtkins_> howcome: If you're in a situation without multicol at all, the margins will collapse in old browsers but not in new.
  230. # [18:44] <TabAtkins_> johnjansen: Yeah, but there are significant other issues with colspanning.
  231. # [18:45] <fantasai> The columnspanning element still won't collapse with non-columnspanning elements
  232. # [18:45] <TabAtkins_> alexmog: Should howcome take an action to describe exactly what should happen?
  233. # [18:46] <TabAtkins_> florian: Elika already described that. I think we should instead investigate to see what Opera actually does, and if it's different, we can decide whether we should change or the proposal should.
  234. # [18:46] <TabAtkins_> ACTION howcome: Investigate Opera's precise behavior around consecutive colspans, to see if they match Elika's "they're just wrapped in an anonymous BFC" proposal is accurate.
  235. # [18:46] * trackbot noticed an ACTION. Trying to create it.
  236. # [18:46] * RRSAgent records action 1
  237. # [18:46] <trackbot> Created ACTION-364 - Investigate Opera's precise behavior around consecutive colspans, to see if they match Elika's "they're just wrapped in an anonymous BFC" proposal is accurate. [on HÃ¥kon Wium Lie - due 2011-09-28].
  238. # [18:47] <TabAtkins_> ACTION tabatkins: Investigate WebKit's precise behavior around consecutive colspans, to see if they match Elika's "they're just wrapped in an anonymous BFC" proposal is accurate.
  239. # [18:47] * RRSAgent records action 2
  240. # [18:47] * trackbot noticed an ACTION. Trying to create it.
  241. # [18:47] <trackbot> Sorry, couldn't find user - tabatkins
  242. # [18:47] <TabAtkins_> ACTION tab: Investigate WebKit's precise behavior around consecutive colspans, to see if they match Elika's "they're just wrapped in an anonymous BFC" proposal is accurate.
  243. # [18:47] * trackbot noticed an ACTION. Trying to create it.
  244. # [18:47] * RRSAgent records action 3
  245. # [18:47] <trackbot> Created ACTION-365 - Investigate WebKit's precise behavior around consecutive colspans, to see if they match Elika's "they're just wrapped in an anonymous BFC" proposal is accurate. [on Tab Atkins Jr. - due 2011-09-28].
  246. # [18:47] <TabAtkins_> plinss: Should we gather author's opinions on this?
  247. # [18:48] <nimbupani> agree with florian
  248. # [18:48] <TabAtkins_> florian: I think authors are confused enough about margin-collapsing, so asking about corner cases in more complicated scenarios is unlikely to result in much useful.
  249. # [18:48] <TabAtkins_> plinss: Okay, we'll revisit next week.
  250. # [18:48] <TabAtkins_> Topic: Flexbox
  251. # [18:48] * Joins: szilles (chatzilla@24.6.120.172)
  252. # [18:49] <TabAtkins_> alexmog: I like the idea of the centering control being separate from Flexbox.
  253. # [18:49] <TabAtkins_> alexmog: Like 'overflow-position' or something.
  254. # [18:51] <TabAtkins_> TabAtkins_: Okay, so I recommend going with true centering, as I think that's what authors would expect, and then we'll solve the rest of this later.
  255. # [18:51] * Quits: myakura (myakura@203.136.181.177) (Client exited)
  256. # [18:51] <TabAtkins_> alexmog: I disagree. Other layout models use "safe centering", and I think we should be consistent for now.
  257. # [18:52] * fantasai let me know when to take over
  258. # [18:52] <TabAtkins_> TabAtkins_: In that case, I think I'd like to pursue this quickly, to allow true centering quickly.
  259. # [18:53] <TabAtkins_> alexmog: This only makes a difference during overflow, so we can address it as a feature of overflow, not a featur eof flexbox.
  260. # [18:53] <fantasai> ScribeNick: fantasai
  261. # [18:53] <fantasai> TabAtkins_: Ok, that seems fine. I'd want to go ahead and address that fairly quickly, because I think true centering is something ppl will expect when using flexbox to center stuff.
  262. # [18:53] <fantasai> TabAtkins_: Using 1-element flexbox for vertica/horizontal centering is very useful.
  263. # [18:53] <fantasai> TabAtkins_: Would we be ok defining this overflow property within flexbox spec?
  264. # [18:54] <fantasai> fantasai: My suggestion is to define it in flexbox for now, and if we find a better place later, we can move it.
  265. # [18:54] <fantasai> TabAtkins_: Ok, I will do that. Change spec back to safe centering, put together first draft of overflow control and put on list for discussion.
  266. # [18:54] <fantasai> TabAtkins_: Next issue was 'flex-flow' values.
  267. # [18:55] * nimbupani can be scribenick if necessary
  268. # [18:55] <fantasai> TabAtkins_: During the F2F, me, fantasai, and Alex got together and put together suggestion for how to address virtually every use case of how you want flex-box direction to respond to things
  269. # [18:55] <fantasai> TabAtkins_: You have pure physical,
  270. # [18:55] <fantasai> TabAtkins_: Physical axis, but responding to 'direction'
  271. # [18:55] <fantasai> TabAtkins_: And pure logical, responding to writing-mode
  272. # [18:56] <fantasai> TabAtkins_: This created many values for flex-flow
  273. # [18:56] * fantasai TabAtkins_ link?
  274. # [18:56] <fantasai> TabAtkins_: That did what it needed to do, but it was pretty complex both to read and understand
  275. # [18:56] <fantasai> TabAtkins_: e.g. deciding between 'row', 'horizontal', 'horizontal-ltr'.
  276. # [18:57] <fantasai> TabAtkins_: I suggest simplifying it down by using :ltr/:rtl
  277. # [18:57] <fantasai> TabAtkins_: And :ttb/etc.
  278. # [18:57] <fantasai> fantasai: You can't key off of computed style, so that won't work.
  279. # [18:58] <fantasai> TabAtkins_: Let's pretend we only have ltr and rtl.
  280. # [18:58] <fantasai> TabAtkins_: You don't need physical then
  281. # [18:58] <fantasai> TabAtkins_: ..????
  282. # [18:58] * fantasai gots confused
  283. # [18:59] <fantasai> TabAtkins_: Whenever you're specifying the direction of writing mode, that's pretty major, you can at the same time switch flexbox.
  284. # [18:59] <fantasai> TabAtkins_: Grid, which we're trying to maintain similarity with is completely logical based.
  285. # [18:59] <fantasai> TabAtkins_: If you're in an rtl context, first column is on right side. In vertical context, first "column" is a row.
  286. # [18:59] <fantasai> TabAtkins_: My proposal is to drop down to pure logical directions.
  287. # [18:59] <fantasai> TabAtkins_: That puts us in a similar situation to grid and loses us little power
  288. # [19:00] <fantasai> alexmog: So you're proposing pure logical?
  289. # [19:00] <fantasai> TabAtkins_: Yes.
  290. # [19:00] <fantasai> alexmog: I think that's ok.
  291. # [19:00] <fantasai> alexmog: I've looked at .. spec authors .. they all appeared to use horizontal and vertical, for the wrong reasons
  292. # [19:00] <fantasai> alexmog: Not switchable ...
  293. # [19:01] <fantasai> alexmog: In most cases more intuitive for ppl to use horizontal/vertical
  294. # [19:01] <fantasai> alexmog: What they mean is rows and columns
  295. # [19:01] <fantasai> alexmog: If your plan is top-level layout, you have a control there, you're applying .... can be anywhere, you can just put writing-mode on itself and it will be in whatever directio nyou want.
  296. # [19:01] <fantasai> alexmog: I think it'll be fine.
  297. # [19:01] <fantasai> TabAtkins_: This is a decent bit easier for us to implement, since WebKit operates in logical mode
  298. # [19:02] <fantasai> alexmog: I'm not buying implementation complexity argument.
  299. # [19:02] <fantasai> TabAtkins_: That change was made a little bit earlier.
  300. # [19:02] <fantasai> TabAtkins_: Any other flexbox issues?
  301. # [19:02] <Zakim> -arno
  302. # [19:02] <fantasai> fantasai: Any concerns with having logical values only?
  303. # [19:03] <fantasai> <silence>
  304. # [19:03] <Zakim> -stearns
  305. # [19:03] <fantasai> RESOLVED: Adopt 'flex-flow' with logical values only
  306. # [19:03] <TabAtkins_> RESOLVED: Make flexbox do "safe centering", add control for overflowing to allow switch to "true centering"
  307. # [19:04] <Zakim> -[Microsoft]
  308. # [19:04] <Zakim> -dbaron
  309. # [19:04] <Zakim> -nimbupani
  310. # [19:04] <Zakim> -cathy
  311. # [19:04] <Zakim> -SteveZ
  312. # [19:04] <Zakim> -[Apple]
  313. # [19:04] <Zakim> -TabAtkins_
  314. # [19:04] <Zakim> -plinss
  315. # [19:04] <Zakim> -howcome
  316. # [19:04] <Bert> zakim, unmute mu
  317. # [19:04] <Zakim> sorry, Bert, I do not know which phone connection belongs to mu
  318. # [19:04] * Quits: arno (arno@192.150.10.200) (Ping timeout)
  319. # [19:04] <Zakim> -florian
  320. # [19:04] <Ms2ger> Zakim, unmute Bert
  321. # [19:04] <Zakim> Bert should no longer be muted
  322. # [19:04] * Parts: florian (florianr@114.181.159.79)
  323. # [19:07] <Bert> https://www.w3.org/blog/CSS/wp-admin/index.php
  324. # [19:07] * Quits: Cathy (qw3birc@128.30.52.28) (Quit: Page closed)
  325. # [19:08] * Joins: miketaylr (miketaylr@24.42.93.245)
  326. # [19:10] * Quits: TabAtkins_ (qw3birc@128.30.52.28) (Quit: Page closed)
  327. # [19:16] <fantasai> http://www.css3.info/angles-in-gradients/
  328. # [19:19] * Quits: szilles (chatzilla@24.6.120.172) (Quit: ChatZilla 0.9.87 [Firefox 6.0.2/20110902133214])
  329. # [19:20] <Zakim> -Bert
  330. # [19:20] <Zakim> -fantasai
  331. # [19:20] <Zakim> -??P6
  332. # [19:21] <Zakim> -antonp
  333. # [19:21] <Zakim> Style_CSS FP()12:00PM has ended
  334. # [19:21] <Zakim> Attendees were florian, plinss, +1.206.552.aaaa, nimbupani, +34.93.329.aabb, dbaron, stearns, johnjansen, fantasai, smfr, +1.415.832.aacc, arno, Bert, antonp, howcome, cathy,
  335. # [19:21] <Zakim> ... +1.281.305.aadd, TabAtkins_, SteveZ
  336. # [19:21] * Quits: johnjansen (qw3birc@128.30.52.28) (Quit: Page closed)
  337. # [19:21] * Parts: smfr (smfr@17.212.152.232)
  338. # [19:21] * Parts: antonp (4de003c4@64.62.228.82)
  339. # [19:24] * Quits: oyvind (oyvinds@213.236.208.22) (Quit: oyvind)
  340. # [19:25] * Quits: jarek (jarek@83.27.243.103) (Quit: jarek)
  341. # [19:28] * Quits: stearns (anonymous@50.132.9.217) (Quit: stearns)
  342. # [19:59] * Joins: stearns (anonymous@192.150.22.5)
  343. # [20:16] * Quits: dbaron (dbaron@173.228.28.227) (Ping timeout)
  344. # [20:59] * Joins: dbaron (dbaron@63.245.220.240)
  345. # [21:10] * Parts: howcome (howcome@88.89.78.85)
  346. # [21:15] * Quits: nimbupani (Adium@24.18.47.160) (Client exited)
  347. # [21:19] * Quits: miketaylr (miketaylr@24.42.93.245) (Quit: miketaylr)
  348. # [21:20] * Joins: nimbupani (Adium@24.18.47.160)
  349. # [21:25] * Zakim excuses himself; his presence no longer seems to be needed
  350. # [21:25] * Parts: Zakim (rrs-bridgg@128.30.52.169)
  351. # [21:27] <hober> fantasai: want to pop into (freenode) #webkit to answer a question from hyatt re: orthogonal flows & css3-writing?
  352. # [21:49] * Quits: nimbupani (Adium@24.18.47.160) (Client exited)
  353. # [21:49] * Joins: nimbupani (Adium@24.18.47.160)
  354. # [22:05] * Quits: nimbupani (Adium@24.18.47.160) (Client exited)
  355. # [22:05] * Joins: nimbupani (Adium@24.18.47.160)
  356. # [22:20] * Quits: karl (karlcow@128.30.54.58) (Quit: Freedom - to walk free and own no superior.)
  357. # [22:21] * Joins: karl (karlcow@128.30.54.58)
  358. # [22:36] * Quits: Ms2ger (Ms2ger@91.181.20.245) (Quit: nn)
  359. # [23:06] * Quits: Martijnc (Martijnc@84.192.44.100) (Quit: Martijnc)
  360. # [23:57] * Quits: karl (karlcow@128.30.54.58) (Client exited)
  361. # Session Close: Thu Sep 22 00:00:00 2011

The end :)