- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 13 Dec 2010 16:54:38 -0800
- To: "www-style@w3.org" <www-style@w3.org>
Summary:
- RESOLVED: Clarify that fantasai's response to PFWG's comment on css3-background
is official.
- LC on Fonts WG's WOFF: http://www.w3.org/TR/WOFF/
- LC on WebAPI WG's Progress Events: http://dev.w3.org/2006/webapi/progress/
- Reviewed status of CSS2.1 Test Suite
- Telecons cancelled for the holidays: 29th
- RESOLVED: Make it undefined in CSS2.1 whether forced break before first page
creates a :first page or a blank page
====== Full minutes below ======
Present:
David Baron
Bert Bos
Arron Eicholz
Elika Etemad
Simon Fraser
Daniel Glazman
Koji Ishii
John Jansen
Håkon Wium Lie
Chris Lilley
Peter Linss
Daniel Weck (late)
Steve Zilles
<RRSAgent> logging to http://www.w3.org/2010/12/08-CSS-irc
Scribe: fantasai
Administrative
--------------
glazou: One extra agenda item from ChrisL
glazou: anything else?
CSS3 Backgrounds and Borders
----------------------------
glazou: What is the status of css3-background?
fantasai: I don't know.
glazou: Were there comments from other WGs that weren't responded to?
fantasai: Not that I know of. Certainly not from PFWG -- those were
responded to.
ChrisL summarizes the situation.
ChrisL: We have a timeline of what happened posted to our WG list,
but nothing has been communicated to PFWG yet.
Bert: I see that fantasai already added the issue to the DoC.
Bert: I don't have a date yet for the telecon with the director.
Bert: I'm not sure what else we do?
glazou: If we have nothing to do that's fine, I just wanted a short report.
ChrisL: I was saying, we have our story straight, but we haven't
communicated back to WAI-PF
Bert: So sounds like we should have a resolution to affirm fantasai's response
<ChrisL> yes lets clarify the official position
RESOLVED: fantasai's reply is official
ACTION Glazman: send response
<trackbot> Created ACTION-279 - Send response to WAI PF [on Daniel Glazman - due 2010-12-15].
fantasai: Does this mean that every time PFWG sends a comment, if my
response is a clarifying question to them, we need a group
resolution that the response is official before they will reply?
Bert: Yes.
ChrisL notes that Tracker can now have cross-wg issues
<ChrisL> got a link to the timeline?
<Bert> -> http://lists.w3.org/Archives/Public/www-archive/2010Dec/0004.html
Fantasai's timeline of the WAI issue
WOFF Last Call WD
-----------------
<glazou> http://www.w3.org/TR/WOFF/
ChrisL: LC on WOFF
ChrisL: We have tried to keep WOFF orthogonal with CSS
ChrisL: But it would be nice to get comments from someone in this WG
not on the Fonts WG
ChrisL: Even if the comment is "no comment"
ACTION glazou: review WOFF
<trackbot> Created ACTION-278 - Review WOFF [on Daniel Glazman - due 2010-12-15].
Progress Events
---------------
<glazou> http://dev.w3.org/2006/webapi/progress/
glazou: LC comments due Jan 13
http://dev.w3.org/2006/webapi/progress/
ACTION everyone: review and send comments on WebAPI Progress Events draft
CSS2.1 Test Suite
-----------------
glazou: Chris, I saw you sent a message about Prince an hour ago
ChrisL: I ran all the paged media tests and the tests that don't have
two passes
ChrisL: About 250 tests
howcome: Excellent work.
<howcome> http://lists.w3.org/Archives/Public/public-css-testsuite/2010Dec/0117.html
fantasai: I still haven't made it through all the issues reported against
the test suite
<glazou> http://test.csswg.org/harness/results?s=CSS21_%HTML_RC3&t=0&f[]=1&f[]=4&f[]=8&f[]=16
fantasai: It's the only thing I'm working on, though, so I can't go any
faster...
howcome: Chris's results haven't been imported yet
Peter: ChrisL, I sent you a link that shows the tests that are needed in
the order that they're needed
Peter: It's the same way as entering data for browsers, except it overrides
the UA string to say it's Prince
+danielweck
<plinss_> http://test.csswg.org/harness/testcase?s=CSS21_HTML_RC3&u=435&o=1
<plinss_> http://test.csswg.org/harness/testcase?s=CSS21_XHTML_RC3&u=435&o=1
Peter: If you use either of these to URLs, it will show tests in the order
most needed for Prince.
Peter: wrt broken lists in the page there, it's because the harness doesn't
know there's one test suite with two formats
Peter: It thinks there are two test suites, and I just had it allow
wildcards in the test suite names
Peter: Once I get reftest support in the harness, I'll work on that
Peter: The harness says that 80 tests need additional results, and may or
may not have two passes when we import Prince's results
Peter: 26 tests with blocking failures means one or more engines need to
fix their bugs to get passes
<glazou> http://test.csswg.org/harness/results?s=CSS21_HTML_RC3&t=0&f[]=1&f[]=4&f[]=8&f[]=16
arron: Maybe we should do another RC just to get the updated tests out there
fantasai: I can push another release out today. What's blocking me is
fixing the rest of the tests.
arronei: Let's just publish RC4, and fix the rest for RC5
ACTION fantasai: publish RC4 asap, push remaining fixes to RC5
<trackbot> Created ACTION-280
Holiday Schedule
----------------
glazou: Question related to the schedule: Who is going to be away during
the holiday season?
<szilles> I will be away from the 22nd thru 3rd of Jan
plinss_: HP officially shuts down from 22nd to Jan 3rd. I won't be going
anywhere
<dbaron> I'll be on the east coast for a bit, but will likely be able to
call in.
fantasai: I'll be flying on the 22nd, but available on the 29th
<johnjan> I'll be offline from the 20th - 3rd
<oyvind> (I'll be offline, including 29th)
<sylvaing> I'll be out Christmas week.
arronei: I'm going to be around until the end of the year, so should be
able to address any MS comments
arronei: Will do impl report with new RC soon as well
<Bert> I'm unavailable on 22 and 29, and almost certainly also on 5.
Telecon cancelled on the 29th
CSS2.1 :first Page Selectors After Page Break
---------------------------------------------
howcome: I had an action point to look into a test
howcome: first-page-selectors-003
<howcome> http://lists.w3.org/Archives/Public/www-style/2010Nov/0421.html
howcome: It would be good to resolve whether it is valid
howcome: It's not clear right now.
howcome: We may want it to be valid
howcome: But we'd have to change the spec slightly
howcome: Question is if you force a break before the first page, is
the first actual page selected by :first?
oyvind thinks the first page that is not printed should match :first
howcome: It's more useful if you select something that's there.
howcome: I think it makes more sense to select the first thing that's printed
howcome: But if we are to do that, we probably need to change CSS2.1
<oyvind> I have no strong opinions on what it should match, but I think
the spec needs to be clarified
fantasai: It would be a clarification -- the spec right now is quite vague
fantasai: This was certainly the intent in CSS3 Paged Media. There is no
other way to specify whether the first page is a left or right page
johnjan: I'd like a day or two to make sure Alex is comfortable with it
http://www.w3.org/TR/CSS21/page.html#page-selectors
howcome: What we're putting here is really a hack to say whether the
first page is :left or :right
Bert: I've used forced page breaks to create a blank first page
glazou: Both interpretations are useful; but we have to pick one
fantasai: We could leave this undefined for 2.1
howcome: I think we might have trouble finding implementations
arronei: They all currently fail
RESOLVED: Make it undefined whether forced break before first page creates
a :first page or a blank page
ACTION fantasai: Propose wording
<trackbot> Created ACTION-281
ACTION fantasai: move page-selector-003 and page-selector-004 to css3-page TS
<trackbot> Created ACTION-282
glazou: Anything else we can do on 2.1?
Gradients
---------
glazou: Can anyone summarize? Are we reaching a consensus?
Simon: I think we have to have Tab here. I don't think we have agreement
between Brad and Tab yet
glazou: I read a few of the proposals, and some of them declared as simple
and easy just scared me
Simon: Tab has an advantage in that he has a spec. I don't quite understand
Brad's propsal well enough to know whether I can implement it.
Steve: We seem to be getting very complex in the backgrounds. Wouldn't it
make more sense to generate images and be able to plug it in as a
background.
fantasai: we're doing that already ...?
Simon: Backgrounds have more things to deal with, e.g. tiling
Simon: If you rotate the image, do you also rotate the grid?
Simon: Sounds complicated
Steve: Tying the way images are processed to the way the grid is done seems
like a problem.
Simon: I don't think we're tying them together.
...
Simon: Rick was suggesting rotation as an alternate way to have angled
gradients
fantasai: The reason you want the angle information in the gradient itself
is that it allows the gradient to be sized appropriately to the box
Simon: I agree
Simon: ... mailing list
glazou: Anything else to discuss in the 8 remaining minutes?
Meeting closed.
Received on Tuesday, 14 December 2010 00:55:15 UTC