W3C home > Mailing lists > Public > www-style@w3.org > October 2008

[CSSWG] Minutes and Resolutions 2008-10-08

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 17 Oct 2008 08:06:10 -0700
Message-ID: <48F8A9E2.2040003@inkedblade.net>
To: www-style@w3.org

Summary:

   - RESOLVED: No change to Media Queries in response to
                 http://lists.w3.org/Archives/Public/www-style/2008Sep/0218.html
               commas kept as error-handling points.
   - RESOLVED: Publish Media Queries as Last Call, deadline for comments
               4 weeks after TPAC.
   - RESOLVED: Add "Avoid breaking inside a replaced element" for Issue 74

====== Full minutes below ======

Attendees:
   David Baron
   Bert Bos
   Arron Eicholz
   Elika Etemad
   Sylvain Galineau
   Ming Gao
   Daniel Glazman
   Melinda Grant
   Anne van Kesteren
   Håkon Wium Lie
   Peter Linss
   Jason Cranford Teague

<RRSAgent> logging to http://www.w3.org/2008/10/08-css-irc

Agenda / Logistics
------------------

   Bert: I posted proposed times for our breaks on Sunday. Let me know if
         we want to change those
   * anne has nothing else planned for Sunday
   Daniel: Can we schedule a walk on the Riviera for Sunday? We don't seem
           to have a very full agenda this time.
   Peter: Let's see how the agenda shapes up

Media Queries
-------------

   <plinss> http://lists.w3.org/Archives/Public/www-style/2008Sep/0218.html
   Peter: David sent an email about commas being an error handling point
   David: The basic question is whether errors that are not inside an
          expression but are between commas cause only the stuff between
          commas to be ignored or the entire query list to be ignored
   David: Given the way error handling inside a query, this makes sense.
   David: But Acid3 assumes the whole query is invalid
   David: Which means we have several implementations that dot aht.
   David: I wanted to check that we should change our implementations
   Anne: I agree this makes sense.
   Anne: The way Hixie has fixed Acid3 is by commenting out the test, so it
         wouldn't affect passing
   Anne: Of course implementations would still have to change their behavior
   Anne: Opera is willing to change
   Peter: I assume Mozilla is willing to change. Microsoft?
   Anne: Microsoft doesn't have an implementation
   Peter: Any other issues?
   Anne: That's the only outstanding issue
   Melinda: Does WebKit have an implementation?
   Anne: Yes. I don't remember if Hyatt agreed with this change or not.
   Peter: I'm not hearing any opposition. Seems like a good idea to me.
   RESOLVED: No change to draft, accept commas as error-handling points.
   Anne: So, do we publish a Last Call draft now?
   fantasai: Yes, let's. Can we publish it before TPAC?
   Anne: I can try
   Peter: We'd still need to extend the Last Call period so people have
          time to comment
   RESOLVED: Publish Media Queries as Last Call, deadline for comments 4
             weeks after TPAC
   <Zakim> +Ming
   <Zakim> +howcome

<anne> (fwiw, I now filed the bugs on WebKit I listed in
         http://krijnhoetmer.nl/irc-logs/css/20081007 so all three
         browsers have the bugs filed for the CSS Namespaces Module.
         Hopefully they're fixing soon :) )

Test Suite Harness
------------------

   Peter: We had an internal meeting on the test suite harness at HP.
   Peter: Don't know how long we can have people working on it, so
          wanted to get comments.
   Melinda: It would be cool if everybody could give it a 1/2 hour spin
   Peter: Biggest thing is need to work on reporting functionality
   <fantasai> http://wiki.csswg.org/test/harness
   fantasai: hmm.. the prototype seems to be very out of date
   Melinda, Peter: We'll send out a url when the latest and greatest
                   is available
   fantasai: We redid the templates
   fantasai: Also added ability to add a mode to the UA string: whether
             you are testing desktop screen, or projection mode, or
             print or print preview
   fantasai: so those can each get a different set of results

Page Break of Floats
--------------------

   Melinda: I wanted to revisit Issue 74
   Melinda: http://wiki.csswg.org/spec/css2.1#issue-74
   <plinss> http://lists.w3.org/Archives/Public/www-style/2008Oct/0046.html
   fantasai: I agree with adding "Avoid breaking inside a replaced element"
   fantasai: I'm not convinced about the other part
   fantasai: I'm concerned about breaking web layouts
   fantasai: which rely on floats and tables
   Melinda: This whole section is fuzzily worded anyway
   Melinda: we want implementations to think about what they're doing and
            do the best they can
   Melinda: At some point we may evolve more rigorous rules here.
   Howcome: I think i agree that more rigorous rules would be useful, but
            at this point I don't know what they would be
   Peter: where do we go from here?
   fantasai: Does anyone object to adding "Avoid breaking inside a replaced
             element"?
   RESOLVED: Add "Avoid breaking inside a replaced element" for Issue 74
   fantasai: I'm not terribly excited about the other stuff. I would prefer
             to leave it out of 2.1
   Peter: I agree. If we're going to specify better page-breaking behavior,
          we should do that with explicit rules and properties.
   Peter: We should think about what should be the proper behavior and how
          do we give the author appropriate controls.
   RESOLVED: Don't add other sentence to 2.1

Other
-----

   fantasai: We have a couple issues that need testcases. If people could
             help with those...
   Arron: We might have some written. I was going to take a look today.
   fantasai: Issues 53, 57, and 69 need test cases.
Received on Friday, 17 October 2008 15:06:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:15 GMT