00:00:29 JJ: Just say "HTML specifications" 00:01:08 DG: Cannot reference HTML5 as it is not a REc. 00:01:21 arno1 has joined #css 00:01:48 RESOLVED: "and future versions" added to to section 3.1 for issue 255. 00:02:10 Topic: issue 256 00:02:20 http://wiki.csswg.org/spec/css2.1#issue-256 00:03:02 DG: Just add "in HTML" 00:03:17 TC: *any version* of HTML. 00:04:28 PL: How about XForms? 00:04:39 ... Leave it as is. 00:04:55 RESOLVED: No change for issue 256. 00:05:00 http://wiki.csswg.org/spec/css2.1#issue-257 00:05:05 Topic: Issue 257 00:05:59 PL: I think we do want boxes to have properties. 00:06:03 DB: I agree. 00:06:07 PL: So no chnage? 00:06:17 RESOLVED: no change for issue 257 00:06:33 Topic: Issue 259 00:06:35 http://wiki.csswg.org/spec/css2.1#issue-259 00:07:43 DG: Indeed the 'inherit' keyword is never the computed value. 00:08:35 HL: In css3-values, 'inherit' is not the specified value. 00:08:46 DB: We might have changed that already. 00:09:24 DG: If 'inherit' is not returned as the specified value, that breaks editors. 00:09:47 EE: Have to distinguish from what the CSSOM says. 00:10:29 HL: There is a "cascaded value" also, that is what editors need. 00:11:14 ... The text in CSS 2.1 is consistent with css3-values. 00:11:47 PL: So no change? 00:11:54 JJ: And do something in level 3? 00:12:05 TA: Better not have level 3 contradict level 2. 00:12:57 HL/JJ: Bahevior isn't different, there is just different terms: cascaded values. 00:13:54 EE: Inconsistency between 3 and 2 is the missing term cascaded value. 00:14:02 ... Could add a note about that. 00:14:28 http://wiki.csswg.org/spec/css2.1#issue-260 00:14:46 ACTION elika: write a proposed text for issue 259 00:14:46 Created ACTION-310 - Write a proposed text for issue 259 [on Elika Etemad - due 2011-03-15]. 00:15:04 Topic: issue 260 00:16:29 EE: We added that note to clarify something else. Opinions differ on what is more or less confusing. So no change. 00:16:53 RESOLVED: no change for issue 260 00:17:07 Topic: Issue 261 00:17:34 DG: Nobody ever complained. Seems not worth a chnage. 00:18:02 PL: Is this already in Selectors spec? 00:18:19 DG: No, that has the same prose as 2.1. 00:18:26 arno has joined #css 00:19:14 PL: No chnage needed. Selectors is a clearer, that's good enough. 00:19:23 RESOLVED: No change issue 261 00:20:50 [Discussion about issues list and numbers, duplicates] 00:21:37 JJ: Issue 262 seems duplicate of 261 and 260. 00:22:00 http://wiki.csswg.org/spec/css2.1#issue-262 00:22:25 Topic: Issue 262 00:22:35 PL: Propose no change for issue 262. 00:23:01 RESOLVED: No change issue 262 00:25:43 homata has joined #CSS 00:26:41 [Discussion about what is best way to deal with minor editorial issues. At this point, just rejecting it is best, no risk of errors.] 00:26:56 http://wiki.csswg.org/spec/css2.1#issue-263 00:27:13 Topic: Issue 263 00:27:52 SZ: Maybe we can make a boilerplate text for all these editorial rejected issues. 00:28:09 ... For when we reply to the submitter of the issue. 00:29:13 PL: Seems same case again: Edit is nice to have, but not needed now. 00:29:22 RESOLVED: no change for issue 263 00:29:29 http://wiki.csswg.org/spec/css2.1#issue-264 00:29:36 Topic: Issue 264 00:30:11 DB: We discussed zero-height floats already today. 00:31:00 JJ: Did the earlier discussion affect this issue? 00:31:20 DB: No. The note in the issue is wrong. 00:32:44 RESOLVED: accept change proposed in the issue e-mail for issue 264. 00:32:56 Topic: Issue 265 00:33:14 RESOLVED: No change issue 265 00:33:22 Topic: Issue 266 00:34:06 http://wiki.csswg.org/spec/css2.1#issue-266 00:35:15 EE: I think we should make the suggested edits, they fix what we missied in the previous round for issue 120. 00:35:26 JJ: And the ones you were not sure about? 00:35:44 ... Issue 3 in the linked e-mail. 00:36:31 [it's about whether table-caption is block-level] 00:36:47 AE: Doesn't seem to hurt anything to make it block-level. 00:38:45 EE: If we don't fix it, we'll have to do it in errata anyway. 00:39:20 [Discussion about how 'overflow' might apply if flex box is added to CSS] 00:39:57 JJ: So take all of them, except issue 6. 00:40:26 s/all of/none of/ 00:41:53 EE: What does Bert think? 00:41:58 BB: I don't know yet. 00:42:40 RESOLVED: Accept issue 6, defer the others to the errata. 00:43:00 [Above is for issue 266] 00:43:08 Topic: Issue 267 00:43:10 http://wiki.csswg.org/spec/css2.1#issue-267 00:43:34 DB: It marches impls that I tested. 00:43:45 s/marches/matches/ 00:44:16 s/It/The proposed edit/ 00:44:45 sgalineau has joined #css 00:44:48 test is http://dbaron.org/css/test/2011/css21-issue-267 00:45:00 (question is which is on top) 00:45:26 actually, it doesn't test the issue 00:45:35 DB: I think it is editorial. 00:45:57 actually, hold on 00:49:12 268 and 269 should be http://lists.w3.org/Archives/Public/www-style/2011Jan/0087.html right? 00:49:21 DB: Two browsers do one thing, two do the other. 00:49:46 ... The proposal matches Opera nd Webkit. 00:49:52 s/nd/and/ 00:50:20 http://wiki.csswg.org/spec/css2.1#issue-268 00:50:22 RESOLVED: Accept propsoed edit for issue 267. 00:50:32 Topic: Issue 268 00:52:02 http://wiki.csswg.org/spec/css2.1#issue-203 00:52:15 http://lists.w3.org/Archives/Public/www-style/2010Sep/0665.html 00:52:15 Topic: Issue 203 (again) 00:52:42 JJ: Anton Prowse disagrees with our resolution. 00:54:17 -> http://lists.w3.org/Archives/Public/www-style/2010Sep/0665.html Anton's message 00:58:50 DB: The reason for the hypothetical top border is so as not to move the element unnecessarily. 00:59:05 AE: Test cases are all interoperable. 00:59:57 ... See margin-collapse-05 01:01:14 EE: Difficult to keep track of which clearance issues are the same issue. 01:01:52 s/margin-collapse-05/margin-collapse-clear-005 01:02:17 http://wiki.csswg.org/spec/css2.1#issue-268 01:03:46 http://lists.w3.org/Archives/Public/www-style/2011Jan/0644.html 01:03:50 resolved in that meeting 01:04:32 RESOLVED: 203 was already discussed and we allowed two behaviors. (See issues list) 01:04:48 s/move the element/move the element up/ 01:04:52 Topic: Issue 268 01:05:09 (I'm having trouble working out a testcase for why the hypothetical border edge is useful, though.) 01:05:30 EE: I thibnk the spec is correct. 01:06:19 alexmog has joined #css 01:06:43 Though actually, maybe I'm misremembering the purpose. 01:06:51 Maybe it's to prevent contradictions. 01:07:22 s/thibnk/think/ 01:07:22 tantek has joined #css 01:08:45 [People trying to find out what the issue is] 01:09:20 AE: Quite a few test cases for this. 01:11:06 actual issue: http://lists.w3.org/Archives/Public/www-style/2011Jan/0085.html 01:12:12 [Mumble mumble] 01:12:36 RESOLVED: No change for issue 268 01:13:54 [DB and EE discuss some case] 01:15:05 EE: All impls seem to agree on what the first formatted line is. 01:15:11 http://wiki.csswg.org/spec/css2.1#issue-269 01:15:15 Topic: Issue 169 01:15:21 s/169/269/ 01:16:44 arno has joined #css 01:17:06 EE: propose to change to edges of line box, instead of block. 01:17:53 RESOLVED: Use line box edges instea dof block edges in issue 269 01:18:03 http://wiki.csswg.org/spec/css2.1#issue-270 01:18:04 Topic: Issue 270 01:18:59 EE: I can propose a text. 01:19:30 DB: I might have some issues. I started implementing this. 01:19:50 arno1 has joined #css 01:20:02 RESOLVED: No change for issue 270. Do something in level 3. 01:20:09 http://wiki.csswg.org/spec/css2.1#issue-271 01:20:12 Topic: Issue 271 01:22:08 AE: I think the colon in the spec was intended to mean "e.g." 01:22:52 [Discussion about what issues to discuss. Skip all editorial?] 01:22:55 http://lists.w3.org/Archives/Public/www-style/2010Dec/0312.html 01:23:02 Anton's list of substantive issues ^ 01:24:25 DB: Turn the email into a wiki page so we can start dealing with it 01:25:10 http://wiki.csswg.org/spec/css2.1/anton-lc-2010 01:25:57 PL: What can we discuss now? 01:26:33 ... How dow we go through Anton's list? 01:26:44 AE: I have made comments on many of the issues. 01:27:36 ... Most of them I found need no change. 01:28:26 so Arron and Elika will get Anton's email into actionable issues 01:28:30 Topic: Test failures 01:28:34 discuss on wednesday. 01:29:35 PL: Background-fixed 4 and 5 were expecting a fix in Gecko. 01:29:48 DB: Give me 5 seconds... 01:30:51 SF: Last week we suggested to leave it undefined. 01:31:30 PL: I agree with undefined. Unless we have a proposal for a spec chnage. 01:31:40 DB: Gecko might take a month to fix. 01:32:26 EE: bg-pos may apply to image with no intrinsic size. 01:33:00 AE: Is it not already undefined? 01:33:15 DB: Might want to make it explicit, and say there is another spec that defines it. 01:33:56 The background position of background images with an intrinsic ratio and no intrinsic size is undefined in CSS2.1, see CSS3 Backgrounds and Borders. 01:34:34 RESOLVED: Change bg-pos of images as fantasai just wrote. 01:34:58 DB: So the test still needs fixing? 01:35:19 Topic: test bidi-breaking-2 01:36:02 EE: should be a may 01:37:15 http://test.csswg.org/suites/css2.1/latest/xhtml1/block-in-inline-relpos-002.xht 01:37:38 Topic: block-in-inline-relpos-002 01:38:53 PL: What do we do with this one? 01:40:00 [DB trying to find out why various browsers fail.] 01:40:27 arronei: http://test.csswg.org/source/contributors/fantasai/submitted/css2.1/bidi-breaking-002.xht 01:40:41 DB: Related to what we discussed earlier, about relative pos. affecting nested block elements. 01:41:21 ... Four browsers that all do different things. 01:41:32 myakura has joined #css 01:42:55 [DB and PL notice that two versions on diff. platforms of Opera do different things, too.] 01:43:01 bidi-breaking-002 should work now; removed the HTML
bit of the test (since that's up in the air anyway) 01:44:06 [People looking over other people's shoulders to see what various browsers do on different platforms...] 01:44:47 DB: Somebody should take an action to figure out what to do. And not me. 01:44:53 AE: I can do it. 01:45:41 ACTION Arron: propose a solution for block-in-inline-relpos-002 01:45:41 Created ACTION-311 - Propose a solution for block-in-inline-relpos-002 [on Arron Eicholz - due 2011-03-15]. 01:49:51 content-computed-value-001 01:50:33 Topic: content-computed-value-001 01:50:41 RESOLVED: Remove the test 01:51:30 stearns has left #css 01:52:42 Topic: replaced-intrinsic-ration-001 01:52:44 we're going through the blocking tests on http://wiki.csswg.org/test/css2.1/blocking 01:52:48 s/ration/ratio/ 01:53:09 DB: Close to a patch for Gecko, just need to fix a few more existing tests. 01:54:18 PL: It seems to be testing multiple things. 01:54:23 EE: [something] 01:54:39 PL: Are you going to define behavior? 01:54:49 EE: I might want to fix this. 01:55:16 ... I will propose text. 01:55:49 ... For the spec. 01:56:15 HL: Is this an SVG issue? 01:57:36 EE: Yes, affects all SVG that doesn't have a fixed size (i.e. scalable SVG) 01:57:47 RESOLVED: Change the spec in some way. 01:57:50 EE: Proposal is to make sizing of replaced elements with intrinsic ratio but no size undefined. 02:00:28 RESOLVED: ... and put the current rule in level 3 instead. 02:00:42 BB: It was put in on request from SVG wasn't it? 02:01:00 Topic: uri-016 02:01:51 http://test.csswg.org/suites/css2.1/nightly-unstable/html4/uri-016.htm 02:01:53 no, it was put in a long time ago because it was it wasn't defined 02:02:00 the test is failing because UAs misinterpreted SVG 02:03:39 kennyluck has joined #CSS 02:03:59 PL: We don't have the exit criteria from other CSS modules in the CSS 2.1 spec, 02:04:21 ... Difference is about experimental builds. 02:04:33 ... Didn't we resolve to fix that already? 02:05:13 http://wiki.csswg.org/spec/css2.1#issue-272 02:05:45 RESOLVED: Update CSS 2.1 exit criteria to the current (CSS3 standard) exit criteria, minus the 30-day implementation requirement. 02:07:11 [End of meeting for today] 02:10:39 rrsagent, draft minutes 02:10:39 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 02:10:49 rrsagent, make logs public 02:13:16 Hmm, forgot to tell rrsagent that the meeting spanned midnight. :-( 02:55:06 miketaylr has joined #css 03:22:29 bradk has joined #css 03:34:49 bradk has joined #css 03:54:37 Xaxio has joined #css 04:55:56 tantek has joined #css 05:00:23 fantasai2 has joined #css 05:04:50 homata has joined #CSS 06:01:15 dsinger has joined #css 06:07:12 jdaggett has joined #css 06:19:52 Arron has joined #css 06:21:21 sylvaing has joined #css 06:39:18 plinss_ has joined #css 06:41:39 anne has joined #css 06:44:59 dbaron has joined #css 06:48:39 arno has joined #css 07:04:24 homata__ has joined #CSS 07:04:27 TabAtkins_ has joined #css 07:20:16 arno1 has joined #css 07:33:07 plinss_ has joined #css 07:38:06 Martijnc has joined #css 07:58:39 homata has joined #CSS 08:07:55 plinss_ has joined #css 08:38:23 homata__ has joined #CSS 09:45:55 plinss_ has joined #css 09:46:07 Ms2ger has joined #css 09:52:22 lhnz has joined #css 10:27:50 plinss_ has joined #css 10:47:45 homata has joined #CSS 10:47:50 plinss_ has joined #css 11:03:15 arronei has joined #CSS 11:20:43 Martijnc has joined #css 16:55:23 RRSAgent has joined #css 16:55:23 logging to http://www.w3.org/2011/03/08-css-irc 16:55:31 invite zakim, #css 16:56:19 Zakim has joined #css 16:57:56 stearns has joined #css 17:00:45 sylvaing has joined #css 17:02:07 TabAtkins_ has joined #css 17:02:33 glazou has joined #css 17:02:55 mihara has joined #css 17:03:08 shan has joined #css 17:03:13 johnjan has joined #css 17:03:29 ScribeNick: fantasai 17:03:54 Arron has joined #css 17:03:58 Topic: Agenda 17:04:28 Steve: Request toput tokyo workshop dates today 17:04:37 ?: multicol today 17:04:54 Arron has joined #css 17:05:24 glazou: module template tomorrow 17:05:39 dbaron has joined #css 17:05:43 glazou: pull tokyo dates and multicol for today, keep rest for tomorrow 17:05:53 glazou: Start with Adobe's proposal 17:06:02 Topic: Adobe's Template Proposal 17:06:22 s/Template/Regions/ 17:06:51 howcome has joined #css 17:07:22 smfr has joined #css 17:07:30 Arno: I'd like tot talk to you a little bit about things we work on we're calling CSS "Regions" 17:07:45 arno: Would like your feedback on whether it's interesting, going in an interesting direction, etc. 17:07:58 bradk has joined #css 17:08:04 arno: It started by us talking to our customers, especially print customers using InDesign t do fancy layouts 17:08:11 arno: e.g. Conde Nast 17:08:24 arno: They want to bring the experience ppl have on paper into digital media 17:08:34 Kazutaka has joined #CSS 17:08:40 arno: We started experimenting, and some of those magazines are already available on the iPad 17:08:51 arno: We very quickly ran into some limitations 17:09:01 arno: e.g. Wired has very complex layouts 17:09:09 arno: We tried using various technologies to represent those layouts 17:09:29 arno: But in this version we had to use images to represent each page 17:09:47 arno: It's a lot of work, since the designers have to do layouts twice once for layout and portrait 17:09:56 arno: With different device aspect ratios, it's even more work 17:10:01 arno: Not a good solution 17:10:21 arno: Not the case for everyone -- some customers have very simple layouts, close to templates, can use HTML to represent their ocntent 17:10:27 arno: which has lots of benefits 17:10:41 arno: We want to find the way to bridge the gap between HTML layouts you can do today, and what you can do on paper 17:10:52 arno: You have very sophisticated layout of text, interaction of graphics and text 17:11:08 arno shows pages with text flowing around contoured images, fitted to shaped regions 17:11:28 arno: We want to be able to find ways to represent these sophisticated layouts in HTML and CSS 17:11:38 arno: We studied these and came up with a proposal tha we think solves the problems. 17:11:54 arno: We wanted to make sure what we were thinking about was implementable 17:12:09 arno: So we started investigating implementing it 17:12:29 arno: BTw, another use case is of course printing, which would benefit from sophisticated layouts 17:12:35 arno: We started experimenting with WebKit 17:12:47 arno: I'm going to show you some screenshots of some things, and then also live demos 17:12:56 arno: Starting with very simple and basic things, it's columns 17:13:02 arno shows a 3-col layout 17:13:10 arno: You can do this with multicol 17:13:22 arno: You have some fairly simple markup -- three divs and a heading 17:13:34 divs are labeled region1 through 3 17:14:21 prior to that there's another div called article-content, which includes a heading and then the flow content (paragraphs) 17:14:43 the regions are styled to be boxes floating side by side 17:15:03 article-content is assigned a flow-thread: main; 17:15:28 the region3 divs are assigned display: region; region-thread: main; 17:16:03 howcome: Those region elements are only there to give the layout 17:16:18 Simon: What happens to the content of the region elements? 17:16:25 mollydotcom has joined #css 17:16:46 jdaggett: It would be better to not put the layout structure as markup in the document. 17:17:01 arno: Next example, we add an image sitting on top of the two first columns 17:17:21 arno: You adjust the two columns to shorten them, and then place the image 17:17:37 glazou: You cannot make content flow from one region to another, right? 17:17:43 arno: correct 17:18:02 jdaggett: I'm wondering if you looked at some of the other proposals.. 17:18:29 plinss: This is not the interesting case. This is a very basic case. 17:18:33 TabAtkins_ has joined #css 17:18:43 jdaggett: But I think this is added semantics on top of one of the other layout approaches 17:19:03 arno: One of the things you can do is to specify the order in which content flows 17:19:28 arno: you do this by specifying region-index: on the region elements 17:19:43 arno: Since the divs are just divs, you can also do more sophisticated things like applying transforms. 17:19:55 arno: Another thing we've been talking about are exclusions 17:20:05 arno: Which is saying "I want the text to avoid these areas" 17:20:14 arno: So you can have images that encroach on the text 17:21:04 arno: Our proposal is to use an exclusion-shape property that takes coordinates which you apply to an element, and then assign exclusions: "#idofelement" to the flow content 17:21:17 ...could also use alpha area of image 17:21:27 jdaggett: SVG path or mask would make more sense 17:21:38 http://www.w3.org/blog/CSS/2007/07/03/rotations_and_non_rectangular_floats 17:22:13 fantasai: There was a proposal from Bert for doing this by adding a single keyword to float. 17:22:47 arno: also want to specify geometric shapes even if there's no image 17:22:51 arno: You also want to do this for e.g. a circular pull-quote 17:23:27 (For the old, 1996(!) idea for flow around non-rectangular images: see 'contour' in https://www.w3.org/Style/Group/css3-src/css3-box/Overview.html#the-float-property) 17:23:34 (For an idea for non-rectangular/connected regions: https://www.w3.org/Style/Group/css3-src/css3-layout/Overview.html#chaining-slots-the-chains-property) 17:24:42 [discussion of margin around the alpha shape] 17:24:50 (The "margin" around non-rect images in the contour idea is given by areas that are almost transparent, say 99%) 17:24:58 http://www.w3.org/TR/WD-layout 17:25:06 arno: we just started with the coordinates since that was simple to implement and could do everything 17:25:34 discussion of float intrusions that break a line in half 17:26:14 plinss: We have a convention, starting with clip property, of using functional notation with shape e.g. rect(...) 17:26:20 plinss: That would let you have different shapes 17:26:24 plinss: more easily 17:26:44 plinss: The other thing is you have a property linking from one to the other 17:26:55 plinss: to define the exclusion 17:27:17 plinss: What is the coordinates relative to? 17:27:44 alex: What defines the tightwrap, content wnats to tightwrap, or shape wants everything to wrap around it? 17:27:57 alex: In CSS1, it was float requesting wrapping 17:28:42 alex: So you could have a boolean, wrap around stuff, or don't wrap around stuff. 17:29:42 alex: if you want to control, e.g. this bfc doesn't avoid floats, or this non-bfc avoids floats 17:29:48 discussion of bfcs 17:30:01 Steve: Think of the part that intrudes as being part of the bfc 17:30:37 dbaron: Well, if we have a BFC due to scrolling, you don't want any floating content intruding into that content and forcing relayout on scroll 17:30:39 hyatt has joined #css 17:31:01 alex: But that's a special case. overflow: hidden; it's totally reasonable to wrap around 17:31:19 arno show s an example of columned text flowing around the coyote 17:31:34 arno shows a page layout that uses this as a component 17:32:29 arno pulls up a live demon 17:32:53 arno: Here's the example with columns that have been transformed to be crooked 17:33:09 arno edits the contenteditable content: the content flows from one column to the other 17:33:32 plinss: What about property inheritance? 17:33:51 plinss: Does content flowing into a region inherit from the region or its element tree parent? 17:34:28 Steve: There is a desire to allow inheritance from regions (in its equivalent model) 17:34:41 Steve: We have a special function, like inherit-from-region, that does that 17:34:53 Steve: What's there doesn't quite match CSS's model 17:35:00 plinss: I looked at that and couldn't figure out how it works 17:35:57 Steve: This would be similar to the way ::first-line works 17:36:22 fantasai: If you're doing inheritable properties, you'll probably want selectors too. So you can change not just the color of the text overall, but e.g. links inside the region 17:36:33 fantasai: If you go down this route, people will want to go in that direction 17:37:00 ... 17:37:08 howcome: Have you shipped content with this? 17:37:12 arno: No, just experimental 17:38:02 howcome asks about resizing and reflow 17:38:25 howcome: With multicol, you'd add a third column as the page gets wider 17:38:50 howcome: what would you do here? is it tied only to two columns? 17:39:13 Steve: This is with fixed regions, each explicitly specified. 17:39:25 Steve: It needs to be adapted to work with multicol, flexbox, grid layout, etc. 17:39:30 Steve: The key concept is the threads 17:39:37 Steve: and the concept of exclusions 17:39:39 mollydotcom has left #css 17:40:05 jdaggett: So what you're saying is not the syntax that's important, but those two concepts that are important. 17:40:20 Steve: Yes. There's still some work to do to make this fit into CSS well 17:40:51 plinss: Another issue is that you're using 'display' to make something a region. You should use something else, so that we can control display of the regions 17:41:24 maybe the 'content' property would work? 17:41:48 e.g., content: flow(main), or content: flow(main, 2) to give indices 17:41:59 plinss: In most cases, you want to use the other layout systems you have, and just have content flow differently through it 17:42:18 Phil: What happens if you run out of content? 17:42:29 (or too much) 17:42:36 arno: It's a good question. 17:43:33 fantasai: The other thing is that the regions shouldn't be empty elements in the document, they should be separate. SO you odn't have to build the layout into the document content 17:44:01 Bert: César and I worked on some of this flow threading with his studies on the Template module 17:44:14 extend the slot concept from css3 template layout to allow for the specification of positioned slots 17:44:30 Bert: One thing that became clear was that you need a baseline grid, so that the lines are consistently placed 17:45:02 ...so that if you have two regions above each other (with different horizontal positions), you don't have a gap due to having half a line at the bottom of the first 17:45:21 need a baseline grid for content today (even if it's not all part of the same flow) 17:45:29 Bert: Other comment, when you were moving the image in the demo, you have some cases where the content shows up in holes in the image. In howcome's proposal, the content always had to be on the outside 17:45:48 Bert: So you wouldn't split the content into two columns 17:48:02 glazou: You want to be able to flow text inside, e.g. a bowl 17:48:07 fantasai: You're talking about two different things. 17:48:56 glazou clarifies by drawing a picture 17:49:06 11|222|33 17:49:13 jdaggett has joined #css 17:49:17 44\555/66 17:49:33 77---88 17:49:49 arno's example doesn't actually allow a line to be split by the float 17:50:10 but it does allow the image to define the contour on both the left and right side of the line, if it's bowl-shaped 17:50:21 (Example XXII in https://www.w3.org/Style/Group/css3-src/css3-layout/Overview.html#chaining-slots-the-chains-property defines a reading order over partly side-by-side regions) 17:50:23 glazou's example intrudes into the text splitting the line into multiple pieces 17:50:46 howcome: So what happens today if you have too much content for the regions? 17:50:49 arno: It will not display 17:51:05 smfr: What if you put overflow: scroll on the last region? 17:51:31 Tab: Could think of this as a kind of overflow mode 17:51:44 css3 template layout defines a grid of anonymous slots. you could imagine also allowing it to define anonymous positioned slots (that other content could then flow around/avoid) 17:51:46 Tab: Would clarify what overflow: scroll means on the first region -- nothing 17:53:00 peterl: (responding to hyatt's first comment) I'd actually like to see the other way - this replacing template's slot concept. 17:53:07 > 17:53:19 div { positioned-slots: sidebar, masthead, body; } ::slot(sidebar) { position: absolute; left:100px; top:100px; box-shape: ; } 17:53:54 howcome: We need to make sure this wokrs in a reusable way for longer articles, for printing 17:54:04 css3 template layout supports per-page templates too 17:54:06 Bert talks about his attempt to extend slots concept in template-layout 17:54:11 peterl: I'd like to be able to define regions in an @page rule. 17:55:05 (Extend in the sense of automatic repeating the same layout template if there is more room, without need for media queries.) 17:55:41 alexmog has joined #css 17:56:00 i would try to separate out all the concepts here. there is (1) content flowing across linked regions, (2) the ability to define an irregular external shape that content flows around, (3) the ability do specify an irregular shape that content inside fits to, and (4) the definition of placed regions themselves that content can flow around 17:56:22 glazou: Do you want to standardize this in CSSWG? 17:56:46 arno: If you're interested in this, yes. 17:57:09 jdaggett: Before we get to the stage of these guys spending time putting together a proposal 17:57:38 jdaggett: I think it would make more sense for your group to start by reviewing the modules we already have, and see what you would need to /change/ to make them work for you 17:57:52 jdaggett: The cases you're trying to solve are valid, but the syntax you're doing is grotty 17:58:00 shonda has joined #css 17:58:08 smfr: I agree, we should avoid adding another module and try to work this into e.g. Template Layout 17:58:44 linked regions might make sense in Template, but would exclusions? 17:59:18 howcome: We can't keep adding more and more advanced layout systems. We should try to merge them 17:59:48 tantek has joined #css 17:59:55 Steve: There are several key concepts here. One is the threading concept, which would fit well in many of our layout specs 17:59:57 the concept of content flowing around a positioned shape and/or of irregular shapes is just new properties for positioned or floating elements (depending on what approach you decide to take) 18:00:24 Steve: The other key piece is the exclusion piece, which is separate but also important 18:00:26 the concept of flow across containers should IMO be limited to anonymous models (multicol, template layout) 18:01:06 dbaron: We could use 'content' property to assign content to a flow, e.g. with a flow() function 18:01:10 i think just using positioned elements as the way to flow around content instead of floats, and then use positioned element z-index rules to say whether you avoid or not might work fine 18:01:18 Steve: That's a pull model, this is a push model. 18:01:19 e.g,. establish a stacking context, then your internal stuff doesn't propagate out 18:01:23 auto z-inxex it does, etc. 18:01:31 Steve: The third approach is to define a mapping between the twol. 18:01:42 Steve: Those are 3 different ways of looking at the problem. 18:01:48 Steve: Layout and grid are using a push model. 18:01:53 Steve: I agree you could use a pull model as well 18:02:02 Bert: There's a pull model in the cross-references in GCPM 18:02:19 q+ 18:02:49 Bert explains hyatt's comment above 18:03:15 Bert: wrt #3, I was wondering if that should be extended to also make the text exactly fit a certain shape by e.g. making it smaller or larger 18:05:21 Steve: That was in the proposal, too, arno just didn't mention it 18:05:32 Tab likes hyatt's comments 18:05:45 and strongly agrees with using anonymous boxes instead of real elements to define the regions 18:06:36 Steve: Classic example of pushing content into an external region that only shows up when needed is footnotes. 18:06:48 Tab: You can tell the region to only exist if it has content inside of it. 18:07:13 glazou: Another way of specifying exclusions, used many years ago, is like background image 18:07:32 glazou: You position the image and it defines an exclusion 18:07:58 Tab says something that I didn't quite follow.... 18:08:03 @page { positioned-slots: header, sidebar, body(col1, col2) ::slot(col1) { ... } ::slot(col2) { ... } } You could imagine the "chains" linking being done without a property, e.g., in the specification of the template itself... see body(col1, col2) example 18:08:27 ... 18:08:48 Steve: In a gridlike or template-like layout you'd like to position to cell boundaries in that model, which doesn't quite fit into the bgpos model. 18:09:24 glazou: Desktop publishing software can do that. What is the best option in terms of you for CSS to be able to translate those layouts into CSS layouts and vice versa? 18:09:56 glazou: If we run into that, people are going to base layouts in CSS, so it needs to be compatible with desktop software 18:10:04 Steve: FYI, glazou writs an editor 18:10:11 glazou: Need to allow round-tripping 18:10:29 arno: For us the key thing is to have the expressiveness. We are willing to take the cost on the tooling side. 18:10:40 arno: round-tripping is a good point to bring up, though 18:10:57 Tab: The only problem with defining exclusions purely on the content element is that it may then be difficult to position content that should sit in those exclusions (like a callout) in an appropriate manner. But Positioned Layout, which I'll work on later this year, should be able to solve this - you can abspos an element relative to the content element, and specify the exclusion and callout using nearly identical rules as a bg-position and as top/right 18:11:38 arno: want for an author to be able to us the tools, but more importantly the concepts they are used to 18:12:24 all applause Arno's pres and demo 18:12:52 arno has joined #css 18:30:57 arno1 has joined #css 18:31:54 mihara has joined #css 18:33:14 alex: What we have here in this version of the spec, it tries to roll into it all the feedback we've had so far 18:33:18 if somalex: If something is thatere, doesn't necessarily mean we have the final overall picture 18:33:27 alex: We're trying to be inclusive here, we wanted to produce a version of how it might work with the feedback 18:33:31 which spec? can we have a link? 18:33:47 alex: We're getting to the shape where we can think about how it integrates with other specs, e.g. merge with Template Layout 18:33:57 alexmog: If there something we didn't get here, doesn't make sense to have there, let's discuss 18:34:30 Markus: Our main goal was to address the feedback from the last F2F, align with Template Layout, figure out integration 18:34:37 Markus: Also think more about print layout and lines 18:35:26 Thanks everyone for the great feedback! 18:36:14 http://dev.w3.org/csswg/css3-grid-align/ 18:36:17 Phil: Hi, my name is Phil and I'm from Microsoft, and I'm one of th editors on the CSS Grid specification 18:36:41 Phil: Recap of feedback was to think in lines, not just thinking in rows and columns 18:36:58 Phil: also think about naming lines to simplify maintenance so you don't have to renumber when you change things 18:37:05 Phil: We also thought about naming regions of space. 18:37:20 Phil: Template Layout does this, so we looked into incorporating that idea 18:37:37 Phil: Also thought about ::slot() pseudo and putting multiple elements into a slot 18:37:51 Phil: ... a default slot 18:38:03 Phil: I'll start by just walking through this and summarizing. 18:38:19 Phil: Grid is not a table. Can do things tables can't do, e.g. hav cells overlap 18:38:41 Phil: It's similar positioning in that regard; can be considered an alternate grid system for positioning 18:39:37 Phil: We think people will use grid to do page layouts, form layouts, etc. 18:39:47 Phil: We want layouts to be able to adapt to available space 18:39:54 Phil: So we have some concepts 18:40:01 Phil: auto sizing to the size of the content 18:40:05 Phil: min/max functions 18:40:16 Phil: fractional units, allocating remaining space 18:40:34 Phil: You declare a grid by setting its display to grid 18:40:42 Phil shows Example 1 18:41:11 Phil: Declare a grid with "display: grid", set grid columns and rows 18:41:32 position to grid 18:41:48 Phil moves to next section 18:42:12 Phil shows template layout in grid 18:42:39 Phil: assign into template regions with 'grid-cell' property 18:42:45 Phil: We're not using the position property here 18:42:59 Phil shows slider control example 18:43:32 Phil: In this example we're using an alternative syntax that names the grid lines 18:43:57 Phil: To name a grid line, you just specify a string before the measurement 18:44:54 Phil: You can assign starting and ending lines to an element to position it in the grid 18:45:03 Phil: There are tracks, lines, and cells in the grid model 18:45:13 Phil: Tracks are the columns and rows of the grids 18:45:46 Phil: grid-columns: 150px 1fr; creates two columns, a 150px column and a remaining space column 18:45:54 Phil: This gives us 3 lines 18:46:49 Phil: In old spec you would define cells implicitly by giving a span property, and then could align content within that cell (which could span multiple row-col intersections) 18:46:57 Phil: in new spec you can define those cells explicitly 18:47:28 ... 18:47:32 Phil: grid-cell speudo 18:47:50 Phil: In template module you would define of the grid-cell with the template string 18:48:00 bradk has joined #css 18:48:06 Phil: Here you can create a grid-cell [somehow] 18:48:53 Phil: by using the grid-cell pseudo element, and giving it positions 18:49:10 Phil: e.g. #grid::grid-cell("cell") { grid-column: .. ; grid-row: ...; } 18:50:03 Phil: This creates a named cell, that you can then assign into just like you can assing into template-created named cells 18:50:58 dbaron: maybe split this example using markup instead of a comment, it's not clear they are two different approaches to the same thing 18:51:38 Steve: So you wanted to create a cell on the grid-line strucutre using pseudo-element 18:52:01 sylvaing: That's similar to what hyatt proposed earlier, with the ::slot() syntax creating a flow target 18:52:49 Brad: Can you assign other properties to a grid cell? 18:52:55 Phil: Some, but mostly positioning stuff 18:53:28 Tab: If you have a slot created by the template property, can you reposition it using grid-rows and grid-columns? 18:53:34 Tab: I would prefer "no" :) 18:54:19 Tab: I would not want a designer to be confused about their slot moving around because a later definition moved it 18:54:52 plinss: I would prefer the cells to be defined where the template is defined. 18:55:01 Markus: You could do that too 18:55:35 plinss: I would prefer to have the template declaration to also include a list of defined cells 18:56:06 plinss: You could then use ::grid-cell() to style the slot 18:56:37 Phil: That starts making the template declaration really long and complicated. 18:56:44 Phil: I like breaking it up into bite-sized chunks 18:57:39 plinss: As a designer, I'd think of the template as a single thing. Don't like breaking it out like this. 18:58:17 plinss: I don't like the template ASCII art thing. 18:58:45 fantasai: You could use an @rule to put all the pieces together and give it a name @template mylayout { .... } 18:59:20 various people object and declare their love for the ASCII art thing 18:59:34 can't hear a word plinss is saying 18:59:36 plinss: I think it's very 80s and very constrained and very silly 18:59:55 Markus: I was exactly in your camp when I first looked at it. We want to make it cleaner, more industrial strength, etc. 19:00:06 Markus: But then we started to try building something a little more complex with it 19:00:15 : #grid::grid-cell("cell-start" "cell-end", "cell-start" "cell-end") { grid-cell-name: "cell" } 19:00:33 Markus: But as you start to have more complex grid structures, the ASCII art structure very easily and clearly represents those layouts 19:00:54 Markus: The problem is that it's not industrial strength. You run out of characters 19:01:00 howcome: Can we get some from the Chinese? :) 19:01:19 Markus: You have the power of both. 19:01:41 Phil: grid cells is a superset of template since you can do overlapping cells 19:02:14 plinss: What happens if the "d"s in a template don't form rectangles? 19:02:22 Tab: You can't do that 19:02:29 Tab: They have to be rectangles 19:02:39 plinss: I have to draw rectangles in ASCII art? 19:02:47 glazou: It's ugly 19:03:03 Tab: As someone who edits CSS in a plaintext editor, I love this. 19:03:13 glazou: My goal is to make CSS editable without a text editor. 19:03:25 glazou: Without knowing about CSS. 19:03:40 Tab: It is really easy to create a UI for the ASCII art. 19:03:53 Markus: We are open to either way. 19:04:38 Steve: I agree with what Markus just said, which is that the argument is a red herring, provided that there is a clear relationship among each method of specifying the grid 19:05:15 (The "ASCII art" was inspired by proprietary WYSIWYG template editors used by two mobile companies; although their output was HTML tables, not CSS.) 19:05:37 Steve: and that you cand round-trip between the two 19:06:09 fantasai: well, ascii art is a subset of the functionality of the other method, so you can't round-trip but there is a clear mapping between the two 19:06:29 (Cesar has a WYSIWYG editor for templates themselves, made by a student.) 19:06:30 Steve: yes 19:06:38 Steve: that satisfies my requirements 19:07:09 Steve: talks about assinging multiple inlines into a single slot 19:07:14 Phil: I wasn't too clear on that point 19:07:36 Phil: If I were to float: left something I positioned into slot A, and positioned something else into slot A, would it flow around the float? 19:07:41 Bert: That was the intention, yes 19:08:04 something about overlapping 19:08:11 Tab: You could create multiple slots in the same place 19:08:39 Alex: Not sure you want to mix unrelated content from various pieces of the dom into a single flow 19:09:10 Bert: run-in has a similar problem, taking an element out of here and putting it there where it has to be reflowed 19:09:22 Steve: You're just creating a shadow element that's the combination of all the things you're flowing into the slot 19:09:35 Steve: and then you flow that 19:09:39 Alex: Yes, it's possible, but it becomes more complicated 19:09:48 Alex: If you really need it we could do it 19:09:56 Steve: The example from the spec is footnotes 19:10:08 Phil: Ok, let's note that and move on. 19:10:24 Phil: You declare a grid using the display property -- could be inline or block 19:10:34 Phil: We have a definition of grid items 19:10:48 Phil: You can put inline-blocks, block-level elements, various other items 19:10:57 Phil: These are wrapped in an anonymous block 19:11:31 Tab: We have more precise terminology for this stuff 19:11:39 (probably should look at 9.2 etc.) 19:12:04 Phil: You can name lines, or not name lines. They have an implicit name which is a number 19:12:34 Steve: Do you use direction and writing mode to determine these? 19:12:36 Phil: Yes 19:12:38 stearns has joined #css 19:13:05 Phil: I can put names by putting strings before the grid measurements. 19:13:17 Phil: I can put multiple names before a measurement, that gives it aliases 19:13:29 Phil: depending on your naming convention, this might be convenient 19:13:36 Phil: You specify a start and end line 19:13:55 Phil: There are also start and end lines predefined, which are keywords rather than strings. 19:14:54 glazou: I don't like that. A lot of authors are going to use the terms start and end 19:15:17 Phil: Not a syntactic conflict. There might be mental conflict. I've heard that several times... 19:15:43 fantasai: Can you count the numbers from the end rather than from the beginning. 19:15:55 Steve: e.g., if you allow negatives to count from end, 1 to -1 would be start to end 19:16:29 Phil: We also introduced syntax we borrowed from grid spec for repeating rows or columns 19:16:33 patterns 19:16:45 Phil: You might want, e.g. a content space and a gutter, content space, gutter. 19:17:12 Phil: We have a concept of repeating patterns for that 19:17:23 Phil: You can name the pattern, that applies to the first line in the pattern 19:17:31 Phil: This is useful for noting the start of the repeating run. 19:17:42 Phil: grid-columns: 10px ("content" 250px 10px)[4]; 19:18:04 Steve: If i have this repeating pattern, and I shrink the window size, is there a way to drop columns? 19:18:31 Phil: Not in this spec. Although we have a concept of automatic columns and rows. 19:18:49 Alex: With grid positioning, repeat meant repeat this combination until you run out of space. 19:18:54 Phil: That's something you could add. 19:19:11 Steve: There's an interesting interaction between fractional space and that concept 19:19:21 Alex: Yeah, you can't combine them. 19:19:33 Alex: I think we resolved them to zero or something. 19:19:44 Tab: You could have repeating pattern, and fractional space on either side. 19:19:49 Tab: I think that's the only case it would make sense. 19:20:05 Alex: You could repeat fractions, but you'd wnat to resolve those first before repeating them. 19:20:33 Steve: You want an integral number of columns, use flex space algo to adjust columns or gaps as specified 19:21:26 repeat("content" 250px 10px, 4) 19:21:39 fantasai: Syntax comment -- we're trying to avoid using additional punctuation for something specific, in case we want to do something generic with it later. So I would suggest to use a functional notation. 19:21:50 Phil: We have some different sizing functions for tracks 19:21:57 Phil: Lenghts, percentages resolved against grid element size 19:22:17 Phil: Fractional values, which are resolved against the remaining space proportional to the number (relative to total of fractional values) 19:22:23 Phil: max-content, min-content keywords 19:22:29 Phil: fit-content 19:22:39 Phil: minmax defines a size range 19:22:48 Phil: auto keyword is equivalent to fit-content 19:23:14 Phil: Any questions on these? 19:23:27 Simon: Did you consider a comma-separated syntax? 19:23:49 Phil: We played with various syntaxes, but tried to avoid adding unnecessary characters 19:24:37 dbaron: If you have commas, you have lines and you have things for the spaces in between them. You have to then figure out where the commas would go. 19:24:53 Steve: good point 19:25:19 fantasai: You could use line breaks, since it's space-separated, which let's you break wherever you think make sense. 19:25:27 simon was concerned about readability with multiple names 19:25:57 Steve asks about flex vs fractional notation 19:26:20 Alex: Aiming to get flex and grid to have same sizing capabilities 19:26:50 Steve: My impression was that it's easier to use flex. 19:27:06 Steve: To get an equivalent mapping, it takes several nested minmax functions 19:27:29 Steve: A 5-tuple as a set of constraints is simple 19:27:34 Tab: Let's talk about that 19:27:36 [later] 19:28:10 Phil: Just a note on how values are computed. 19:28:32 Phil: You might have the same name appear multiple times in the grid value ... 19:29:19 Phil: auto grid column and row generation in case you refer to a gridline that doesn't exist 19:29:53 Phil talks about used value serialization 19:30:05 CSSOM results 19:30:52 glazou: Computed Value is extremely painful to parse 19:30:58 Simon: What's the alternative? 19:31:28 glazou: parsing the repeat notation is problematic 19:31:40 Simon: Thinking about gradients, how could that have been better? 19:31:49 glazou: For gradients need a better CSSOM 19:32:04 glazou: Think about users of getComputedStyle, expand everything 19:33:12 Phil: We wanted to be able to re-assign the value back into the OM and get the same result 19:33:31 Phil explains a complicated example 19:33:49 dbaron: I think it's important that it be round-trippable 19:34:15 dbaron: I think expanding it beyond what it was is causing it to be non-round-trippable. 19:34:47 dbaron: If you read in the grid , and there's an element that auto-generates lines, and you write back, and then you read in and remove the element, you wind up wit lots of extra grid lines that weren't there before 19:35:23 Phil: The grid-column and grid-row properites are used for positioning children of the grid 19:35:38 Phil shows the syntax propdfe tables 19:35:50 Phil: If you don't specify ? you get an implicit end column 19:35:55 s/column/line/ 19:36:09 Phil: We said that items are placed in a cell. 19:36:15 s/propdfe/propdef/ 19:36:22 Phil: That doesn't necessarily mean the element stretches to fill the cell 19:36:31 rrsagent, pointer? 19:36:31 See http://www.w3.org/2011/03/08-css-irc#T19-36-31 19:36:33 Phil: The cell is just a containing block 19:36:42 Phil: There's also the concept of explicitly defining the grid cells, which we covered before 19:36:58 Phil: with that name you can place more than one item into a cell 19:37:27 Steve: What do you mean by placing more than one item into a cell? 19:37:41 Phil: The default behavior is for these items to stack 19:38:04 one after the flow 19:38:45 Phil: whereas positioning them makes them overlap 19:38:50 Steve: That seems a little subtle 19:39:07 Phil: There's a property to control this, grid-cell-stacking 19:39:21 Phil: You can have things stack in rows or columns directions, or layer them 19:40:13 Phil: Perhaps the initial value here should be layer for ocnsistency 19:40:16 Steve: That would be better 19:40:21 Simon: ... 19:40:44 Phil: We intend that they are block-level or inline-block elements. 19:40:52 Phil: if they are valid grid items 19:41:10 Phil: There is also special sizing behavior, where the alignment properties for when you put an element into a grid-cell include stretch, start, end and center 19:41:17 Phil: There's a row alignment and a column alignment 19:41:57 Phil: If you take a block-level element and assign it a grid-column-align property other than stretch, then it will align to one of the edges of its grid-cell and size itself shrink-to-fit 19:42:11 Phil: relationship between that and stacking items in a grid cell 19:42:15 Phil: default is to stretch 19:42:25 Phil: so it stretches to occupy the whole cell 19:42:36 Phil: But if you're stacking, the elements will size shrink-to-fit so you can put one on top of the other 19:42:53 rrsagent, this meeting spans midnight 19:43:20 Phil explains something more about sizing, several people look confused 19:43:43 stearns has joined #css 19:44:12 Phil talks too fast 19:44:32 Steve: Sounds sort of like each of these cells is a flexbox in what you're doing, with the flex direction being either rows or columns 19:44:48 Phil: No flex, but yes similar 19:45:27 Steve: Each item that's stacked is being handled as if it were a flex item whose size is based on its content. I.e. it beocmes a BFC, there's no margin collapsing, etc. 19:45:47 Phil scans through sections of the draft defining the various properites 19:46:41 fantasai: What if grid-row specifies and a start and an end line, and grid-row-span also specifies a span? Could have a cascading problem too. 19:46:51 Phil: We should make it clear that an ending line has priority over a span. 19:46:53 Phil: We left in grid-row-span, grid-column-span, because we liked that ability more 19:47:13 Phil: There's a concept of implicit columns or rows 19:47:23 Phil: You create auto tracks as needed 19:47:39 Phil: There's a property to control what size track gets created, so that they're not always auto-sized 19:48:04 Phil: Lastly, concept of automatically placing items in the gird. 19:48:29 Phil: There's a concept of grid-flow, which creates more rows (or columns) as needed. 19:48:40 Phil: Would take awhile to explain, take a look at the draft 19:48:52 Steve: this is for indefinite numer of coluns? 19:49:19 Phil: Yeah. I have a form with lots of fields, as an author just want to define a grid for your fields 19:49:31 Phil: I create three columns, and then tell the forms to find an auto row 19:50:22 Phil: Here are the grid alignment properites, discusses writing mode interactions, etc. 19:51:28 Phil: Drawing order of grid items is not changed; got some feedback on using z-index, haven't incorporated yet 19:51:46 Phil: Concern is wanting to drop things behind other things, but not behind the grid element background 19:51:55 Phil talks about stacking contexts 19:53:12 Phil: Need an easy send-to-back functionality 19:53:26 dbaron: A full stacking context would do that 19:53:50 Phil: Not sure we really want to prevent z-ordering behind the grid element just because we want easy send-to-back 19:54:08 dbaron: You don't have to do that by default, but the author could specify it themselves 19:54:19 dbaron: That makes the send-to-back scenario work 19:56:02 Phil: Stacking contexts are complicated, I'm concerned about making authors understand them and z-index in order to make this work. 19:56:38 Alex explains something about making all form controls relpos just to get z-index working 19:57:10 fantasai: What is the relationship of this to existing grid module? 19:57:23 Alex: Positioning is really interesting in concept of page layouts, and we have some ideas on how to integrate them 19:58:02 Alex: I have some ideas on how to integrat them 19:58:19 fantasai: It seems this module folds in a lot of that functionality, so you could publish this as an update to that module. 19:59:29 Alex: Grid positioning deals with other content, no necessarily your immediate children 19:59:55 Alex: One thing that needs to be defined is element sizing, and how do you define a positioning container ... where grid is applicable 20:00:46 Alex: Once we figures out where grid position is applicable, who is the grid positioning container, and how is the grid defined on that, we can easily merge these specs together 20:01:03 Alex: So that everything here contributes to grid definition. 20:01:18 Markus: We still need a lot of the concepts from that spec to integrate. 20:01:41 Alex: I think the main ue case for grid positioning is page floats 20:02:00 Alex: I don't think page floats is quite as ready 20:03:59 fantasai: Ok, I understand why they are separate and I agree that makes sense. 20:04:04
20:31:32 Zakim has left #css 20:31:53 Kazutaka has joined #CSS 20:34:38 stearns has joined #css 20:41:42 stearns has left #css 20:41:51 stearns has joined #css 21:02:37 Arron has joined #css 21:02:59 mmielke has joined #css 21:03:50 Zakim has joined #css 21:05:12 smfr has joined #css 21:07:02 TabAtkins_ has joined #css 21:07:21
21:07:54 Markus: Wanted to follow up on discussion from before-lunch meeting 21:08:09 Markus: Would like to advance grid layout spec from editor's draft to WD 21:08:49 jdaggett: For FPWD, there are special requirements 21:08:49 glazou has joined #css 21:09:10 test 21:09:45 fantasai: From what Alex was saying, I think it makes sense for the modules to be separate 21:09:49 [howcome asked if we can merge them] 21:09:59 fantasai: And publish this as grid-layout 21:10:01 Jay has joined #CSS 21:10:15 jdaggett: What are the requirements? 21:10:45 glazou: Has to be in the charter 21:11:22 fantasai: It is, since it's closely related to existing css3-grid 21:11:32 fantasai: need permission from plh to publish FPWD, but nothing else 21:12:02 RESOLVED: Publish as css-grid, i.e. CSS Grid Layout [Level 1] 21:12:18 ACTION Bert make publication 21:12:18 Created ACTION-312 - Make publication [on Bert Bos - due 2011-03-15]. 21:12:48 s/css-grid/css-grid-layout/ 21:13:25 karl has joined #CSS 21:13:45 note: level 1 is not part of title, just clarifying that no other level is 21:14:04 plinss: Skipping line grid, since it's marked as "if time allowed" 21:14:20 plinss: Flexbox? 21:14:23 Tab: ??? 21:14:30 Alex: Wouldn't you like to present the changes in your latest draft? 21:14:32 Tab: I could? 21:14:44 shonda has joined #css 21:14:54 Tab goes up to present 21:14:58 s/Skipping line/Deferring line/ 21:15:39 Moved "Line Grid" to end of agenda for today on wiki 21:15:43 Tab gives overview of flexbox 21:15:45 http://dev.w3.org/csswg/css3-flexbox/ 21:16:04 Tab: Current editor's draft of flexbox is much closer to my draft, and to suggestions we've made so far 21:16:10 Tab loads page with lots of red 21:16:34 Tab: Using term flexbox consistently, instead of box which is too generic 21:16:44 Tab: Flex-direction says which directions the boxes flow in 21:17:11 Tab: Have physical and logical directions 21:17:29 Alex: If we had a multiline flexbox, how would we extend flex direction for it? 21:17:39 ISSUE ^ 21:17:47 Alex: One approach would be to use existing writing mode 21:17:53 Alex: There is no logical equivalent of those 21:18:04 Alex: Maybe do come up with eight logical abbreviation directions 21:18:18 bradk_ has joined #css 21:19:40 fantasai: How about combining keywords with spaces, e.g. tb lr 21:19:52 Tab: flex-order lets you reorder items 21:20:28 bradk_ has joined #css 21:20:28 Tab: Flexible lengths is where it really changes. 21:20:42 Tab: Old draft used a flex property that took an integer, and then keywords for alignment 21:20:59 Tab: I'm going with a different approach here, 21:21:16 Tab: Got feedback from daniel and web authors that "width" being an input in to the flex algo and not really the width was confusing 21:21:38 Tab: Using now a flex() function, which takes 3 args, first one is positive flex, second is negative flex -- 21:22:03 Tab: Established at F2F that negative and positive flex should be distinguished, otherwise you get unintuitive results, ie. largest thing becoming smallest 21:22:15 Tab: Third arg is the starting width. 21:23:00 Tab: auto gives previous behavior; it's always additive flex, but by default this arg is zero so you get absolute flex if you don't specify 21:23:14 Phil: Is there plan to have something not flex-prefixed for any type of layout not based on source order? 21:23:21 sylvaing has joined #css 21:23:27 (regarding flex-order) 21:23:51 Phil asks about having the reordering be a more generic concept, since it's useful in many layout models not just for flexboxy 21:23:54 s/y// 21:24:11 Tab: Ok, could have that be a generic mechanism for rewriting source order 21:24:25 Steve: ... 21:24:50 Phil: Template layout had an area that used source order for flowing items, might want to reorder in that as well 21:25:12 dbaron: Do people have positive experiences using an integer-ordering property like this? 21:25:44 dbaron: or does this get unweildy with more content? 21:25:53 Tantek: numbering BASIC worked so well! 21:26:11 Steve: Might want to reorder columns 21:26:19 Steve: in that case maybe using names 21:26:37 Tab: Elika brought up case of tabbed layouts, where active tab is always in front 21:26:49 Tab: I'm certain like many of our advanced tools it can be abused 21:26:57 Tab: Like we shouldn't be sorting lists with this 21:27:05 Tab: But I'm not sure how else to get the functionality we need here 21:27:38 dbaron: Wrt usefulness of order, Gecko has implemented box-ordinal-group for around a decade now. 21:27:51 dbaron: But it's used so rarely that we're still getting very fundamental bugs filex on it 21:28:11 Tab returns to flex() 21:28:25 Tab: The old flex property and box-align properties are replaced with flex() notation 21:28:47 Tab: Then we have the flex-pack property, which determines the distribution of content within the flex direction 21:29:20 Tab: It works similar to text-align 21:30:01 Tab: justify evenly spaces out the flexboxes, aligning them flush 21:30:32 fantasai: I would suggest to look at ruby-align property, esp distribute (which seems like a better name here) and distribute-space 21:30:39 Tab: flex-align property.. 21:30:59 Tab: Normally use flex to do alignment, but couldn't figure out how to do baseline alignment 21:31:18 Tab: Not totally clear on the use cases, so still haven't fully specc'ed it out. 21:31:35 Tab: auto just means normal flex distribution, baseline means currently-undefined magic 21:31:48 Tab: That's pretty much it, rest is algorithms 21:32:41 Tab: We've established that for flex, we want positive flexibility, negative flexibility, and a starting width. These are all important pieces of information we need to flex correctly. 21:33:04 Tab: The original approach of having two different properties that have to be thought of together to get a single effect was confusing 21:33:13 Tab: And with negative flex we needed yet another one 21:33:30 [Markus asked why there's flex() instead of 'flex'] 21:34:08 Alex: My concern is that it makes absolute flex easier but relative flex harder 21:34:50 Alex: The main working mode of the whole spec becomes absolute flex, which is not the previous system 21:35:05 Alex: I expected default starting width to be auto 21:35:34 Alex: Have padding initial be zero, width initial be auto 21:36:43 Markus: ... 21:37:10 Tab: Talking to authors playing with old spec, they're confused. 21:37:25 Tab: Having flex: 1; on multiple elements result in different sizes confuses them 21:38:05 Alex: If you're working on top-level page layout, absolute flex is more useful 21:38:21 Alex: If you're laying out form controls, then additive flex is more useful. 21:38:34 s/form controls/form controls or menus/ 21:38:36 Tab: I have to make one shorter syntax than the other 21:38:48 Alex: Let's look at other options 21:39:31 Tab talks about terminology for width and height algos 21:39:45 Markus: Is your motivation that this would replace existing flexbox spec? 21:39:48 Tab: Yes, replace 21:40:00 Markus: Despite existing implementations? 21:40:09 Tab: Yes. I think this is sufficiently better that it should replace. 21:40:21 Tab: Working with chrome devs, they are enthusiastic about replacing it 21:40:41 Alex: Is Mozilla going to move to the new syntax? 21:40:50 dbaron: We'd definitely like to have a standard version of flexbox. 21:41:06 dbaron: It's hard to tell how quickly it would happen/ 21:41:19 Alex: would it make a difference if it stayed closer to the old syntax? 21:41:27 dbaron: I think the syntax is less of a big deal than the concepts 21:41:42 dbaron: A lot of the stuff we use flexbox for now is stuff we want additive flex for now. 21:41:56 dbaron: potentially harder to convert existing content 21:42:03 Tab: I don't buy the conversion argument 21:42:08 dbaron: But it seems like a lot of typing 21:42:32 people might not know what flex(1, 0, auto) means 21:42:33 dbaron: And I don't think people will know what flex(1,0,auto) means 21:42:39 (which they'll be using a lot) 21:43:11 Markus: Shouldn't we standardize the current spec now? 21:43:19 Markus: And make this the next level? 21:43:37 Tab: You can't really do that. They're not compatible, not without some really hacky stuff 21:43:56 Tab: Also my experience talking with authors is that the current spec is really confusing 21:44:10 Markus: Yeah, it's not that great, but we have implementations 21:44:43 Tab: I'm not in favor of standardizing something that's bad. 21:45:04 dbaron: I think you're getting different feedback because the web authors you're talking with are trying flexbox for something it wasn't designed for 21:45:11 standardization is always bad because it is always a compromise 21:46:19 i/Arno: I'd like tot/-> http://lists.w3.org/Archives/Public/www-archive/2011Mar/att-0011/CSS_Regions.pdf CSS Regions draft 21:46:42 fantasai: So, my position is [minute here later] 21:47:05 Tab: If it's a question of which (additive vs absolute) is easier, I'm not concerned about that question 21:47:21 Tab: What's important to me is breaking with the previous syntax. 21:47:29 Markus: We have implementations coming, and it's used. 21:47:32 Tab: But not on the Web 21:47:39 Tab: And our implementation at least is very buggy 21:47:50 Tab: It's a minority prefixed thing. 21:48:07 glazou: Current implementations are too weak and too buggy for use 21:48:18 Tantek: That's the point of prefixes -- they allow us to experiment. 21:49:37 fantasai rants, but doens't have time to type it 21:50:11 dbaron: I don't think negative flex is the hardes thing here, it's adding flex to margins and padding 21:50:22 fantasai: But thats needed if you want to apply this to HTML, because in XUL you have to use elements 21:50:27 dbaron: ...and as a value to existing properties 21:50:41 Steve: ... 21:50:51 Steve: This in my mind has the level of flexibility that you need 21:51:01 Steve: It's also a lot easier to explain to people than the other one 21:52:06 Steve: It would work perfectly well within the grid layout model 21:52:21 Steve: I think Tab's choice of using the zero-width thing is more appropriate there 21:53:00 Tab: For the most common case, of starting flex from the auto width and using single flex, you can just use 'auto' 21:53:06 Tab: That's equal to flex(1,0,auto) 21:53:41 Tab: We can still talk about how to make them easy, but there are ways to make both common cases easy 21:53:54 dbaron: Shouldn't the width value come first? 21:54:29 Tab: I had it that way at first; seemed reasonable; Alex convinced me to change. 21:55:43 Tab: I had that first, and it makes it easier to do relative flex, but it doesn't work so well for absolute flex 21:55:51 Tab: And Alex suggested swapping the order 21:56:10 fantasai asks about making flex() detec whether it's aboslute or relative based on whether it's a length or an integer 21:56:34 Steve: ... 21:57:01 Steve: The flex unit is confusing if grow and shrink are given in one set of units, and differnt in another 21:57:15 Tab^: I had flex units be additive and flex() be absolute before 21:57:28 ... 21:57:46 Tab: The idea of what's the best way to present this concept to authors is omething we should talk about 21:58:00 Steve: Btw I'm not disputng the 5-tuples 21:58:09 Steve: Just discussing synta 21:58:38 Tab: I think this is the best option, though I'm open to other options. 21:58:49 Tab: Main question is whether we go forward with this or revert to the old draft. 21:59:06 Alex: We want draft to become stable and move forward 21:59:14 Alex: I don't see a way to get there without having a new draft 21:59:23 plinss asked for objections to moving forward with this draft 21:59:50 RESOLVED: Publish updated draft of css3-flexbox 22:00:08 Topic: MultiCol 22:00:47 howcome: Multicol is in CR. We have a couple of issues, but close to getting a new version 22:00:53 howcome: Would like to publish another CR 22:01:03 howcome: Big issue was pseudo-algorithm 22:01:44 howcome: In previous versions the pseudo-algorithm tried to reduce the number of columns 22:02:05 howcome: Seems to be consensus on not doing that, and relying on authors setting column-width to give the columns a minimum width 22:02:34 howcome: here's what I suggest to edit the pseudo-algorithm 22:03:01 fantasai: Can we get comments in the pseudo-algorithm? 22:03:04 howcome: maybe 22:03:37 howcome: I think my proposal is correct, put a max fuction to make sure width doesn't go negative 22:04:01 howcome: The prose says that if both 'column-width' and 'column-count' have non-auto values, the integer value describes the maximum number of columns 22:04:09 howcome: fantasai noted this in the minutes 22:04:20 howcome: But this prose is not included in the pseudo-algorithm 22:04:36 Sylvain: Fix the pseudo-algorithm 22:07:03 Discussion of use cases for column-count 22:08:14 brennannovak has joined #css 22:08:15 howcome: btw, my proposal for fixing this should use min() instead of max() ... 22:08:41 brennannovak has left #css 22:11:06 fantasai makes an argument that the combination of column-width and column-count is the most useful way of specifying column-count, and this behavior is not provided by any of the alternative proposals 22:11:19 wheres the behavior of the alternative proposals can be gotten in other ways 22:11:32 Simon: Should we rename it to column-min-width? 22:11:52 howcome: we'd have to go back to last call 22:12:29 no strong opinions in favor of renaming 22:12:35 howcome: Can we update the CR? 22:13:50 plinss wants to be more verbose and have it column-min-width 22:13:59 fantasai disagrees 22:14:09 Brad: If there's only one thing to set the widht, it should just be width 22:14:21 RESOLVED: Publish updated WD of css3-multicol 22:14:29 RESOLVED: Publish updated CR of css3-multicol 22:14:37 dbaron: test suite? 22:14:53 dsinger has joined #css 22:15:15 howcome: I'm working on the test suite 22:15:49 dbaron: we have 22 reftests for columns 22:16:18 fantasai: bunch more in pagination 22:16:35 dbaron: we'd need to go back and check that the tests match the current spec 22:16:44 johnjan: I have some ideas 22:16:51 howcome: how do we go forward with the tests 22:17:00 johnjan: We should take what we learned about CSS2.1 and apply to CSS3 22:17:13 johnjan: I think first we should map every test to the part of the spec's testing 22:18:01 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 22:18:29 dbaron, fantasai: We have links to section headings laready 22:18:43 fantasai: css3 specs have more fine-grained subsections than CSS2.1 22:19:20 johnjan, fantasai: ideally would do per-paragraph anchors 22:19:48 fantasai: but hard to have stable anchors 22:20:24 i/I'd like tot talk/-> http://lists.w3.org/Archives/Public/www-archive/2011Mar/att-0011/CSS_Regions.pdf CSS Regions draft 22:20:27 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 22:20:46 http://test.csswg.org/suites/css2.1/20110111/xhtml1/toc.xht 22:20:48 johnjan talks about testing 22:20:54 keeping track of which sections are tested, not tested, 22:21:01 how many tests are for each section 22:21:35 johnjan: we're not interested in implementation testing, but in implementability testing 22:21:46 dbaron: We need a test suite to enter PR, but that shouldn't be the only purpose of the test suite. 22:21:55 dbaron: I think we should be developing the test suite for interop 22:22:34 dbaron: We want the test suite to solve real problems for authors, not just get us to PR 22:22:44 dbaron: Authors have problems when impls don't do the same thing 22:23:36 dbaron: And we want to test things that will have bugs that bother them 22:23:48 It's not about proving interop... it's about improving interop. 22:23:49 johnjan: proving compliance and interop are two different 22:23:50 i|I'd like tot talk|-> http://lists.w3.org/Archives/Public/www-archive/2011Mar/att-0011/CSS_Regions.pdf CSS Regions draft 22:23:54 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 22:24:33 dbaron: It's not about proving interop, it's about IMproving it 22:24:39 ... 22:25:01 johnjan: There's no motivation for making test suites other than going to CR 22:25:19 what if test ID used a section URL plus the text of the paragraph? then mapping can use simple search to map. when paragraph moves it is still mapped to. when the pargarph changes the tests have to be updated anyway... 22:25:19 sylvaing: You could say that you need an implementation report to drop your prefixes 22:25:48 sylvaing: Today, we allow dropping prefixes as soon as we go to CR. 22:26:11 sylvaing: If we require tests, that gets us tests and it makes sure that impls dropping prefixes implemented it correctly 22:26:28 johnjan: I think testing has to drive the process more 22:27:52 fantasai: public-css-testsuite and the svn repo are available to all css modules, not just 2.1 22:29:10 fantasai and arronei review the review process 22:29:42 http://wiki.csswg.org/test 22:29:52 Tab: There should be an excuse to why it's not a reftest 22:30:42 dbaron: Did we adopt the scripted reftest conventions? 22:30:54 fantasai: Not yet, we'd have to do so 22:31:26 dbaron explains reftest-wait 22:32:39 howcome: do we need scripted tests? 22:32:47 dbaron: Yes, changing pagination points 22:32:54 johnjan: resizing the window 22:33:11 howcome: Safari? 22:33:18 Simon: We have 50-60 tests in our test suite 22:33:33 Simon: But they're not really suitable for test suite tests in their current incarnation 22:34:19 howcome: What about multi-col in vertical text? 22:34:22 Alex: It should just work :) 22:35:51 johnjan: what about prefixes? 22:36:02 Arron: No prefixes in the test suites 22:36:17 johnjan: So we can't test until we drop prefixes 22:36:31 dbaron: Could add prefixes with regexp 22:37:56 homata__ has joined #CSS 22:38:22 fantasai: Current build system has concept of output formats, would be easy to build regexp into that 22:38:27 mollydotcom has joined #css 22:38:36 Arron: Another issue is tracking issues on the testcases 22:38:47 Arron: Using the mailing list is really really unweildy 22:39:09 Arron: Can we use bugzilla? 22:40:36 johnjan: The mailing list is really going to be hard to manage 22:40:52 dbaron: Bugzilla is too heavyweight 22:40:58 plinss: we have a design for a system, just need to build it 22:41:11 johnjan: We need something now 22:41:28 Arron: May not be perfect solution, but Bugzilla gives us something for now 22:42:31 fantasai: So I think we should adopt Bugzilla, one bug report per test unless you have a really good reason not to. 22:43:29 howcome: So we put tests in contributors directory, and if I review and approve them I move them to the approved/ directory 22:43:33 fantasai, arron: right 22:43:49 RESOLVED: Use Bugzilla for test suite bugs, one bug report per test unless there's a good reason not to 22:45:53
22:48:59 hey folks - I'm much on the mend now - wondering if I should come in? Or rest and wait 'til tomorrow? 22:50:13 (ps it's not contagious ;)) 22:55:53 That's very sweet, Sylvain. I think I will stay and rest here as there's not much time left of the day. Better to be feeling more myself tomorrow 23:03:57 Topic: Tokyo Workshop 23:04:11 http://wiki.csswg.org/planning/tokyo-workshop-2011 23:04:14 howcome has joined #css 23:04:16 howcome: http://wiki.csswg.org/spec/css-multicol 23:05:19 Koji: There is a group in Japan supported by Japanese government trying to host forum or workshop 23:05:27 Koji: I'm the liaison to the CSSWG 23:06:06 My name is Jay [?] 23:06:23 Jay: I am going to make a presentation for the upcoming Tokyo workshop 23:06:28 Jay Kishigami 23:07:12 http://wiki.csswg.org/planning/tokyo-workshop-2011 23:07:26 Jay: This is a good opportunity to discuss with Japanese publishers and other users of vertical writing. 23:07:41 Jay: But it's not only in Japan, but also in other countries. 23:07:51 Jay: Old Korean was written in vertically 23:07:57 Jay: And also Chinese write in vertical 23:08:08 Jay: Chinese, Japanese, and Mongolian all currently write in vertical 23:08:12 Newspapers in Korea were in vertical up until 1996 or so 23:08:30 Jay: Maybe this community discuss the real requirements 23:08:54 Jay: Publishers and software vendors are very interested in ths workshop 23:09:12 Jay: Maybe some presentation from Asian layout implementers and device vendors 23:09:16 You can find Korean newspaper archives by date at http://dna.naver.com 23:09:17 Jay: authors 23:09:30 Jay: I just wanted to confirm dates for workshop 23:09:37 Jay: Before or after 23:09:51 Jay: I heard that fantasai cannot attend before, but others are better before 23:10:16 Jay: before is also good if items come up for WG discussion, can be discussed at F2F after 23:10:23 Jay: Is there any objections or comments on the date? 23:10:26 bradk has joined #css 23:10:37 glazou: How many days do you plan to have the workshop? 23:10:45 Koji: I don't think we have finalized this yet 23:10:54 glazou: I think one day is probably enough 23:11:07 glazou: Since we are meeting W-F for CSSWG F2F 23:11:48 glazou: So Tuesday is best especially for people travelling from far away 23:12:52 Bert: How many people should come to the workshop? 23:13:11 Koji: It depends if you want a small group, then we can have such a meeting, or if you want to have a bigger meeting we can do that. 23:13:14 glazou: We can have both. 23:13:19 glazou: Most of the WG will be present. 23:13:31 hober has joined #css 23:13:38 glazou: We can have panels with questions where WG interact with audience, split into tables for lunch 23:13:57 glazou: The only problem in smaller groups is your last line, the language 23:14:12 Jay: Atm we have two solutions for the language. 23:14:19 Jay: one is to have basic language be English 23:14:36 Jay: But for some people they're not comfortable to speak English 23:14:45 Jay: So we can have simultaneous language 23:14:58 glazou: Japanese is probably best for main language, but we need English :) 23:15:17 Jay: So proposal is May 31st Tuesday from 9 or 10am through the evening, with lunch session 23:15:25 Jay: We can have tables with discussions at the tables 23:15:37 glazou: That's doable if we have one person per table able to translate between English and japanese 23:15:41 glazou: That's the only trouble we have 23:16:05 Peter: One other thought about the dates is that we could push our meeting back by a day or shorten it by a day 23:16:14 jdaggett: I think we definitely shouldn't shorten our meeting 23:17:12 plinss: We could also push back our meeting by a day, T-S 23:18:35 fantasai and Steve can't make Tuesday 23:18:47 ?: Tab, can you host on Saturday? 23:19:02 Tab: difficult, since Google employees won't be there 23:19:14 jdaggett: We could host on Saturday 23:19:29 (So how big will the ftf be, again 25, or less?) 23:21:27 TabAtkins_: 23:21:33 ScribeNick: TabAtkins_ 23:21:55 jdaggett: I'm concerned that if it's only publishing/gov people, we (CSS) aren't really capturing the main audience for this, which is people designing for the web. 23:22:16 jdaggett: It's good to consider the use-cases the publishers have, but that tends to be a relaitvely limited set of uses compared to everyone designing webpages. 23:22:39 Jay: The participants here may be from the publishing area, but will include the web designers. 23:22:40 i'd like to jump in on that too 23:22:43 if I may? 23:23:02 Jay: Maybe the signage designers would be able to offer useful feedback as well 23:23:10 John's concerns are very real, and of course this is an ongoing issue 23:23:31 jdaggett: We're designing CSS here, and the focus is on designing CSS, not necessarily on how Japanese test works. 23:23:39 as the person who acts as developer liaisons, we have to engage designers more 23:24:10 but Japanese text is part of that too - designers designing Japanese sites need the technology 23:24:19 Jay: The goal of this workshop is understanding how to handle vertical text. 23:24:28 [reading Molly's comments] 23:24:46 I'm just repeating my old mantra: Engage designers somehow 23:24:57 jdaggett: It would be useful to have a workshop on CSS and how Japanese fits into that context, rather than how publishing works in Japan. 23:25:00 It's very difficult, not our fault, but it's necessary 23:25:44 Koji: I think we tried to make the participant list take into account input from the WG, including you. 23:25:46 +1 That's the point, is it not? John. At least as I see it 23:26:05 jdaggett: I think it seems that this is trying to be everything to everyone, and it needs some clear themes. What are the problems we're trying to discuss. 23:26:18 jdaggett: My concern is that people are just going to get up and talk about things that they think are important. 23:26:41 Markus: So you want to frame it as "How can we help", action items that the WG can take away to work on. 23:26:57 jdaggett: Right; we need to think about it in terms of CSS and the web, not just about the difficulties of publishing. 23:27:42 plinss_: I think CSS is becoming more and more important in publishing. 23:27:55 jdaggett: Right, but we need to ensure that it's both about the web and publishing. 23:28:09 Markus: If you explain what is the delta between what you see on the Web and what you would want to see 23:28:11 Markus: I think it's easiest to phrase things as a delta between what currently exists and what is lacking that is needed. 23:28:28 I agree - but any focus on publishing and not the Web pisses off a lot of developers and designers. Who is using CSS more today? 23:28:36 Jay: We want to intentionally produce just such a productive and tangible result from the discussions. 23:28:42 Markus: Every time you have a speaker, elicit a summary so we can walk away with an understanding of what we need to work on. 23:29:08 Jay: Though, perhaps the older publishing people won't fully grasp what is "CSS". 23:29:16 Jay: So some interpretation may be required. 23:29:43 myakura has joined #css 23:29:45 it sounds unfocused to me 23:29:47 Steve: Are you looking at this as a meeting as a way for CSSWG to present what we're doing and get comments and questions back, 23:29:49 what is the end goal? 23:30:00 in one sentence 23:30:02 Steve: Or are we sitting through presentations where japanese people explain what they need? 23:30:31 Steve: I don't have a particular preference, but from the CSS viewpoint it seems to make more sene for us to present what we are doing, since that's what we are expert in 23:30:42 Steve: But it would also be relevant to hear what other people think we /should/ be doing 23:31:01 "what they need" is already described really well by the amazing http://www.w3.org/TR/jlreq/ document 23:31:30 Koji: Is there anyone who can give an overview of what's going on in CSSWG? 23:31:31 How about focus sessions on each then? "Hear from the CSS WG" and "Hear from the attendees" which could be very compelling if well described 23:31:42 fantasai: you? :) 23:31:56 tab reads out comments from IRC 23:33:50 fantasai: Could hve two days, one in Japanese, one with the WG in English 23:33:58 Zakim has left #css 23:34:06 hyatt: yes that document is amazing 23:34:21 glazou: that's really what we've been using in webkit to guide our implementation 23:34:27 fantasai: Japanese can use the first day to interact with and learn from each other, and organize what they want to present to us, ask us, request from us 23:34:33 hyatt: how suprising :-) 23:35:57 Koji: Could have first day Japanese learning, second day presenting to WG 23:36:21 Jay: So could have second day be workshop, with English support, first day be preparation for/by/in Japanese 23:36:52 Jay reads out name of government org that will be co-organizing with W3C 23:37:21 glazou: When do you think the organizing committee is going to release a schedule for the day? 23:37:42 Jay: Need to coordinate with Japanese government and W3C 23:37:55 Koji: SVGWG is also interested in participating in this forum 23:38:19 Steve: They have their F2F the next week 23:38:39 Steve: I think Chris favored having the workshop beforehand as well 23:39:09 Steve: He also talked about having a joint SVG-CSS meeting 23:39:51 Koji: Should be able to get back to everyone within 2-3 weeks 23:40:04 Steve: Asap, so people can get airline tickets 23:41:16 RESOLVED: Tokyo workshop tentatively scheduled 31st and 1st, 31st as Japanese-only, 1st also in English with CSSWG; CSSWG F2F moved to Thursday-Saturday June 2-4 23:41:48 Topic: CSS3 Line Grid 23:41:55 plinss: anything to discuss here? 23:42:20 John: I don't think we should be discussing things where we don't have anything written down. I think that should be a prereq for discussing at an F2F 23:42:29 jdaggett: I'm a little confused why we're talking about this as a separate spec 23:42:35 jdaggett: This was in a previous CSS3 Text draft 23:42:49 jdaggett: I think it's peculiar to be creating modules here 23:43:20 philcupp has joined #css 23:43:30 fantasai recaps history of CSS3 Text 23:43:46 jdaggett: Given everything we have on our plate here, I think it's a little premature to work on a spec here 23:43:59 jdaggett: Were there implementers on the CSSWG who wanted to implement this? 23:44:05 Koji: Apple 23:44:26 fantasai: We need 2 implementers to take on a module 23:44:38 arno has joined #css 23:44:45 Koji: CSS3 Text was born 12-13 yrs ago as International Text Layout spec from stuff at Microsoft 23:44:52 szilles has joined #css 23:45:07 Koji: The Japanese portion of that spec was mostly written by me, brought from MS Word features 23:45:19 Koji: Line grid one of the features Word implemented in 97 and tried to bring into IE 23:45:29 Koji: Nobody has been showing much interest since IE 23:45:41 Koji: Not sure what happend after, but it was decided to split up 23:45:55 jdaggett: What needs to happen first is Apple need to say they're interested in this 23:46:04 jdaggett: And then we can assess whether this is something we want to take on 23:46:11 jdaggett: We have a very full charter 23:46:22 jdaggett: Seems like something that should be starting after we finish CSS3 Text and CSS3 Writing Modes 23:46:26 jdaggett: Talking about it now seems premature 23:46:46 Alex: We started that set of specs in IE6 time to reflect what we had in IE and what we wanted to have in IE 23:47:21 Alex: line-grid itself is largely driven by Japanese publishing but it is also line alignment that typography, in particular multicol, that is used in desktop publishing 23:47:27 Alex: We are glad that somebody else is interested 23:47:34 Alex: We had a hard time last 12 years in promoting this 23:47:49 Alex: We should create a spec that a new implementer like us can agree on 23:48:00 Alex: Not sure what we do if Apple goes to implement line grid without a spec 23:48:34 jdaggett: If both Apple and Microsoft are interested, then we should have them write down what they're interested in implementing 23:48:47 jdaggett: Let's have a written proposal that describes what they're interested in 23:49:25 Simon: for the record, we weren't aware of this, so we need to talk with hyatt and find out more 23:49:33 Koji: ... 23:49:37 jdaggett: So we can talk about it then 23:49:46 Alex: What do you propose for start making changes to the spec 23:49:59 jdaggett: first, I think we should have a written proposal of what we want to take on, 23:50:15 jdaggett: second, group reviews this and decides whether this is something we want to take on 23:50:32 jdaggett: It's largely a matterof editor's time, but also discussions at F2F and telecons, so impacts groups time 23:50:40 s/Koji: .../Koji: I prioritice writing mode and text higher, but expect to get to line grid in a few months./ 23:50:48 Koji: It's not a new spec, it already exists in 2003 CR 23:51:05 jdaggett: So point to the spec sections 23:51:22 http://www.w3.org/TR/2003/CR-css3-text-20030514/#document-grid 23:51:34 jdaggett: Do you want all of this? 23:52:34 jdaggett: What is the exact set of features from that spec that you are talking about? 23:52:55 Koji: My approach was to write an editor's draft and ask people for review 23:53:32 jdaggett: Usually people write a rough draft of what they want 23:53:54 Steve: I think there are two points going around here. 23:54:12 Steve: One is, we get regularly beat up from W3CM about having too many irons in the fire and not finishing anything 23:54:26 Steve: We did a priority review at the last charter, and concluded this was not at all a priority 23:54:37 Steve: Since then priorities have changed, especially due to EPUB 23:54:45 Steve: So one issue is what are we giving up to work on this 23:55:00 Steve: Second is, if we are going to work on this, is how to go about doing it. 23:55:15 Steve: Adobe and Microsoft both put proposals on the table to discuss 23:55:30 Arron: You mean a proposal other than the current spec? 23:55:38 Steve: Could just be updated copy of old spec 23:56:27 jdaggett: I also think along with the proposal, an indication of what set of features implementers are interested in implementing from that proposal, is also important. 23:56:37 jdaggett: My concern is that you and Elika are editors of the CSS3 Text spec 23:56:45 jdaggett: And I don't see that as being stable, there's a lot of work remaining there. 23:57:03 jdaggett: My concern is that we shouldn't be talking about priorities until we get through whatever has to happen for that 23:57:49 Koji: So when the time arrives I should copy from 2003 CR and put on my own site? 23:58:07 jdaggett: Just put it on dev.w3.org 23:58:18 fantasai: I think that was all he was asking for. 23:58:33 Bert: Putting it in the charter is a separate matter, but dev.w3.org is available. 23:58:59 Topic: Compositing 23:59:11 plinss: SVGWG has published Last Call of their Compositing spec. 23:59:24 s/has/will/ 23:59:27 s/ed// 23:59:36 plinss: They plan to set a 4-week LC period, until april 7 23:59:45 plinss: They are asking us if that's sufficient time 23:59:47 http://dev.w3.org/SVG/modules/compositing/master/ 00:00:51 plinss: Ok, nobody seems to be asking for more time. 00:01:10 plinss: That's most of what we preplanned out for today. Also have the elephant in the room of CSS2.1 issues 00:01:21 plinss: Daniel and I suggest tackling those 00:05:05 myakura has joined #css 00:19:58 Topic: CSS2.1 00:20:07 plinss: Plan for rest of day is to work on CSS2.1 issues. 00:20:27 plinss: If people want to leave, feel free to leave. We are not working on anything else today. 00:20:28 Kazutaka has joined #CSS 00:20:45 plinss: One quick thing to discuss, over lunch we talked about keeping the editorial issues we don't want to deal with now 00:21:02 plinss: but that we think are valid 00:21:24 plinss: Several options are making a CSS2.1.1 or CSS2.1 00:21:31 plinss: or slip them in between PR and REC 00:22:03 plinss: Advantage is that we can tell people that we accept their issue just not right now and it will show up in a future revision 00:22:15 Arron: My concern with the last one is that we accidentally introduce a substantive change. 00:22:24 plinss: Other thoughts? 00:23:07 this is to ensure that we can shelf 2.1 or does it still remain in limbo 00:23:13 sgalineau has joined #css 00:23:21 johnjan has joined #css 00:23:34 dbaron: So, it's somewhat dangerous from an editing perspective to branch if you're going to make substantial changes to both halves of a branch 00:23:45 ...and then want to merge them 00:24:02 fantasai: I don't think the merge is going to be that difficult, because CSS2.1 has short lines and we aren't making that many changes at this point. 00:25:21 plinss: So what are we going to do? 00:25:47 fantasai: I don't care, as long as I have some place to put the edits so I never have to look at these emails again. 00:25:56 hahaha 00:27:03 http://wiki.csswg.org/spec/css2.1/anton-lc-2010 00:27:09 dbaron: Should consider which branch is going to get served off the server, if you're going to branch 00:27:27 it's been suggested from the design community to add an intermediary css2.1.1 or somesuch. I don't know if that helps or hurts us, but that's the general sentiment 00:28:09 markus has joined #css 00:28:11 plinss: I'm looking for resolution to accept the recommendations on the wiki page where Arron and fantasai analyzed Anton's comments. 00:29:04 arron: Stuff we didn't have a no-change conclusion on has been filed in the wiki 00:29:09 as issues 00:29:38 mollydotcom has left #css 00:31:45 looks like IRC may not be working. 00:32:44 fantasai reviews the wiki doc 00:33:00 ah... it is working. it's just very very quiet there. 00:38:43 johnjan: you're at the airport ? 00:38:55 yeah 00:39:01 san jose ? 00:39:05 yes 00:39:14 have a good trip ! 00:39:25 having a beer while the CSSWG discusses 2.1! 00:39:33 tss tss :-) 00:43:19 CL3 could add a more explicit reference to other section, but there's a link already 00:50:24 http://dbaron.org/css/test/2011/css21-issue-280 is a testcase for issue 280 00:54:06 fantasai: I basically have three levels of suggestion: 1. Change now 2. Change in errata 3. Editorial for some undetermined future revision. (and of course 0. No change) 00:55:11 plinss_: First open issue is 179. 00:55:15 dbaron: Has an action to Bert. 00:55:20 dbaron: So what do we need to do? 00:55:27 plinss_: Do we need to make this change? 00:55:35 fantasai: Yes, it's currently wrong. It's an example, but it's wrong. 00:56:05 RESOLVED: Accept the edit for 179. 00:56:10 plinss_: Issue 225 00:57:39 dbaron: I don't understand "the top of the parent box" in this proposal. 00:58:05 dbaron: In the text he's quoting, the conditions for top and bottom are different, and I think they need to be. 00:58:11 arronei: I think the current text is fine, personally. 00:59:06 dbaron: This proposal looks like a substantive change. 00:59:09 stearns_ has joined #css 01:00:56 dbaron: I don't understand why this is saying "top of the parent box" instead of using the same language for top and bottom in each list item. 01:01:00 dbaron: What's the parent box? 01:01:07 arronei: It should be the top border edge of ??? 01:01:18 dbaron: If it has a previous sibling, the top of the parent isn't what you want. 01:01:51 dbaron: And a lot of this section is dealing with situations where the first child may be outside of the element's own height, because margins are collapsing through that first child. 01:03:20 dbaron: Anton is correct that the current spec is wrong. 01:04:18 dbaron: It was written at a time when we assumed there was no in-flow content that would inhibit margin collapsing ??? [maybe never mind, the text may be right] 01:05:20 dbaron: Never mind, I don't see anything that needs changing here. Certainly don't see what's wrong with the second sentence. 01:05:57 plinss_: So, do we think the spec is fine? 01:06:01 dbaron: Yeah, I think so. 01:06:09 RESOLVED: No change for issue 225. 01:06:38 plinss_: Issue 226 01:06:47 fantasai: I need to write text. 01:07:00 plinss_: Do we agree that this is a necessary change? 01:07:02 fantasai: Don't remember. 01:07:05 http://wiki.csswg.org/spec/css2.1#issue-226 01:07:10 arronei: let's look at it and see. 01:09:27 Jay has joined #CSS 01:10:00 RESOLVED: 226 is editorial, deferred to CSS3. No change to CSS2. 01:10:03 plinss_: 229. 01:10:12 dbaron: This is a case where no impls match the spec, I think. 01:11:17 http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%20magenta%22%3E%0A%20%20%3Cdiv%20style%3D%27float%3A%20left%3B%20border%3A%20solid%20green%3B%20%27%3EA%3C%2Fdiv%3E%20aaaa%0A%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%20blue%3B%20margin%3A%20-2em%22%3E%0A%20%20%3Civ%20style%3D%22float%3A%20left%3B%20border%3A%20solid%20yellow%3B%20%22%3EB%3C%2Fdiv%3E%20bbbbbbb%0A%3C%2Fdiv%3E 01:11:54 http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%20magenta%22%3E%0A%20%20%3Cdiv%20style%3D%27float%3A%20left%3B%20border%3A%20solid%20green%3B%20%27%3EA%3C%2Fdiv%3E%20aaaa%0A%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%20blue%3B%20margin%3A%20-2em%22%3E%0A%20%20%3Civ%20style%3D%22float%3A%20left%3B%20border%3A%20solid%20yellow%3B%20%22%3EB%3C%2Fdiv%3E%20bbbbbbb%0A%3C%2Fdiv%3E 01:13:32 fantasai: The "aaa"s don't move to make room for the "bbbb". 01:13:47 if the tests are right, looks like everyone is interop, but no one is compliant. 01:13:49 dbaron: If there's a float between two blocks, does the placeholder get wrapped? 01:14:29 fantasai: No, placeholders only get created for tables. 01:14:37 dbaron: But I thought we needed it for containing block? 01:14:57 dbaron: The reason the spec is wrong is the wording we used to work around the fact that the float's placeholder isn't in a block. 01:15:33 fantasai: ???? 01:16:09 dbaron: There is some wording about "the float can't be below the bottom of the previous block" 01:16:44 dbaron: Either the person who wrote that assumed that the previous block is clearly the lowest block, or they assumed that you should also check all the previous blocks, but no implementor picked up on that. 01:17:05 dbaron: In some ways the spec is maybe better, but we have no implementations of that, because nobody ever pointed out this issue before #229. 01:17:40 Bert: I wrote those rules 15 years ago, and I definitely didn't want floats to move up when their containing block moved up. 01:17:56 Bert: The intention was definitely to check for the lowest thing of *everything* that came before. 01:18:13 Bert: I imagined keeping a running track of what is currently the lowest element. 01:18:28 fantasai: I think most impls do that, but also move it up if you have a negative margin. 01:18:44 dbaron: We do the same thing for floats, we just don't do it for blocks. We track the to pof the last float. 01:20:39 dbaron: In rule 4, we already have this condition... 01:20:52 dbaron: It helps, because we already have the hypothetical that we need. 01:22:04 dbaron: [something about rule 5, strike the "block or"] 01:22:16 dbaron: And then in rule 6, you'd only count the linebox containing the float, and not lineboxes earlier than that one. 01:23:30 dbaron: [something about negative margins] 01:24:06 [unminuted discussion] 01:24:17 plinss_: I think at this point we should lean toward undefined. 01:24:25 fantasai: We can't undefine the whole floats section! 01:24:47 fantasai: And fixing this is probably about as much effort as carefully undefining just the behavior we're talking about. 01:25:59 arronei: I'm up for a note. We have no testcases. 01:27:04 fantasai: What are you going to do? Report that we resolved this by noting that the spec is in error? 01:27:49 plinss_: I like David's suggestion - the spec is correct. In the future we'll create a testcase to identify impl issues, and address them at that time (possibly with spec issues). 01:28:50 plinss_: If we can do this by simply saying the interaction with negative margins is undefined, that's fine too. 01:28:57 dbaron: I think that is making too much undefined. 01:31:10 dbaron: We deifnitely want to limit it to negative vertical marings in the containing block prior to that float. 01:31:23 s/marings/margins/ 01:31:53 plinss_: Objections? 01:31:58 If, within the BFC, there is a negative margin such that it moves the float up from the position it would be at were the negative margin(s) set to zero, 01:32:01 arronei: I'm concerned there may be more interactions, but I'm okay. 01:32:10 the position of the float is undefined 01:32:48 agree with fantasai's proposal. 01:32:59 that seems to describe interop behavior. 01:33:15 If, within the BFC, there is a negative margin such that the floats position is above the position it would be at were all such negative margins set to zero, the position of hte float is undefined. 01:33:23 RESOLVED: Accept fantasai's edits for issue 229. 01:33:58 plinss_: Issue 239. 01:34:19 http://lists.w3.org/Archives/Public/www-style/2010Oct/0750.html 01:35:12 add "in-flow vertical" to margin above 01:35:18 was 239 the right number? Issue is currently marked closed. 01:35:23 johnjan, ^ 01:36:28 plinss_: Issue 242. 01:36:29 re-resolved to accept proposal for 241 in case we didn't accept it already 01:37:17 checking my list 01:38:09 239 is the correct issue. I didn't think we closed on Body propogating to HTML based on Alex's comments. 01:38:30 if we did, then my mistake. 01:38:33 Kazutaka0 has joined #CSS 01:43:12 RESOLVED: Defer 273 to future version, editorial. 01:43:16 plinss_: issue 274. 01:43:31 fantasai: 274 is related to the earlier one we discussed. 01:44:00 plinss_: Did we undefine this one implicitly? 01:44:02 fantasai: No. 01:44:46 dbaron: [something about lineboxes next to floats] 01:46:45 dbaron: Lineboxes are not shortened by a float that occurs after them. 01:46:59 which we could note can only occur under the undefined behavior we just added 01:47:10 RESOLVED: Accept dbaron's edit for 274. 01:47:14 plinss_: Issue 274. 01:47:21 plinss_: Issue 275 01:48:08 dbaron: This is saying that if you're in a 500px wide block, and you have a 490px wide float, and you're trying to place a word next to that float, which is more than 10px wide. 01:48:28 dbaron: It doesn't fit, so you push that linebox down until it's past the float, or there aren't any floats next to you and you just have an overflow. 01:48:53 Bert: But do you move the line box, or do you move the word? 01:49:02 Bert: and have empty line boxes all the way down? 01:49:19 dbaron: i remember discussing this in a meeting when tantek was on macIE. 01:49:40 dbaron: I think this was an intentional decision (to allow the gap to be a non-integral multiple of line-height) 01:49:57 dbaron: So the issue is that 9.4.2 says that lineboxes are stacked with no vertical separation. 01:50:09 dbaron: I'll say that 9.5 overrides 9.4.2 and we can just live with it. 01:50:23 dbaron: Or we can say in 9.4.2 "except as described in 9.5". 01:51:04 Bert: Kind of ugly, because it can mess up the vertical rhythm. 01:51:19 TabAtkins_: Many things can do that; we shouldn't worry about that until we have a spec that can solve it properly. 01:51:36 plinss_: So what's the resolution? Fix, or leave spec as it is? 01:52:53 plinss_: There are many places where one piece of prose overrides another. Let's just leave it. 01:52:57 leave as is. 01:53:14 note that 9.5 overrides 9.4.2 01:53:22 on the list 01:53:50 RESOLVED: No change for issue 275. 01:55:21 Bert: "(except as specified elsewhere)" 01:55:36 RESOLVED: accept Bert's proposal for 275. 01:56:08 plinss_: Issue 276 01:56:44 dbaron: I'm okay with the proposal. 01:56:55 fantasai: It's in CSS Selectors, though it's not better defined there. 01:57:07 that's OK, selectors has time to get it right. 01:57:14 fantasai: I think we should add a note that the precise behavior is undefined, and may be defined in a future version. 01:57:19 johnjan, not really, since it's ahead of 2.1... 01:57:41 good point... 01:57:56 RESOLVED: Note that :first-letter, :first-line are undefined, to resolve issue 276. 01:58:42 plinss_: Issue 277. 01:58:58 arronei: This is a terminology issue. We should get it right, but it's editorial. 01:59:07 dbaron: Though it affects DOM APIs... 01:59:33 I was just correcting "may confuse conversations" to "may or may have confused conversations or DOM APIs" 01:59:39 since CSSOM misuses declaration 02:04:50 A rule set (also called "rule") consists of a selector followed by a set of rules (also called "declaration blocks"). 02:04:52 RESOLVED: Defer issue 276 for errata. 02:05:10 277, right? 02:05:36 tantek has joined #css 02:05:54 s/276/277/ 02:05:55 right 02:06:31 plinss_: Issue 278. 02:06:45 dbaron: This is saying we should exlicitly say "margin box" to be clearer? Seems good. 02:06:49 RESOLVED: accept proposal for 278 02:06:50 RESOLVED: Accept edit for 278. 02:06:58 plinss_: Issue 279. 02:08:06 http://lists.w3.org/Archives/Public/www-style/2010Sep/0130.html 02:09:51 RESOLVED: Accept edit for 279. 02:09:54 plinss_: Issue 280. 02:10:06 dbaron: I believe 280 is an error in the spec, where the impls got it right and the spec is wrong. 02:10:11 http://dbaron.org/css/test/2011/css21-issue-280 02:10:59 dbaron: The question is whether fuschia starts within or below the purple box. 02:11:03 fantasai: We have full interop. 02:11:08 dbaron: ...which disagrees with the spec. 02:11:20 dbaron: I think the problem is that the spec can be taken more literally than intended. 02:11:38 dbaron: The spec says that [omg rule 3]. 02:11:59 dbaron: But this neglects the possibility that the right-floating box may be at the same vertical postion as the left float, but be entirely to its left. 02:12:08 dbaron: Which is this testcase. 02:13:17 dbaron: The change is to make the spec say "when they overlap in vertical position". 02:13:25 dbaron: But the spec literally says something wider. 02:13:31 s/wider/to the right/ 02:14:24 dbaron: so the implementations implemented what Bert meant to say, and Anton has noticed that this is not what was actually said 02:14:30 dbaron: "next to it" works. 02:14:45 Bert proposed "next to it" 02:15:04 RESOLVED: Change "to the right of it" into "next to it". 02:15:09 glazou: Issue 281. 02:15:41 no change necessary for 2.1 here.... errata 02:16:00 fantasai: I think we should fix this. It's just wrong. 02:16:25 dbaron: You could change it to "not a position derived from the line-height". 02:16:37 maybe change "not the 'line-height'" to "not a position derived from the 'line-height'" 02:17:00 fantasai: or just replace the clause with "and has nothing to do with the 'line-height'" 02:18:07 RESOLVED: Accept fantasai's edit for 281. 02:18:12 I can buy that 02:19:09 Meeting closed. 02:19:17 Still not on the plane, johnjan? 02:20:49 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 02:21:01 Meeting: CSS ftf day 2 02:21:13 Chair: Peter/Daniel 02:21:34 I have made the request to generate http://www.w3.org/2011/03/08-css-minutes.html Bert 02:24:51 dsinger has joined #css 02:33:52 jdaggett has joined #css 04:13:40 glazou has joined #css 04:19:10 TabAtkins_ has joined #css 04:35:01 plinss_ has joined #css 04:46:46 Arron has joined #css 04:53:59 plinss_ has joined #css 05:03:53 mmielke has joined #css 05:28:31 plinss_ has joined #css 05:57:31 plinss_ has joined #css 06:20:57 plinss_ has joined #css 06:55:11 kennyluck has joined #CSS 07:17:21 plinss_ has joined #css 07:37:13 philcupp has joined #css 07:38:28 Xaxio has joined #css 08:19:39 TabAtkins_ has joined #css 08:38:24 shepazu has joined #css 08:50:46 TabAtkins_ has joined #css 08:53:26 plinss_ has joined #css 08:58:17 Ms2ger has joined #css 09:09:59 homata has joined #CSS 11:12:03 arronei has joined #CSS 11:50:55 myakura has joined #css 11:57:35 anne has joined #css 13:26:08 jdaggett has joined #css 14:24:09 philcupp has joined #css 15:13:59 plinss_ has joined #css 15:26:48 plinss_ has joined #css 15:48:55 plinss_ has joined #css 16:06:08 Martijnc has joined #css 16:11:42 dsinger_ has joined #css 16:45:35 dbaron has joined #css 16:50:46 dsinger has joined #css 16:54:50 Arron has joined #css 16:55:51 stearns has joined #css 16:57:09 Does the F2F pre-empt the weekly conference call, or should I hop on the phone? 16:58:25 plinss_ has joined #css 17:01:42 shonda has joined #css 17:01:47 jdaggett has joined #css 17:02:43 dbaron has joined #css 17:02:51 stearns, dsinger, it pre-empts 17:02:52 glazou has joined #css 17:03:35 shan has joined #css 17:06:00 cslye has joined #css 17:06:49 RRSAgent, make logs public 17:06:56 I see no action items