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