/irc-logs / w3c / #css / 2009-06-03 / end

Options:

# Session Start: Wed Jun 03 00:00:00 2009
# Session Ident: #css
# [00:14] * Quits: dbaron (dbaron@93.10.129.79) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [00:17] * Quits: MoZ (chatzilla@89.159.37.7) (Ping timeout)
# [00:24] * Joins: MoZ (chatzilla@89.159.37.7)
# [00:57] * Joins: dsinger (dsinger@17.202.35.52)
# [00:57] * Quits: dsinger (dsinger@17.202.35.52) (Client exited)
# [01:15] * Quits: arronei (arronei@131.107.0.111) (Client exited)
# [01:15] * Joins: arronei (arronei@131.107.0.112)
# [03:28] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [03:30] * Joins: karl (karlcow@128.30.54.58)
# [05:24] * Quits: Bert (bbos@mcclure.w3.org) (Ping timeout)
# [05:29] * Joins: Bert (bbos@mcclure.w3.org)
# [05:36] * Quits: anne (annevk@82.227.229.89) (Ping timeout)
# [05:59] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
# [06:01] * Quits: Bert (bbos@mcclure.w3.org) (Client exited)
# [06:01] * Joins: Bert (bbos@mcclure.w3.org)
# [07:12] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [07:16] * Joins: dbaron (dbaron@93.10.129.79)
# [07:16] * Quits: dbaron (dbaron@93.10.129.79) (Connection reset by peer)
# [07:16] * Joins: dbaron_ (dbaron@93.10.129.79)
# [07:16] * dbaron_ is now known as dbaron
# [07:17] <dbaron> sleep is, apparently, only for the non-jetlagged :-(
# [07:25] <MikeSmith> dbaron: 6am there?
# [07:26] <dbaron> MikeSmith, 7:22 now, but I went for a run at 6:15 after giving up on sleeping
# [07:33] <MikeSmith> dbaron: you can sleep during the meeting
# [07:33] <MikeSmith> that's what I usually do
# [07:53] * dbaron had some Café Noir with breakfast
# [08:06] * Quits: dbaron (dbaron@93.10.129.79) (Ping timeout)
# [08:08] * Joins: annevk (opera@80.13.73.211)
# [08:20] * Joins: mollydotcom (molly@90.28.244.209)
# [08:20] <mollydotcom> hey, anyone over at the office with a car?
# [08:20] <mollydotcom> Need ride! Farther away than I thought to walk, but only a few minutes by car
# [08:21] <mollydotcom> I sent directions to the email list
# [08:22] <mollydotcom> I await a chariot
# [08:25] * Quits: mollydotcom (molly@90.28.244.209) (Ping timeout)
# [08:26] <annevk> heh
# [08:26] * annevk wonders if molly knows about this taxi concept
# [08:27] * Joins: mollydotcom (molly@90.52.78.229)
# [08:28] <mollydotcom> alloooooooooooo
# [08:32] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
# [08:33] <annevk> mollydotcom, taxi :)
# [08:38] <mollydotcom> yep, they are calling one now
# [08:38] <mollydotcom> thanks :)
# [08:39] <mollydotcom> I figured if I caught someone on the way it would be better but they can get me a taxi in five minutes
# [08:39] <mollydotcom> okay, on my way
# [08:39] * Quits: mollydotcom (molly@90.52.78.229) (Quit: mollydotcom)
# [08:45] * Joins: ChrisL (ChrisL@128.30.52.30)
# [09:01] * Quits: annevk (opera@80.13.73.211) (Quit: annevk)
# [09:03] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [09:10] * Joins: Arron (arronei@193.51.208.72)
# [09:11] * Joins: dbaron (dbaron@193.51.208.72)
# [09:21] * Joins: RRSAgent (rrs-loggee@128.30.52.30)
# [09:21] <RRSAgent> logging to http://www.w3.org/2009/06/03-CSS-irc
# [09:21] <dbaron> RRSAgent, make logs public
# [09:21] <RRSAgent> I have made the request, dbaron
# [09:21] <dbaron> Meeting: CSS Working Group Face-to-Face
# [09:21] <dbaron> Chair: Daniel Glazman
# [09:22] * Joins: sylvaing (sylvaing@193.51.208.72)
# [09:24] * Joins: anne (annevk@193.51.208.72)
# [09:24] * Joins: glazou (glazou@193.51.208.72)
# [09:24] * Quits: ChrisL (ChrisL@128.30.52.30) (Ping timeout)
# [09:25] * Joins: mollydotcom (molly@193.51.208.72)
# [09:25] * Joins: jdaggett (jdaggett@193.51.208.72)
# [09:25] * Joins: ChrisL (ChrisL@128.30.52.30)
# [09:26] <jdaggett> karen goes for the food
# [09:26] <ChrisL> trackbot, start telcon
# [09:26] * trackbot is starting a teleconference
# [09:26] <trackbot> RRSAgent, make logs member
# [09:26] <RRSAgent> I have made the request, trackbot
# [09:26] * Joins: Zakim (rrs-bridgg@128.30.52.30)
# [09:26] <trackbot> Zakim, this will be Style_CSS FP
# [09:26] <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
# [09:26] <trackbot> Meeting: Cascading Style Sheets (CSS) Working Group Teleconference
# [09:26] <trackbot> Date: 03 June 2009
# [09:26] <ChrisL> zakim, remind us in 8 hours to go home
# [09:26] <Zakim> ok, ChrisL
# [09:26] <ChrisL> scribenick: ChrisL
# [09:26] <dbaron> Present: Sylvain Galineau, Steve Zilles, Daniel Glazman, John Daggett, Bert Bos, Anne van Kesteren, Alex Mogilevsky, Håkon Wium Lie, Molly Holzschlag, Elika Etemad, Arron Eicholtz, Chris Lilley, David Baron
# [09:26] <ChrisL> topic: testsuites
# [09:27] * Joins: fantasai (fantasai@66.252.19.122)
# [09:27] <ChrisL> dg: CSS2.1 testsuite is a major item
# [09:27] <ChrisL> ... we should have ts and imp reports by end of 2009 to be on time for charter
# [09:27] * Joins: alexmog (alexmog@193.51.208.72)
# [09:27] <ChrisL> ... problem is to decide when to stop, which we are not good at
# [09:28] <ChrisL> ... its for CR exit criteria and then secondly a continuously improved, large one
# [09:28] <ChrisL> ... we can't improve the first one forever or we will never get to rec
# [09:29] <ChrisL> dg: also we have many modules getting ready for cr and not test suites for most of them
# [09:29] <ChrisL> ee: we have it for some, build scripts need some work
# [09:30] <ChrisL> dg: test suites are part of the technical work. its part of what we do. we need sustained commitment to finish specs by doing test suites. otherwise the specs are useless
# [09:31] <ChrisL> ae: is the process fully documented?
# [09:31] <ChrisL> jd: at last f2f we parcelled out the tests. i l looked at the font submissions, it was not clear where some of the tests came from
# [09:32] <ChrisL> ... there are build scripts that don't work, tests that are in svn, tests on ms page not in svn. format varies too
# [09:32] <ChrisL> ...so it all needs some work
# [09:32] <ChrisL> ee: yes, some is half finished
# [09:33] <ChrisL> ... supposed to have build scripts continually rnning, thats not been done yet
# [09:34] <ChrisL> jd: i was writing a script to try and pull all this together because looking at source one by one is tedious
# [09:34] <ChrisL> ee: ok so lets get that script and put it on the server
# [09:35] <ChrisL> jd: its not packaged, and volunteers need a packaged product and platform-independent instructions
# [09:35] <ChrisL> ... eg rendering can be off by half a pixel, rather than "switch off cleartype"
# [09:36] <ChrisL> jd: we need packaged zips of tests, with as version number, so we know what people have tested
# [09:36] <ChrisL> ee: not looked at platform specifics, probably mainly affects fonts, will need to look at this more
# [09:36] <ChrisL> ... need to get the build scripts working
# [09:37] <ChrisL> jd: need to prune out obsolete stuff like old build scripts, old instructions that are wrong, etc
# [09:37] <ChrisL> ee: yes some of it is a mess but its possible to review from the source
# [09:38] <ChrisL> ae: chapter 4 needs http
# [09:39] <ChrisL> jd: there are instructions that say install this font then take it out "at the end" .... end of what
# [09:39] <ChrisL> hl: tests are better online, but yes we need versioning, dated versions like in CSS1 test suite
# [09:40] <ChrisL> jd: main thing is it should be simple to run
# [09:40] <ChrisL> hl: should not call them conformance tests
# [09:40] <ChrisL> (several agrees)
# [09:41] * Bert wonders what people will think if we call it a "non-conformance test suite" :-)
# [09:42] <ChrisL> hl: want to see the term removed. don't call them a "conformance" test suite
# [09:42] <ChrisL> ee: easy to fix
# [09:42] <ChrisL> jd: a lot of pages, some outdated. need to tidy them up
# [09:43] <ChrisL> ... never clear what the status was. some need to be marked as not maintained
# [09:43] <ChrisL> avk: please cite specific examples
# [09:43] <ChrisL> bb: wiki pages are just scratch pads, ignore those
# [09:43] <fantasai> http://www.w3.org/Style/CSS/Test/
# [09:44] <ChrisL> jd: people need to know what to ignore
# [09:44] <ChrisL> ee: wiki pages say how to contribute to the project
# [09:45] <ChrisL> jd: are we going to merge these?
# [09:45] <ChrisL> ee: yes eventually
# [09:45] * Quits: MoZ (chatzilla@89.159.37.7) (Quit: ChatZilla 0.9.84 [Firefox 3.0.10/2009042315])
# [09:45] <ChrisL> ae: this page is the central hub but it needs links to instructions
# [09:45] <ChrisL> ee: wiki has the instructions
# [09:46] <jdaggett> http://wiki.csswg.org/test/css2.1
# [09:46] <ChrisL> jd: wiki talks of cvs but now we are using svn
# [09:47] <ChrisL> ee: happy to move tests to the w3c site, would like them to be in svn as we often move directories
# [09:47] <ChrisL> jd: so already reviewed tests will be suppleented by ms tests, once reformatted?
# [09:48] <ChrisL> ee: should be same format
# [09:48] <ChrisL> jd: but there can be tests per chapter
# [09:48] <ChrisL> ee: will make snapshots more regularly, also combine so we have svn as the master repository
# [09:49] <ChrisL> jd: main thing is to have the documentation more clear
# [09:50] <ChrisL> ee: (argues convincingly that its easier to tidy up the structure than document the existing brokenness)
# [09:50] <ChrisL> avk: if changes are made, do they propogate to the ms test suite?
# [09:51] <ChrisL> ae: probably easier to send comments rather than test changes as we have multiple internal copies and some internal red tape to go through
# [09:51] <ChrisL> ... easier for me if people send feedback to mailing list rather than modifying tests
# [09:52] <ChrisL> ... want to have a same week turnaround for changes to the tests after review
# [09:52] <ChrisL> dg: so when will we be done?
# [09:52] <ChrisL> ae: december is a good target if we have the reviews
# [09:53] <fantasai> dg: The test suite is done when we have less tests coming in and the review comments are no longer finding lots of errors in the tests
# [09:54] <ChrisL> dg; need to decide when we are done (for CR)
# [09:54] <ChrisL> dg: deadline for submitting nw tests would help, i can't decide that alone
# [09:55] <ChrisL> ae: we have submitted all the ones that we think are needed
# [09:56] <ChrisL> dg: so it comes doen to a problem of commitment. its less interesting
# [09:56] <ChrisL> ... we have a bad image in the consortium because of this
# [09:56] <ChrisL> avk: color and namespaces, test have come fast. also for media queries
# [09:57] <ChrisL> dg: yes, we have submissions but all over the place. no implementation report, not instructions, no review. having some tests is only the first step
# [09:58] <ChrisL> db: for selectors we are lacking imp reports
# [09:58] <ChrisL> ee; selectors tests build script is broken
# [09:58] <ChrisL> dg; original one was a directory, its become more complex now
# [09:58] <ChrisL> mh: sounds like we need some project management
# [09:59] <ChrisL> ee: familiar with the technical basis but have no project management skills
# [09:59] <ChrisL> (laughter)
# [09:59] <ChrisL> hl: you are the right person
# [10:00] <ChrisL> jd: moz japan has funding for an intern to do testing
# [10:01] <ChrisL> dg; want a one-click setup of a framework for nrew tests, so it all builds and you just drop in tests
# [10:01] <ChrisL> ... reusable instructions
# [10:01] <ChrisL> s/nrew/new/
# [10:02] <ChrisL> ee: for most test suites, they can reuse the same instructions. its only if they need something special
# [10:03] <ChrisL> dg: we could have 30 test suites if you look at all the modules
# [10:03] <ChrisL> ee: its just a few lines of config script
# [10:03] <ChrisL> db: lets not add more requirements
# [10:03] <ChrisL> dg: trying to avoid revisiting this for each test
# [10:04] <ChrisL> avk; can avoid having html, xhtml, xml versions
# [10:04] <ChrisL> ee: build scripts do wquite a lot in fact
# [10:04] * Quits: sylvaing (sylvaing@193.51.208.72) (Quit: sylvaing)
# [10:04] * Joins: sylvaing (sylvaing@193.51.208.72)
# [10:04] <ChrisL> ... makes TOC for example, by chapter and section
# [10:05] <ChrisL> dg: so, all tests subitted by september/october 2009?
# [10:05] <ChrisL> ... for css 2.1
# [10:06] <ChrisL> dg: tests bu 15 Sept, reviews by 1 Dec. then we can do a release at new year
# [10:07] <ChrisL> s/bu/by/
# [10:07] * Parts: sylvaing (sylvaing@193.51.208.72)
# [10:07] <ChrisL> dg: ok so lets really do it this time
# [10:07] * Joins: sylvaing (sylvaing@193.51.208.72)
# [10:08] <ChrisL> dg; we should be able to get to PR by end of year
# [10:08] <ChrisL> avk: we do need the implementations
# [10:09] <ChrisL> cl; need the reports to see where the implementation gaps are
# [10:10] <ChrisL> cl: a coverage report is needed, to show spec coverage
# [10:10] <ChrisL> avk; for navigation, just a directory listing is fine
# [10:10] <ChrisL> ... not sure we should updaste the build scripts
# [10:11] <ChrisL> db: would like to discuss test format and do a demo
# [10:11] <ChrisL> dg; selectors test suite, all we need is imp reports
# [10:12] <ChrisL> ee: also needs some tests to be dropped and a couple others added
# [10:12] <ChrisL> db; have sent imp reports four times already
# [10:12] <ChrisL> cl; can just remove non-relevant lines from existing reports
# [10:12] <ChrisL> ee: so the build is broken and only hixie can fix
# [10:13] <ChrisL> s/;/:/g
# [10:13] <ChrisL> db: copied color build scripts from selectors?
# [10:13] <ChrisL> ee: no, from css2.1 in fact
# [10:14] <ChrisL> db; how crucial are the newly added tests
# [10:14] <ChrisL> ee: format is reaslly wierd. its some xml thing that hixie made up
# [10:14] <ChrisL> db: but dont redisign the entire thing to add one more test
# [10:14] <fantasai> Hixie, are you still able to build the Selectors test suite?
# [10:14] <Hixie> hm?
# [10:14] <Hixie> haven't tried in many years
# [10:15] <Hixie> what's up?
# [10:15] <ChrisL> cl: better to make an xslt that converts it to a more directly useful format
# [10:15] <glazou> Hixie: that would help us a lot if you could do it
# [10:15] <ChrisL> ee; lachlan added tests, could not build it either
# [10:15] <glazou> Hixie: a few tests were added and some removed
# [10:15] <Hixie> the format is daniel's, i think :-)
# [10:15] <ChrisL> avk: just link to the additional tests
# [10:15] <ChrisL> jd: sucks
# [10:15] <glazou> Hixie: we're not speaking of format but build scripts
# [10:15] <Hixie> oh
# [10:15] <fantasai> fantasai: The source format is not something you can run
# [10:16] <fantasai> Hixie, IIRC, neither lachlan nor I was able to run the build scripts
# [10:16] <Hixie> the answer appears to be "no", because my copy wasn't from cvs
# [10:16] <Hixie> what's the error?
# [10:17] <ChrisL> dg: so mozilla has almost complete coverage for selectors. what about opera and microsoft?
# [10:17] * fantasai tries again
# [10:17] <ChrisL> db: can we see what tests changed, rather than re-run the entire thing again?
# [10:17] <ChrisL> hl: much easier
# [10:18] <fantasai> Hixie, I'm not getting an error, I'm only just not getting any built tests
# [10:18] <fantasai> Hixie, dist is empty
# [10:18] <ChrisL> hl: depends on how many tests need to be re-run
# [10:18] <Hixie> fantasai: odd
# [10:18] <ChrisL> db: selectors takes about an hour to re-run
# [10:19] <Hixie> fantasai: mail me a tarball
# [10:20] <ChrisL> db: last time i sent a report, no-one else did so .....
# [10:20] <ChrisL> dg: we have a two year charter and need to get it done
# [10:20] <ChrisL> hl: why was the test suite changed
# [10:20] <ChrisL> dg: because we removed a section, and found some tests were missing
# [10:21] <ChrisL> db: we did outr reports and then some more tests arrived. we need to decide to freeze it and stick to that decision
# [10:21] <ChrisL> avk: we changed selection
# [10:22] <ChrisL> hl: who accepted the additional tests
# [10:22] <ChrisL> avk: lachlan submitted them
# [10:23] <fantasai> Hixie, sent
# [10:23] <ChrisL> mh; do we have an acceptance policy
# [10:23] <ChrisL> dg: yes but we didn't follow it
# [10:23] <ChrisL> action: chris run the six new selectors tests on opera
# [10:23] * trackbot noticed an ACTION. Trying to create it.
# [10:23] <trackbot> Sorry, amibiguous username (more than one match) - chris
# [10:23] <trackbot> Try using a different identifier, such as family name or username (eg. ChrisWilson, clilley)
# [10:23] * RRSAgent records action 1
# [10:24] <ChrisL> action: chris to run the six new selectors tests on opera
# [10:24] * trackbot noticed an ACTION. Trying to create it.
# [10:24] * RRSAgent records action 2
# [10:24] <trackbot> Sorry, amibiguous username (more than one match) - chris
# [10:24] <trackbot> Try using a different identifier, such as family name or username (eg. ChrisWilson, clilley)
# [10:24] <ChrisL> action: clilley to run the six new selectors tests on opera
# [10:24] * trackbot noticed an ACTION. Trying to create it.
# [10:24] * RRSAgent records action 3
# [10:24] <trackbot> Created ACTION-147 - Run the six new selectors tests on opera [on Chris Lilley - due 2009-06-10].
# [10:24] <fantasai> Hixie, sorry, I used a different email address by accident, search for my first name
# [10:25] <fantasai> if you're trying to find it in your inbox
# [10:25] <fantasai> or search for selectors :)
# [10:25] <fantasai> (in the subject)
# [10:27] <ChrisL> cl: color module seems to have mostly complete coverage now
# [10:27] <Hixie> fantasai: and nothing has changed except the test files? so i can ignore everything but the test files?
# [10:27] <ChrisL> db; sent in some implementation report already
# [10:27] <fantasai> Hixie: right
# [10:27] <ChrisL> s/;/:/g
# [10:28] <fantasai> Hixie: I made a change to the makefile so the perl command would run under bash
# [10:28] <fantasai> Hixie: but other than that I have not touched the build scripts
# [10:28] * Hixie uses bash
# [10:28] <fantasai> Hixie: we added some files (css3-modsel-184?.xml) and removed a few
# [10:29] * fantasai isn't sure why the Makefile was complaining then
# [10:29] <fantasai> ScribeNick: fantasai
# [10:29] <fantasai> dbaron: One issue with our test suites is that they have to be run manually, and that's a laborious possible
# [10:29] <fantasai> dbaron: Insofar as we can run tests automatically, we should do that
# [10:30] <fantasai> dbaron: It could reduce the amount of time needed to run the tests
# [10:30] <fantasai> dbaron: This can make it much quicker to create an implementation report
# [10:30] <fantasai> dbaron: and to keep implementations from regressing
# [10:31] * Joins: howcome (howcome@193.51.208.72)
# [10:31] <fantasai> dbaron: The idea of reftests is that the test consists of two HTML files plus an assertion that those two files either look the same or don't look the same
# [10:31] <fantasai> dbaron: It's something that can be automated
# [10:31] <fantasai> dbaron: but is also something you can run manually
# [10:31] <fantasai> dbaron: Here are two tests I can run manually.
# [10:31] <fantasai> dbaron: I can open them in two tabs and flip between them, to verify that they're the same
# [10:32] <fantasai> dbaron: You can also run them automatically
# [10:32] <fantasai> dbaron: Our implementation for running this automatically uses canvas and JavaScript
# [10:32] <fantasai> dbaron: other implementations can use other automation frameworks
# [10:33] <fantasai> dbaron: and you can also run the tests manually
# [10:33] <fantasai> dbaron: There's a whole lot of stuff you can automate this way, although not everything
# [10:34] <fantasai> dbaron: The counters tests I submitted for CSS2.1, for example, were originally reftests
# [10:35] <fantasai> dbaron: I would like to be able to submit tests in this format
# [10:36] <fantasai> discussion of some tests
# [10:36] <fantasai> glazou: box-shadow with blur radius, combine with image?
# [10:36] <fantasai> fantasai: can't do that because gradient for blur radius is explicitly undefined
# [10:36] <fantasai> dbaron: The not-equals tests can be useful to check that assumptions are correct
# [10:37] <fantasai> http://mxr.mozilla.org/mozilla/source/layout/reftests/
# [10:38] <fantasai> avk: Opera uses an image-based regression test framework
# [10:38] <fantasai> avk: we compare to screenshots
# [10:38] <fantasai> jdaggett: For a lot of these tests you need to notice a 1px difference
# [10:38] <fantasai> jdaggett: Some of the Microsoft tests, it's really hard to tell
# [10:39] <fantasai> dbaron shows off his box model acid test
# [10:39] <fantasai> http://mxr.mozilla.org/mozilla/source/layout/reftests/box-properties/CSS21-t100303.xhtml
# [10:39] <fantasai> http://mxr.mozilla.org/mozilla/source/layout/reftests/box-properties/CSS21-t100303-ref.xhtml
# [10:40] <fantasai> dbaron: It's much better to write a test that combines a lot of assertions than to require the tester to run 600 individual tests that are all almost the same
# [10:41] <fantasai> jdaggett: The automation is always going to be vendor-specific
# [10:41] <fantasai> dbaron: I'm not saying we should require tests in this format, but that we should allow tests to be submitted in this format
# [10:42] * Parts: howcome (howcome@193.51.208.72)
# [10:43] <fantasai> Bert: comparing two PDFs will be a bit more difficult than comparing two screenshots
# [10:43] <fantasai> Bert: This is fine for a browser
# [10:43] <fantasai> Bert: But how am I going to test Prince, or Opera Mini, or HP's printer?
# [10:44] <fantasai> Bert: Hold two pieces of paper against the light?
# [10:45] <ChrisL> yes, compare them by hand. the tests can be run manually, but are also automatable in some cases
# [10:45] <fantasai> Discussion of metadata
# [10:46] <fantasai> Reftests should have all relevant metadata: author, help, assertion, flags, etc
# [10:46] <fantasai> Chris: SVG compares SVG and a PNG image, we do side-by-side comparisons and have a harness for hit
# [10:46] <fantasai> s/hit/it/
# [10:47] <fantasai> jdaggett: The key point of this format is that it's not rendering vs image, but rendering vs rendering
# [10:47] <fantasai> jdaggett: With images you can't guarantee the same image across multiple platforms
# [10:47] <fantasai> (anti-aliasing, etc)
# [10:48] <fantasai> Steve: There are a number of cases where we've consciously left things undefined, so you cannot assert pixel equivalence
# [10:48] <ChrisL> jes, using raster images relies on specific font rendering so it makes it harder to automate. markup equivalents are better as the platform difference is evened out
# [10:48] <ChrisL> s/jes/yes/
# [10:49] <Hixie> i figured out the problem with the test suite generator
# [10:49] <Hixie> fantasai: remove the first line of generate.pl
# [10:50] <Hixie> fantasai: and rerun make
# [10:50] <ChrisL> bb: why are we allowing another format that is different to what we decided some years ago?
# [10:50] <ChrisL> dg: because it allows automated testing and means we get more results
# [10:50] <ChrisL> bb; think this is worse
# [10:51] <ChrisL> db: its much faster to run through tests in this format
# [10:51] <ChrisL> am: we have very little project management here, thats why we are lagging
# [10:51] <Hixie> fantasai: there'll be an updated copy on my site by the time i hit enter on this sentence
# [10:51] <Hixie> ok it'll take a few more minutes
# [10:52] <ChrisL> avk: this format is a lot better for implementors
# [10:52] <ChrisL> bb: some implementors
# [10:52] <ChrisL> avk: no, most
# [10:52] <fantasai> Hixie: ok
# [10:52] <ChrisL> dg: its good because it gets us closer to our exit criteria
# [10:52] <fantasai> ScribeNick: ChrisL
# [10:52] <Hixie> there, done
# [10:52] <Hixie> the copy on my site is up to date again
# [10:52] <fantasai> Hixie: I'm running into css3-modsel-184a: modulename/number attributes wrong ('css3-modsel-184')
# [10:53] <Hixie> yeah you need to fix the number="" attribute to match the filename
# [10:53] <ChrisL> jd: its a practical matter, allows browsers to fix bugs and check for regression. excellent to catch regressions
# [10:53] <Hixie> number="184a" or whatever
# [10:53] <ChrisL> ... helps maintain a higher level of interoperability
# [10:53] <fantasai> Hixie, ok, making those changes now
# [10:53] <ChrisL> sg: so we run these for imp reports?
# [10:53] <ChrisL> dg: yes
# [10:54] <ChrisL> sg: does it get us to the deadline faster
# [10:54] <ChrisL> db: yes. and new tests always need to be run
# [10:54] <ChrisL> dg: david is asking if this format is acceptable
# [10:55] <ChrisL> cl: this is for css3 as well
# [10:55] <fantasai> Hixie, thanks
# [10:55] <ChrisL> resolved: we accept tests in ref-format as well, as long as they have the existing metadata style
# [10:56] <ChrisL> ae: prefer to have them link to each other in the metadata
# [10:57] <ChrisL> db: manifest file helps in the case of many-to-one links from refs to tests
# [10:57] <ChrisL> ... and they can be concatenated easily
# [10:58] <ChrisL> (break)
# [11:14] * MikeSmith wonders if glazou is around at the moment
# [11:15] <glazou> yes but hold on please
# [11:17] * MikeSmith points glazou to PM
# [11:23] <ChrisL> topic: upcoming meetings
# [11:26] <ChrisL> tpac is 2-3 nov 2009
# [11:26] <ChrisL> sz: are we meeting the sunday as well?
# [11:26] <ChrisL> (no)
# [11:26] <ChrisL> (we look at march 2010)
# [11:27] <ChrisL> db: time for a north american meeting
# [11:27] <ChrisL> cl: www2010 is 26-30 april
# [11:28] <ChrisL> in raleigh
# [11:28] <ChrisL> http://www2010.org/www/
# [11:28] <ChrisL> dg: yes but we need a meeting in between
# [11:30] <ChrisL> (hakon offers oslo in february, to laughter)
# [11:33] <ChrisL> (brainstorming on dates and locations. speculation as to tpac 2010 site and date)
# [11:39] <ChrisL> proposed: bay area in march, several hosting possibilities, easy for peter linss to get to
# [11:39] <ChrisL> dg: after 8 march
# [11:40] <ChrisL> sg: sxsw etc overlaps
# [11:40] <ChrisL> db: mar 12-16
# [11:40] <ChrisL> mh: crazy week, mix right after
# [11:41] <ChrisL> proposed: 22-24 march, bay area
# [11:41] <ChrisL> adobe, mozilla as possible hosts
# [11:43] <jdaggett> proposed: apple hosts
# [11:43] <ChrisL> s/adobe/adobe, apple, microsoft/
# [11:44] <ChrisL> hakon proposes oslo in august
# [11:45] <ChrisL> or june
# [11:45] <ChrisL> hl: the more meetings, the lower the attendance
# [11:47] <ChrisL> 16-18 August 2009, Oslo
# [11:47] <ChrisL> sz: perfer to avoid 16
# [11:47] <ChrisL> 18-20 2010, Oslo
# [11:48] <ChrisL> s/16-18 August 2009, Oslo//
# [11:48] <ChrisL> and then see about tpac
# [11:48] <dbaron> s/18-20 2010/18-20 August 2010/
# [11:49] <ChrisL> topic: role of molly, liaison, use cases, website
# [11:50] <ChrisL> mh: we has jason teague, did a lot of work, and it was put aside and lost momentum
# [11:50] <ChrisL> ... so would like to project manage that to bring to fruition
# [11:50] <ChrisL> ... bert did soem work but we lost the information architecture
# [11:51] <ChrisL> ee: that would be great
# [11:51] <ChrisL> bb: want to keep existing links and names of pages (cool links don't break)
# [11:51] <ChrisL> ... thought i used the structure
# [11:51] <ChrisL> ee: layout but not the information architecture
# [11:52] <ChrisL> bb: public pages, i'm responsible and have to be maintainable
# [11:52] <ChrisL> ... and chris as well
# [11:52] <ChrisL> ... so don't want to learn new tools
# [11:52] <ChrisL> .. have some make scripts, eg for translations
# [11:53] <ChrisL> ... structure, what did I do wrong there?
# [11:53] <Bert> http://www.w3.org/Style/CSS-tmp/
# [11:53] <ChrisL> bb: this is a temporary page and will go away
# [11:54] * Joins: szilles (chatzilla@193.51.208.72)
# [11:54] <ChrisL> ... trimmed out links to other w3c groups
# [11:54] <ChrisL> ... also made top left menu shorter
# [11:55] <ChrisL> ee: news and current work are very long , unstructured. jason and elika design had a structure, not just the page but the whole site.
# [11:55] <ChrisL> ... set up a structure to understand the site. but this is a huge long list
# [11:56] <ChrisL> ee: jasons draft did not have the long lists
# [11:56] <ChrisL> bb: oh, i didn't use his latest work
# [11:56] <ChrisL> .... didn't like it
# [11:57] <ChrisL> ee: propose that we take berts draft and rearrange the content to have the current work in a smaller or secondary page
# [11:57] <dbaron> I just updated http://www.w3.org/Style/Group/meetings.html with "(tentative)" entries for the two meetings we just planned. Somebody else should check I got everything right, though.
# [11:57] <ChrisL> yup, looks good
# [11:58] <ChrisL> mh: needs to be clear and simple with links to further information
# [11:58] <ChrisL> ee; drowned in long list of news items
# [11:58] <ChrisL> sz: keep top 3
# [11:58] <ChrisL> mh: replace current work with an intro, link to more details
# [12:00] <ChrisL> (discussion on whether the design is too big)
# [12:00] <ChrisL> mh: its a current design trend, big and bold
# [12:01] <ChrisL> mh: boxes need to be smaller, to the point. this is designer/developer outreach, not for coders
# [12:01] <ChrisL> ... like richard ishidas site, very clean
# [12:01] <ChrisL> ... this may be a bit over designed
# [12:02] <ChrisL> jd: just needs tghtening to a higher information density
# [12:02] <ChrisL> bb: ok, that would be easy, trimming news items, replacing table with an intro
# [12:02] <ChrisL> ee: little boxes to introduce topics
# [12:03] <ChrisL> ... actual sections, not random links. need to impose a structure
# [12:03] <jdaggett> jdaggett: many thumbs up for this...
# [12:04] <fantasai> ee: and navigation header represents these topics across all subpages
# [12:04] <ChrisL> mh; just presnting the material well. tighten up and match the information to the audience and a consistent navigation scheme throughout
# [12:04] <ChrisL> ee: so I suggest I talk with molly to show bert what we mean
# [12:05] <ChrisL> bb: top bar has three items as well as the home page
# [12:05] <ChrisL> sz; want a quick way to see whats on *this* page
# [12:06] <ChrisL> ... lots below the fold
# [12:06] <ChrisL> cl: maybe tabs to give an overview
# [12:07] <ChrisL> ee: so small boxes, if its short you can see the whole thing at a glance
# [12:07] <ChrisL> mh; good info, bt does not all belong on home page
# [12:07] <ChrisL> ... so elika and i will work on that and i can manage this
# [12:08] <ChrisL> ... people expect more of w3c in terms of usable information
# [12:08] <ChrisL> mh; which brings us to community outreach and liaison
# [12:08] <ChrisL> ... to drive traffic we need attractive resources, then use twitter
# [12:09] <ChrisL> ... its our relationship to the world
# [12:09] <ChrisL> .. fundamental, and missing
# [12:09] <ChrisL> ... social networking can enhance this and I want to work on that. developers want to be more involved, but designers find it hard to track whats going on
# [12:10] <ChrisL> jd; is this really aimed at content developers?
# [12:10] <ChrisL> ... desigers spend a lot of time on edge cases caused by poor interop
# [12:11] <ChrisL> bb: ther is the blog as well
# [12:11] <ChrisL> dg; demo pages
# [12:11] <ChrisL> s/;/:/g
# [12:12] <ChrisL> dg: want to see demo pages for new stuff, with an explanation below. short articles
# [12:12] <ChrisL> mh: showing use of features, best practices
# [12:13] <ChrisL> ... community liaison is what I am best at
# [12:13] <ChrisL> dg: template with container elements
# [12:13] <ChrisL> sz: so what happens if the browser does not implement the feature?
# [12:13] <Bert> http://www.w3.org/Style/Examples/011/firstcss
# [12:13] <Bert> http://www.w3.org/Style/Examples/007/
# [12:14] <ChrisL> mh: understanding of css is still very low. need to teach the current stuff as well as the upcoming stuff
# [12:14] <ChrisL> sz: sure, but want to see a screen cap as well to show what it should look like
# [12:14] <ChrisL> mh: or video
# [12:15] <ChrisL> dg: example, using :target to do tabs
# [12:15] <ChrisL> bb: the links above are some of the most popoular pages
# [12:15] <ChrisL> ... need something between absolute beginners and expert level
# [12:16] <ChrisL> mh: in colleges people are learning products like dreamweaver, not standards. show what they need to know now wnd what is coming later
# [12:16] <ChrisL> jd: we have decided to move modules forward independently so there is no css3
# [12:17] <ChrisL> ... the outside world sees it as a monolithic entity and wonders where it is
# [12:18] <ChrisL> mh: educators need to find a new terminology that is consistent with the module structure
# [12:18] <ChrisL> ... educators and evangelists need materials to work with
# [12:18] <ChrisL> ... its a bunch of pieces, not a versioning system
# [12:20] <ChrisL> cl: key message is the relevance of css 2.1, module s add to it, doesn't throw it all away
# [12:20] <ChrisL> mh: also want to call to the community
# [12:21] <ChrisL> sz: snapshots should replace css3. css3 snapshots, then drop the "3". its whats realistic today
# [12:22] <ChrisL> mh: so all of this, the outfacing site, the comunity liaison - give designers ownership and make them feel part of it
# [12:22] <ChrisL> ee: also we need feedback on the design
# [12:22] <ChrisL> mh: via social networks
# [12:23] <fantasai> s/on the design/from designers/
# [12:23] * ChrisL thanks
# [12:23] <ChrisL> dg: so we all agree to assign this to molly?
# [12:24] <ChrisL> (general agreement)
# [12:24] <ChrisL> bb; how to keep in touch?
# [12:28] <ChrisL> cl; concerns ove rthe group not being as public as the charter says it should be
# [12:30] <ChrisL> jd; one thing is to work out how defined a feature is and to not talk up highly unstable stuff
# [12:30] <fantasai> ChrisL, we try to keep administrivia on the internal list, in general that's the only thing that should be going to the internal list
# [12:30] <fantasai> ChrisL, if technical issues get sent internally, it's an error on the senders part and should be resent to www-style
# [12:31] <ChrisL> (lunch)
# [12:31] <ChrisL> div class="two column hack"
# [12:33] * Quits: jdaggett (jdaggett@193.51.208.72) (Quit: jdaggett)
# [12:33] * Quits: mollydotcom (molly@193.51.208.72) (Quit: mollydotcom)
# [12:33] * Quits: glazou (glazou@193.51.208.72) (Quit: glazou)
# [12:39] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Client exited)
# [12:42] * Joins: billyjackass (MikeSmith@mcclure.w3.org)
# [12:42] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [12:43] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
# [12:43] * Quits: billyjackass (MikeSmith@mcclure.w3.org) (Client exited)
# [12:43] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [12:46] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Client exited)
# [13:03] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
# [13:38] * Joins: glazou (glazou@193.51.208.72)
# [13:38] * Joins: jdaggett (jdaggett@193.51.208.72)
# [13:43] * Joins: mollydotcom (molly@193.51.208.72)
# [13:50] <Arron> scribenick arron
# [13:50] <dbaron> ScribeNick: Arron
# [13:50] <fantasai> http://lists.w3.org/Archives/Public/www-style/2009May/0167.html
# [13:50] <fantasai> http://lists.w3.org/Archives/Public/www-style/2008Aug/0271.html
# [13:51] <Arron> ee: vertical overflow or jsut the last line
# [13:53] <Arron> am: and ellipsis only mase sense on the last line not always in the middle
# [13:55] <Arron> ee: (drawing ellipsis examples)
# [13:55] <Arron> bb: how automatic are the rules for ellipsis
# [13:56] <Arron> cl: what happens when scrolling? does the ellipsis stay with last line?
# [13:56] <Arron> ee: yes
# [13:58] <Arron> db: if its a single line we may need a special case for not clipping
# [13:59] <Arron> ee: do we want to handle both cases for text-overflow vertical and horizontal?
# [13:59] <Arron> do we want to add additional properties
# [14:00] <Arron> mh: what would designers expect and how would it be clipped
# [14:01] <Arron> ee: when there is an ellipsis the text just goes away and is referenced by the ellipsis
# [14:01] * Joins: myakura (myakura@122.29.15.50)
# [14:02] <Arron> Resolved: text overflow in case of vertical overflow still applies to individual lines
# [14:04] <Arron> Topic: Writing desposition of comments after last call
# [14:04] <fantasai> s/desposition/disposition/
# [14:05] <fantasai> Daniel explains color coding
# [14:05] <fantasai> of dispositions of comments
# [14:05] <fantasai> Green means resolved
# [14:06] <fantasai> Orange means deferred
# [14:06] <fantasai> Red means unresolved
# [14:06] <Arron> cl: the idea is a standard for disposition of fomments
# [14:07] <Arron> s/fomments/comments
# [14:07] <fantasai> Anne: I used orange to mean rejected, and red to mean formal objection
# [14:07] * Joins: howcome (howcome@193.51.208.72)
# [14:07] <Arron> cl: one solution is to have two columns
# [14:08] <fantasai> dbaron: For Color I had a separate color for rejected features that were objections
# [14:10] <Arron> db: whoever reads it should define the standards for this
# [14:10] <Arron> cl: lets ask for examples of good practices
# [14:11] <Arron> cl: ask Ian or some of the chairs
# [14:12] <Arron> Action: Daniel to send email asking about standards for color codings and disposition of comments
# [14:12] * trackbot noticed an ACTION. Trying to create it.
# [14:12] * RRSAgent records action 4
# [14:12] <trackbot> Created ACTION-148 - Send email asking about standards for color codings and disposition of comments [on Daniel Glazman - due 2009-06-10].
# [14:13] <fantasai> ScribeNick: fantasai
# [14:13] <fantasai> Topic: Last Call Comments for Multi-Col
# [14:14] <fantasai> howcome: We have three issues
# [14:14] <fantasai> howcome: We have generally agreed to go to last call, but one issue came up, and Alex raised another issue I would like to resolve as well
# [14:14] <fantasai> howcome: The one issue that was left from the Tokyo F2F was about expressing column breaks
# [14:15] <fantasai> howcome: There have been various proposals that were discussed on www-style afterwards
# [14:15] <fantasai> howcome: I put in the proposal I thought we had consensus on in the mailing list
# [14:15] <fantasai> howcome: where we go from having a set of page-break-* properties to using more generic names
# [14:15] <fantasai> howcome: adding new keywords to express column breaking
# [14:16] <fantasai> howcome: This would be an alias, which is something new in CSS
# [14:16] <fantasai> anne has some concerns about expressing this in the DOM
# [14:16] <fantasai> [http://lists.w3.org/Archives/Public/www-style/2009May/0100.html
# [14:17] <fantasai> howcome: other options are to add new properties for columns
# [14:17] <fantasai> howcome: and the resolution from the last f2f was to simply add new keywords to page-break-*
# [14:18] <fantasai> howcome: which would result in e.g. page-break-before: column
# [14:18] <fantasai> http://lists.w3.org/Archives/Public/www-style/2009Apr/0270.html
# [14:18] <anne> the concern is that introducing a new CSS property introduces a new DOM attribute even if you call it an "alias"
# [14:18] <fantasai> http://lists.w3.org/Archives/Public/www-style/2009May/0100.html
# [14:18] <anne> (unless we start doing trickery)
# [14:19] <anne> (and I'm not sure how that'd work, to be clear)
# [14:20] <anne> (arguably you could remove pageBreakBefore from the DOM and obsolete it in favor of breakBefore under the assumption that nobody relies on it anyway)
# [14:22] <fantasai> people were unhappy with page-break-*: column because it's confusing and awkward
# [14:22] <fantasai> howcome: I think creating six new properties for this is overkill
# [14:23] <fantasai> Alex: One of the reasons we didn't like adding column-break before was that not all combinations of column-break and page-break didn't make sense
# [14:23] <fantasai> Alex: now we have arrived at the conclusions that all combinations are sensible, so should be able to provide all
# [14:25] <fantasai> howcome prefers the alias approach, and doesn't think there's enough dom use of page-break properties to block shifting that over
# [14:28] <ChrisL> break: nicely
# [14:30] <fantasai> fantasai summarizes the three proposals in Melinda's email
# [14:30] <fantasai> Molly thinks the shorthand thing makes sense
# [14:30] <fantasai> howcome wants to avoid creating new properties
# [14:33] <fantasai> howcome: anyone object to #2?
# [14:33] <fantasai> Bert objects
# [14:33] <fantasai> Bert: I hate aliases, but I want only one property I want to set.
# [14:36] <fantasai> Bert: break-* is too generic, imo. We have lots of kinds of breaks, e.g. line breaks which are totally unrelated
# [14:38] <fantasai> discussion of whether #3 is an "alias" (where separation is maintained through the system) or a "syntax feature" (which gets resolved at parse time)
# [14:40] <fantasai> Alex: we could also do #2 without the shorthand
# [14:40] * Zakim fantasai, you typed too many words without commas; I suspect you forgot to start with 'to ...'
# [14:41] <ChrisL> zakim, get a grip
# [14:41] <Zakim> I don't understand 'get a grip', ChrisL
# [14:42] <ChrisL> zakim, what hakon is proposing
# [14:42] <Zakim> I don't understand 'what hakon is proposing', ChrisL
# [14:42] <fantasai> Alex: I don't think shorthands are useful or necessary here
# [14:42] <fantasai> some disagreement with that
# [14:42] <fantasai> Steve: Another thing to consider is spreads
# [14:43] <fantasai> fantasai: Melinda suggested adding 'avoid-turn' to 'page-break-*'
# [14:45] <fantasai> Arron: I think #2 is easier to understand
# [14:45] * Quits: glazou (glazou@193.51.208.72) (Quit: glazou)
# [14:46] <fantasai> Molly: #3 is freer because it's not dependent on the media
# [14:49] <fantasai> fantasai: If I have a multicolumn layout on pages, I can say that page breaks are just as bad as column breaks and both should be equally avoided
# [14:49] <fantasai> fantasai: Or I can say that page breaks are worse than column breaks, and I want to avoid column breaks, but even more than that I want to avoid page breaks
# [14:51] <fantasai> fantasai: So I may wind up skipping columns in order to keep things on one page
# [14:51] <fantasai> fantasai: How do I express these as two distinct possibilities?
# [14:53] <fantasai> RESOLVED: #3 -- page-break-* as syntactic suga
# [14:53] * dbaron wonders who will propose "coffee-break-before: continuing-discussion" :-)
# [14:53] <fantasai> r
# [14:54] <fantasai> howcome: Alex suggested taking out column-span
# [14:54] * Joins: glazou (glazou@193.51.208.72)
# [14:54] <anne> we can now introduce 'colour' with this as precedent :)
# [14:54] * Bert notices we don't have an excuse anymore now to refuse people the 'colour' property alias...
# [14:54] <fantasai> howcome: He thinks we can express this in other properties
# [14:54] <fantasai> Alex: It's weird that it takes the values '1' and 'all'
# [14:57] <fantasai> howcome: Alex is saying that we don't need this, you can just put extra <div>s around the content before and after the spanning element
# [14:58] <fantasai> fantasai: If you want an image to span multiple columns what are you going to do, put <div class="before-image"> and <div class="after-image"> around the content before/after the image?
# [14:59] <ChrisL> this requires some ugly presentational markup; i don't like forcing authors to do this
# [15:03] <fantasai> discussion of column-spanning and nested multicol elements
# [15:04] <fantasai> Chris: Can you do column-span: 2 in a 3-column layout?
# [15:04] <fantasai> Yes, this feature was there before but was hard to define/implement so we're starting with column-span: 1 | all
# [15:05] <fantasai> Alex: I'll have to take away my statement that this can be done with other things.
# [15:05] <Bert> Chris: Maybe call '1' 'one' instead, to avoid that people expect '2' to work?
# [15:07] <fantasai> Someone asks what happens if there's a float that's wider than the column
# [15:07] <fantasai> it overflows the column
# [15:08] <fantasai> and affects adjacent columns
# [15:08] <fantasai> fantasai: Does it affect previous columns, or only subsequent ones?
# [15:12] * ChrisL break-before: consensus
# [15:12] <fantasai> discussion of this issue
# [15:13] <fantasai> floats that affect previous columns are complicated to implement, it requires multiple passes
# [15:13] * Bert : Hmm, Håkon moved the draft without making a redirect :-(
# [15:14] <fantasai> floats that affect subsequent columns are straightforward
# [15:17] <fantasai> RESOLVED: howcome to add an example of a float intruding into previous columns and we wait for implementors to complain
# [15:18] <fantasai> Sylvain: There's also an issue on the pseudo-algorithm
# [15:41] <sylvaing> http://lists.w3.org/Archives/Public/www-style/2009Jun/0009.html
# [15:42] <sylvaing> and summarized here to try and make it more readable: http://lists.w3.org/Archives/Public/www-style/2009Jun/0046.html
# [15:42] <fantasai> howcome: Adding line numbers is easy
# [15:42] <glazou> Bert is playing Simon game with the conf-call hardware
# [15:43] <fantasai> howcome: The hard one is the shrink-to-fit one
# [15:44] <dbaron> http://dbaron.org/css/intrinsic/ has some work on defining the shrink-to-fit algorithm
# [15:44] <fantasai> howcome: we could point to the shrink-to-fit algorithm, but we can't define it here
# [15:46] <fantasai> Bert reviews the proposed changes
# [15:52] <fantasai> RESOLVED: accepted to fix
# [15:58] <fantasai> Topic: Abandoned Working Drafts
# [15:58] <fantasai> ScribeNick: alexmog
# [15:58] <alexmog> ScribeNick:alexmog
# [15:58] <alexmog> discussing mathml
# [15:58] <alexmog> RESOLVED: css math -- dropped
# [15:59] <alexmog> anne: what does dropping mean?
# [15:59] <alexmog> daniel: another group takes over
# [16:00] <alexmog> CSS style Attribute syntax 3
# [16:00] <alexmog> chris: scoping is still needed?
# [16:01] <alexmog> discusing scope, how it is related to HTML5
# [16:01] <alexmog> anne: HTML5 allows more, media independent style sheets, etc.
# [16:02] <alexmog> david: suggest dropping this spec but publish what needs to be specified elswhere
# [16:03] <alexmog> RESOLVED: drop "style attribute syntax" spec
# [16:04] <alexmog> RESOLVED: keep "style attribute syntax" spec, remove extensions, only keep current syntax
# [16:04] <alexmog> ACTION: fantasai: edit "style attribute syntax" to constrain to current syntax
# [16:04] * trackbot noticed an ACTION. Trying to create it.
# [16:04] * RRSAgent records action 5
# [16:04] <trackbot> Created ACTION-149 - Edit "style attribute syntax" to constrain to current syntax [on Elika Etemad - due 2009-06-10].
# [16:05] <alexmog> CSS Hyperlink
# [16:06] <alexmog> CSS Hyperlink Presentation Module
# [16:08] <alexmog> daniel: reason for the spec is to allow to overide link behavior from user style sheet
# [16:08] <alexmog> the behavior is now available via DOM
# [16:10] <alexmog> browser vendors don't express interest in implementing it
# [16:11] <alexmog> RESOLVED: drop Hyperlink Presentation module
# [16:12] <alexmog> CSS Web Fonts Level 3
# [16:12] <alexmog> merged with CSS3 Fonts -- links should be redirected to the merged spec
# [16:12] <alexmog> CSS Introduction
# [16:13] <alexmog> RESOLVED: snapshot will override; when snapshot is published, introduction link will point to the snapshot
# [16:14] <alexmog> CSS Reader Media type
# [16:14] <alexmog> already dropped, should not be in current work
# [16:15] <alexmog> RESOLVED: publish a note on not working on CSS Reader Media Type
# [16:15] <alexmog> CSS OM View
# [16:16] <alexmog> Anne is working on the spec, it is meant to obsolete DOM spec
# [16:17] <alexmog> status -- in WD for over the year
# [16:17] <alexmog> anne: time to publish a new WD
# [16:17] <alexmog> RESOLVED: publish a new working draft on CSS OM View
# [16:18] <alexmog> anne: have requests for support of 3D transforms
# [16:18] <alexmog> RESOLVED: Aural stylesheets - dropped
# [16:19] <alexmog> CSS Lists
# [16:19] <alexmog> fantasai: should not be dropped
# [16:19] <alexmog> CSS Scoping
# [16:19] <alexmog> daniel is the editor
# [16:20] <alexmog> daniel: the idea was to suggest a way to scope stylesheets to an element; HTML5 has scoping support, this spec is not needed
# [16:22] <alexmog> RESOLVED: CSS Scoping is droppped
# [16:23] <alexmog> CSS Ruby
# [16:24] <alexmog> IE has partial implementation
# [16:24] <alexmog> Action:Arron to send a list of CSS Ruby properties supported by IE8
# [16:24] * RRSAgent records action 6
# [16:27] <alexmog> RESOLVED: Ruby spec is on hold until an editor is found
# [16:29] <alexmog> CSS Object Model
# [16:29] <alexmog> no working draft yet
# [16:30] <alexmog> anne: huge project, no time currently
# [16:31] <alexmog> RESOLVED: CSS Object Model -- not dropped, abandoned for the time being
# [16:31] <alexmog> CSS Presentation Levels
# [16:31] <alexmog> Hakon: let's drop it. it's going nowhere.
# [16:33] <alexmog> RESOLVED: CSS Presentation Level -- not being worked on for undetermined time
# [16:36] <alexmog> discuss the difference between dropped, abandoned and on hold
# [16:43] <alexmog> discussing keeping documents on low-priority, off-charter list vs. completely removing documents and saying we are not working on it any more
# [16:53] * Quits: szilles (chatzilla@193.51.208.72) (Ping timeout)
# [16:54] * glazou summons dsinger
# [16:58] <alexmog> RESOLVED: CSS Presentation Level -- discontinue, publish a note that contains the whold content of current document
# [16:58] <alexmog> s/whold/whole/g
# [17:08] <sylvaing> scribenick:sylvaing
# [17:08] <fantasai> http://www.css3.info/border-image-issues/
# [17:08] <sylvaing> topic: border-image feedback
# [17:08] <fantasai> Second issue
# [17:08] <sylvaing> comments were requested on issue #2
# [17:08] <fantasai> border-image: url(...) 20% 40% / 10% 4em 20% / 0 1em;
# [17:08] <sylvaing> i.e. syntax is arcane
# [17:08] <sylvaing> someone suggested splitting into multiple props; helps JS manipulation....
# [17:09] <sylvaing> ..or :hover selector
# [17:09] <sylvaing> many other responders expressed support for this idea
# [17:09] <sylvaing> (all above was fantasai)
# [17:10] <sylvaing> chrisl: even if we add properties we should preserve the current syntax since it has been implemented, even if behind a vendor prefix
# [17:10] <sylvaing> fantasai: yes, absolutely, the shorthand syntax remains
# [17:10] <sylvaing> fantasai: it does create more properties but people find it simpler and like the flexibility
# [17:12] * Quits: ChrisL (ChrisL@128.30.52.30) (Ping timeout)
# [17:12] <sylvaing> fantasai displays second issue from http://www.css3.info/border-image-issues/
# [17:13] <sylvaing> (comparing split example against border-image property definition...)
# [17:16] <sylvaing> hakon: does border-image-outset change the size of the boxes ?
# [17:17] <sylvaing> fantasai: no
# [17:17] * Joins: dsinger (mobile@67.218.105.95)
# [17:17] <dsinger> Hi. Thx for the call.
# [17:18] <sylvaing> chrisl: can outset values be negative to make insets ?
# [17:18] <sylvaing> fantasai: no
# [17:19] <dbaron> I'm not crazy about separating border-image-slice from border-image-source.
# [17:19] <dbaron> (And there was agreement that border-image-widths should be border-image-width.)
# [17:20] * dsinger is there background reading on iptv (other than bert's email) i should do?
# [17:20] * sylvaing thanks, David
# [17:21] <sylvaing> fantasai explains that border-image is a painting effect i.e. it does not affect the size of the border box
# [17:21] <sylvaing> annevk: optimizing for the case where the image cannot be loaded seems wrong
# [17:21] <sylvaing> chrisl: it's not an optimization. you also want to avoid layout flicker when the image resource loads slowly
# [17:22] <sylvaing> bert: not sure we need the complexity of outset
# [17:22] <sylvaing> fantasai and chrisl disagree
# [17:22] <sylvaing> fantasai: any objections to splitting border-image ?
# [17:23] <sylvaing> bert: not to the principle but to the naming
# [17:25] <sylvaing> fantasai: so we drop the plural on border-image-width. anything else ?
# [17:26] <fantasai> add border-image-repeat for the keywords
# [17:26] <Zakim> ChrisL, you asked to be reminded at this time to go home
# [17:29] <sylvaing> discussing the default for border-image-repeat: tile or stretch ?
# [17:30] <sylvaing> dbaron: we might want to leave this open for now
# [17:31] <fantasai> Mark border-image-repeat name as an open issue
# [17:32] <sylvaing> RESOLVED: border-image property split proposal is accepted
# [17:33] <sylvaing> glazou declares an end to the hostilities
# [17:33] * Bert to dsinger: AFAIK, my e-mail is the only material on IPTV so far (plus the document I linked to.
# [17:34] * dsinger thx Bert. Congrats on cess. of hostil
# [17:36] * Quits: dsinger (mobile@67.218.105.95) (Quit: Rooms • iPhone IRC Client • http://rooms.derflash.de)
# [17:37] * Quits: glazou (glazou@193.51.208.72) (Quit: glazou)
# [17:37] * Quits: jdaggett (jdaggett@193.51.208.72) (Quit: jdaggett)
# [17:37] * Quits: sylvaing (sylvaing@193.51.208.72) (Quit: sylvaing)
# [17:37] * Quits: mollydotcom (molly@193.51.208.72) (Quit: mollydotcom)
# [17:39] * Quits: alexmog (alexmog@193.51.208.72) (Ping timeout)
# [17:40] * Quits: Arron (arronei@193.51.208.72) (Ping timeout)
# [17:40] * Quits: dbaron (dbaron@193.51.208.72) (Ping timeout)
# [17:40] * Quits: howcome (howcome@193.51.208.72) (Ping timeout)
# [17:46] * Joins: mollydotcom (molly@193.51.208.72)
# [17:50] * Zakim excuses himself; his presence no longer seems to be needed
# [17:50] * Parts: Zakim (rrs-bridgg@128.30.52.30)
# [17:53] * Quits: mollydotcom (molly@193.51.208.72) (Ping timeout)
# [18:08] * Joins: Arron (arronei@90.52.74.83)
# [18:25] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
# [18:47] * Joins: dbaron (dbaron@93.10.129.8)
# [19:04] * Quits: Arron (arronei@90.52.74.83) (Ping timeout)
# [19:20] * Joins: Arron (arronei@90.52.74.83)
# [19:29] * Joins: jdaggett (jdaggett@82.242.111.184)
# [20:02] * Quits: Arron (arronei@90.52.74.83) (Ping timeout)
# [20:36] * Quits: dbaron (dbaron@93.10.129.8) (Quit: 8403864 bytes have been tenured, next gc will be global.)
# [21:55] * Joins: Arron (arronei@90.41.159.61)
# [22:06] * Quits: Arron (arronei@90.41.159.61) (Ping timeout)
# [22:07] * Joins: annevk (opera@80.13.73.211)
# [23:17] * Quits: annevk (opera@80.13.73.211) (Quit: annevk)
# Session Close: Thu Jun 04 00:00:00 2009

The end :)