Options:
- # Session Start: Wed Apr 18 00:00:01 2012
- # Session Ident: #css
- # [00:02] <fantasai> kennyluck: still working through your other issues, so you've got us busy for awhile yet ;)
- # [00:05] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [00:06] * Joins: arno (arno@192.150.10.200)
- # [00:13] * Joins: krit (Adium@192.150.10.201)
- # [00:24] <krit> plinss: btw.According to the model at http://wiki.csswg.org/test/css2.1/review#process the new mode for reviews on shepherd should be called "Accepted".
- # [00:24] <plinss> fantasai: ping
- # [00:28] <plinss> krit: thanks, working on adding it now
- # [00:28] <krit> plinss: thanks :)
- # [00:28] <plinss> np
- # [00:56] * miketaylr is now known as miketaylr|
- # [00:56] * miketaylr| is now known as miketaylr||
- # [01:06] * Joins: jet (jet@203.63.65.169)
- # [01:16] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [01:17] <kennyluck> fantasai, I think I am finally done with all my V&U issues.
- # [01:17] * kennyluck is going to sleep now
- # [01:33] * Joins: arno (arno@192.150.10.200)
- # [01:36] * Joins: krit1 (Adium@192.150.10.201)
- # [01:36] * Quits: krit (Adium@192.150.10.201) (Connection reset by peer)
- # [01:36] * Joins: krit (Adium@192.150.10.201)
- # [01:36] * Quits: krit1 (Adium@192.150.10.201) (Connection reset by peer)
- # [01:41] * Quits: tantek (tantek@70.36.139.112) (Quit: tantek)
- # [01:42] * Quits: miketaylr|| (miketaylr@70.112.101.224) (Quit: Leaving...)
- # [01:43] * Quits: drublic (drublic@77.2.135.236) (Client exited)
- # [01:44] <krit> plinss: ping
- # [01:44] <plinss> krit: pong
- # [01:45] <krit> plinss: I would like to try the script from https://lists.w3.org/Archives/Member/w3c-css-wg/2011AprJun/0164.html Is it supposed to still work?
- # [01:45] <krit> plinss: I'd like to test it on CSS Transforms
- # [01:45] <plinss> looking
- # [01:45] <plinss> yes, it still works
- # [01:46] <plinss> you just need to add the proper hashtag for your test suite: CSS3-TRANSFORMS_DEV
- # [01:46] <plinss> (to the script link in your spec)
- # [01:46] <krit> plinss: should it work locally as well?
- # [01:46] <plinss> yes
- # [01:47] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # [01:47] * Joins: jet (jet@203.63.65.169)
- # [01:48] <krit> plinss: <html><body><p><strong>NOTICE: </strong>Not a valid specification url</p></body></html>
- # [01:49] <plinss> where do you get that from?
- # [01:49] <krit> plinss: http://test.csswg.org/harness/status.php?s=CSS3-TRANSFORMS_DEV&x=file%3A%2F%2F%2FUsers%2Fdschulze%2FDocuments%2Fhg%2Fcsswg%2Fcss3-transforms%2FOverview.html
- # [01:49] <krit> GET http://test.csswg.org/harness/status.php?s=CSS3-TRANSFORMS_DEV&x=file%3A%2F%2F%2FUsers%2Fdschulze%2FDocuments%2Fhg%2Fcsswg%2Fcss3-transforms%2FOverview.html 400 (Bad Request)
- # [01:49] <krit> plinss: that is the response from the server
- # [01:49] <plinss> where did that url come from?
- # [01:50] <krit> plinss: I embedded the scipt like described in the post
- # [01:50] <krit> plinss: that is the result on the web console
- # [01:50] <krit> plinss: <script src='http://test.csswg.org/harness/annotate.js#CSS3-TRANSFORMS_DEV' type='text/javascript' defer></script>
- # [01:51] <plinss> hang on, let me try locally
- # [01:51] <fantasai> plinss: pong
- # [01:52] <plinss> fantasai: I was wondering what level of access setting 'accepted' should be restricted to
- # [01:52] <plinss> currently is anyone who can commit changes...
- # [01:52] <krit> plinss: that is also what the wiki says. Everyone
- # [01:53] <krit> plinss: "Anyone with the ability to read and understand the http://www.w3.org/Style/CSS/Specs/ and a thorough understanding of the http://www.w3.org/Style/CSS/Test/guidelines.html can review additions and changes to the Approved collection."
- # [01:53] <plinss> the question is, _everyone_ or just those who have the right to insert reviewer links
- # [01:54] <plinss> or should we have another level of rights between public and committer
- # [01:55] <plinss> krit: anyone can review and make comments in Shepherd, the question is, who can set status to accepted
- # [01:55] <krit> hm, also right
- # [01:55] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [01:55] <fantasai> plinss: I'll bias to everyone
- # [01:55] <fantasai> plinss: that's why we have the approver role
- # [01:56] * Joins: arno (arno@192.150.10.200)
- # [01:56] <plinss> fantasai: but there's an implication that someone accepting a test can insert a reviewer link
- # [01:56] <plinss> and not everyone can do that
- # [01:56] <fantasai> plinss: should be able to yes
- # [01:56] <fantasai> plinss: no?
- # [01:56] <plinss> we don't have public push access
- # [01:56] <plinss> to the repo
- # [01:57] <fantasai> plinss: oh, right. All committers, then
- # [01:57] <plinss> eventually there will be a web UI to insert reviewer links, but then Shepherd will be modifying the test, so there should still be a restriction to committers...
- # [01:57] <plinss> I think
- # [01:58] <plinss> krit: reload your spec now
- # [01:59] <krit> plinss: works!
- # [01:59] <krit> plinss: Thanks a lot!
- # [01:59] <plinss> krit: I just needed to set the Overview.html home page on the spec setup in the harness
- # [01:59] <plinss> glad it works
- # [02:05] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [02:08] * Joins: jdaggett_ (jdaggett@202.221.217.77)
- # [02:08] * Quits: jdaggett (jdaggett@202.221.217.73) (Ping timeout)
- # [02:08] * jdaggett_ is now known as jdaggett
- # [02:41] <plinss> krit: Shepherd now has 'accepted' status
- # [02:41] <plinss> when you add a reviewer link, it auto changes the status
- # [02:41] <krit> plinss: Great! That is awesome!
- # [02:42] <plinss> krit: np
- # [02:42] <plinss> I made a trivial edit to the files you already reviewed so Shepherd updated them already
- # [02:43] <krit> plinss: what happens if the Owner denies the patch and sets the state to "Needs work" and the author just uploads a simple change. Will the status change to "Accepted" automatically, since the reviewer link is on the test?
- # [02:43] <plinss> no the link only has an effect the first time Shepherd sees it
- # [02:43] <krit> plinss: In this case it should stay at Awaiting review, no?
- # [02:44] <krit> plinss: ok, that means on the second review I just set the flag in shepherd
- # [02:44] <krit> plinss: that is great
- # [02:44] <plinss> right, or add another reviewer link
- # [02:44] <krit> plinss: really awesome!
- # [02:45] <plinss> note that if you review and find issues, you need to file the issue as a comment in Shepherd _after_ you push the reviewer link and manually set the status to 'needs work'
- # [02:45] <plinss> or simply don't put the reviewer link in until you accept the test, just file issues directly in Shepherd
- # [02:45] <krit> plinss: yes, I think that is what the wiki recommands anyway
- # [02:46] <krit> plinss: http://test.csswg.org/shepherd/search/spec/CSS3-TRANSFORMS/status/accepted/ it works! :)
- # [02:46] <plinss> Shepherd already had all the reviewer link functionality, it just only worked for those that had approval rights and set the status to 'approved'
- # [02:46] <plinss> it was fairly simple to hook in the accepted state
- # [02:46] <krit> plinss: so it was a change in the rights managment :)
- # [02:47] <plinss> sort of, mostly adding the new status level
- # [02:47] <plinss> also, approvers now get a link on the home page to tests in the 'accepted' state stating 'Awaiting Approval'
- # [02:52] * Quits: jdaggett (jdaggett@202.221.217.77) (Quit: jdaggett)
- # [02:55] <krit> plinss: great. So tests do not get forgotten. Thanks a lot for the fast investigation.
- # [02:56] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [02:56] <plinss> krit: no problem
- # [02:58] * Quits: krit (Adium@192.150.10.201) (Quit: Leaving.)
- # [03:02] <fantasai> plinss++ :)
- # [03:04] <plinss> fantasai: nows there's more links for you to put into your home page mockup :-)
- # [03:21] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [03:22] * sylvaing is now known as sylvaing_away
- # [03:44] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # [03:44] * Joins: jet (jet@203.63.65.169)
- # [04:08] <fantasai> plinss: heh
- # [04:14] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [04:14] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [05:32] * Joins: tantek (tantek@208.54.5.129)
- # [05:41] * Quits: tantek (tantek@208.54.5.129) (Quit: tantek)
- # [05:48] * Joins: asdf (d572924d@109.169.29.95)
- # [05:51] * Quits: asdf (d572924d@109.169.29.95) (Quit: http://www.mibbit.com ajax IRC Client)
- # [05:56] * Joins: krit (Adium@24.6.231.253)
- # [07:48] * Quits: glenn (gadams@174.29.126.28) (Client exited)
- # [07:55] * Quits: krit (Adium@24.6.231.253) (Quit: Leaving.)
- # [09:33] * Joins: jarek (jarek@79.186.14.128)
- # [09:37] * Quits: kennyluck (kennyluck@114.25.246.110) (Quit: kennyluck)
- # [09:38] * Joins: kennyluck (kennyluck@114.25.246.110)
- # [10:10] * Joins: SimonSapin (simon@82.232.219.95)
- # [10:16] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [10:17] * Quits: jarek (jarek@79.186.14.128) (Quit: jarek)
- # [10:52] * Joins: drublic (drublic@93.132.253.242)
- # [10:54] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # [13:01] * Joins: Ms2ger (Ms2ger@157.193.9.65)
- # [13:01] * Joins: jet (jet@203.63.65.169)
- # [13:03] * Quits: drublic (drublic@93.132.253.242) (Client exited)
- # [13:04] * Joins: drublic (drublic@93.132.253.242)
- # [13:17] * Joins: florianr (florianr@213.236.208.22)
- # [13:56] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # [14:00] * Joins: jet (jet@203.63.65.169)
- # [14:29] * Quits: Ms2ger (Ms2ger@157.193.9.65) (Ping timeout)
- # [15:13] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # [15:43] * Quits: leaverou (leaverou@67.180.84.179) (Ping timeout)
- # [15:46] * Joins: krit (Adium@24.6.231.253)
- # [16:26] * Joins: ksweeney (ksweeney@63.119.10.10)
- # [16:32] * Quits: krit (Adium@24.6.231.253) (Quit: Leaving.)
- # [17:13] * Joins: Ms2ger (Ms2ger@91.181.73.47)
- # [17:41] * sylvaing_away is now known as sylvaing
- # [17:45] * Joins: tantek (tantek@76.115.51.221)
- # [17:51] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [17:51] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
- # [17:51] <RRSAgent> logging to http://www.w3.org/2012/04/18-css-irc
- # [17:51] <plinss> zakim, this will be style
- # [17:51] <Zakim> ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 16 minutes
- # [17:51] <plinss> rrsagent, make logs public
- # [17:51] <RRSAgent> I have made the request, plinss
- # [18:01] <Zakim> Style_CSS FP()12:00PM has now started
- # [18:02] <Zakim> +??P2
- # [18:02] <florianr> Zakim, I am ??P2
- # [18:02] <Zakim> +florianr; got it
- # [18:02] * Joins: glazou (glazou@85.168.27.11)
- # [18:02] <Zakim> +plinss
- # [18:03] <Zakim> +??P0
- # [18:03] * Joins: oyvind (oyvinds@213.236.208.22)
- # [18:04] <glazou> Zakim, ??P0 is me
- # [18:04] <Zakim> +glazou; got it
- # [18:04] * Quits: arronei (arronei@131.107.192.154) (Quit: arronei)
- # [18:05] * Joins: smfr (smfr@173.228.90.231)
- # [18:06] * Joins: antonp (50a94e63@109.169.29.95)
- # [18:06] <Zakim> +sylvaing
- # [18:06] * Joins: dstorey (Adium@67.180.84.179)
- # [18:06] * Joins: arronei (arronei@131.107.192.154)
- # [18:07] <Zakim> +hober
- # [18:07] <Zakim> +smfr
- # [18:07] <Zakim> +stearns
- # [18:08] <Zakim> +[Microsoft]
- # [18:08] <Zakim> +[Microsoft.a]
- # [18:08] <arronei> zakim, microsoft has me
- # [18:08] <Zakim> +arronei; got it
- # [18:08] * Joins: JohnJansen (qw3birc@128.30.52.28)
- # [18:08] <Zakim> +antonp
- # [18:08] * Quits: smfr (smfr@173.228.90.231) (Ping timeout)
- # [18:09] <tantek> good morning
- # [18:10] <Zakim> + +1.415.308.aaaa
- # [18:10] <Zakim> +??P62
- # [18:10] * Joins: bradk (bradk@99.7.175.117)
- # [18:10] <Zakim> + +1.650.275.aabb
- # [18:10] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [18:10] <bradk> Zakim, aabb is me
- # [18:10] <Zakim> +bradk; got it
- # [18:11] <JohnJansen> Zakim, Microsoft has JohnJansen
- # [18:11] <Zakim> +JohnJansen; got it
- # [18:11] <Zakim> + +1.415.832.aacc
- # [18:11] <vhardy_> Zakim, aacc is me
- # [18:11] <Zakim> +vhardy_; got it
- # [18:11] <stearns> Zakim, aaaa is krit
- # [18:11] <Zakim> +krit; got it
- # [18:11] <plinss> zakim, ?P62 is fantasai
- # [18:11] <Zakim> sorry, plinss, I do not recognize a party named '?P62'
- # [18:12] <plinss> zakim, P62 is fantasai
- # [18:12] <Zakim> sorry, plinss, I do not recognize a party named 'P62'
- # [18:12] <plinss> zakim, who is here?
- # [18:12] <Zakim> On the phone I see florianr, plinss, glazou, sylvaing, hober, smfr, stearns, [Microsoft], [Microsoft.a], antonp, krit, ??P62, bradk, vhardy_
- # [18:12] <Zakim> [Microsoft] has JohnJansen
- # [18:12] <Zakim> On IRC I see vhardy_, bradk, JohnJansen, arronei, dstorey, antonp, oyvind, glazou, RRSAgent, Zakim, tantek, Ms2ger, ksweeney, florianr, drublic, SimonSapin, kennyluck, logbot,
- # [18:12] <Zakim> ... paul___irish, ed, krijnh, Echoes, fantasai, stearns, shepazu, TabAtkins_, hober, Liam, isherman, kojiishi, gsnedders, danielfilho, CSSWG_LogBot, vhardy, sylvaing, plinss,
- # [18:12] <Zakim> ... alexmog, shans, pjrm, Hixie, Bert, trackbot
- # [18:12] <fantasai> ScribeNick: fantasai
- # [18:13] <fantasai> Florian: Wanted to add new editors to CSS Device Adaptation
- # [18:13] <florianr> https://lists.w3.org/Archives/Member/w3c-css-wg/2012AprJun/0073.html
- # [18:13] * Joins: nimbu (Adium@192.150.10.201)
- # [18:13] <fantasai> Vincent: We're looking internally to see if someone might be able to join as well
- # [18:13] <fantasai> plinss: Please take time to add agenda topics to Hamburg wiki
- # [18:14] <fantasai> plinss: And some of those there are vague; please add more detail
- # [18:14] <fantasai> plinss: One issue left on margin collapsing?
- # [18:14] * Joins: smfr (smfr@173.228.90.231)
- # [18:14] <fantasai> antonp: I'd like to work on other 2.1 issues than that one
- # [18:14] <fantasai> antonp: so let's postpone, and for next week I'll try to prepare some other ones
- # [18:14] <fantasai> plinss: Ok, ping me when it's ready
- # [18:14] * Joins: alexmog_ (qw3birc@128.30.52.28)
- # [18:15] <alexmog_> zakim, microsoft has me
- # [18:15] <Zakim> +alexmog_; got it
- # [18:15] <fantasai> Florian: Current editor for CSS Device Adaptation is going on paternity leave, so we're proposing two new editors from Opera myself and ?
- # [18:15] <Zakim> + +47.21.65.aadd
- # [18:15] <Zakim> +??P80
- # [18:15] <fantasai> Florian: We also invite people from other vendors to join, help us move this forward
- # [18:15] <florianr> s/?/Øyvind Stenhaug/
- # [18:15] <dstorey> zakim, ??P80 is me
- # [18:15] <Zakim> +dstorey; got it
- # [18:15] <Zakim> +??P83
- # [18:16] <fantasai> Vincent: What's the status of this module?
- # [18:16] <fantasai> Florian: Some open issues, and some editorial work
- # [18:16] <fantasai> Florian: Don't think there is a public test suite
- # [18:16] * Joins: howcome (howcome@88.89.78.85)
- # [18:16] <fantasai> Sylvain: We have a partial implementation, might provide feedback soon
- # [18:16] <fantasai> Florian: Would be much appreciated
- # [18:17] <fantasai> Florian: Noticed you only implemented part of the spec, want to know if that's because you haven't done it yet or thought better to not implement it.
- # [18:17] <fantasai> Sylvain: Mostly we don't have it yet
- # [18:17] <fantasai> RESOLVED: Add new editors from Opera to Device Adaptation
- # [18:17] <stearns> list intro: http://lists.w3.org/Archives/Public/www-style/2012Apr/0278.html
- # [18:17] <fantasai> Topic: CSS Regions
- # [18:17] <stearns> ED section: http://dev.w3.org/csswg/css3-regions/#regions-visual-formatting-details
- # [18:18] <fantasai> stearns: Added new sections to Regions to handle auto-height regions
- # [18:18] <fantasai> stearns: We've been validating this in code in a WebKit branch, making sure what we have there is implementable
- # [18:18] <fantasai> stearns: would like people to take a look and give us some feedback
- # [18:18] <fantasai> stearns: that's all
- # [18:19] <fantasai> howcome: I went through it, and I find it hard to read/understand/comprehend that part
- # [18:19] <fantasai> howcome: It may be right, but I find it hard to review and relate to the regions spec
- # [18:19] <fantasai> howcome: when the #1 concern that I and others have raised is not addressed yet
- # [18:19] <fantasai> howcome: I would have preferred if that hurdle could be passed.
- # [18:19] <fantasai> howcome: Right now, it doesn't seem like this should be something to work on
- # [18:20] <fantasai> stearns: It's definitely something we're working o
- # [18:20] <Zakim> +[Microsoft.aa]
- # [18:20] <fantasai> stearns: what you do with the regions box is not related to how you size it
- # [18:20] <fantasai> stearns: we want the sizing algorithm independent of where the box comes from
- # [18:20] <fantasai> stearns: I agree we need to address box generation
- # [18:20] <Zakim> +TabAtkins
- # [18:20] <fantasai> stearns: don't know that that issue gates auto-sizing regions
- # [18:20] * Joins: Katie (qw3birc@128.30.52.28)
- # [18:20] <glazou> q+
- # [18:20] * Zakim sees glazou on the speaker queue
- # [18:21] * Joins: ChrisL (ChrisL@128.30.52.169)
- # [18:21] <fantasai> howcome: I agree they may be independent, but there's not much motivation to review the spec when this hurdle remains in the way
- # [18:21] <sylvaing> didn't we agree to address this as part of the template work in Paris?
- # [18:21] <fantasai> Vincent: We are working on page templates, syntax for generating regions
- # [18:21] <fantasai> Vincent: We're trying to address the big issues you and others have raised; auto-sizing was one of those issues
- # [18:21] <fantasai> Vincent: We're not ignoring the other issues
- # [18:21] <Katie> zakim, who's on the call?
- # [18:21] <Zakim> On the phone I see florianr, plinss, glazou, sylvaing, hober, smfr, stearns, [Microsoft], [Microsoft.a], antonp, krit, ??P62, bradk, vhardy_, +47.21.65.aadd, dstorey, ??P83,
- # [18:21] * tantek is on IRC only for this meeting.
- # [18:21] <Zakim> ... [Microsoft.aa], TabAtkins
- # [18:21] <Zakim> [Microsoft] has alexmog_
- # [18:21] <Zakim> +ChrisL
- # [18:22] <plinss> ack glazou
- # [18:22] * Zakim sees no one on the speaker queue
- # [18:22] <fantasai> glazou: I reviewed document with a fresh eye
- # [18:22] <fantasai> glazou: I did not find it hard to read or understand
- # [18:22] <fantasai> glazou: I found it pretty easy to read and understand
- # [18:22] <fantasai> glazou: The thing I originally missed, and discovered rereading it
- # [18:22] <fantasai> glazou: Is that generating boxes is completely independent of notion of regions
- # [18:22] <Katie> zakim, [Microsoft.a] is Katie
- # [18:22] <Zakim> +Katie; got it
- # [18:22] <fantasai> glazou: Explanation in Section 7 is needed to explain how regions work
- # [18:22] <fantasai> glazou: could be independent of generation of boxes
- # [18:23] <fantasai> glazou: We might need for other things in CSS
- # [18:23] <fantasai> glazou: Without that, document is not understandable as a whole
- # [18:23] <glazou> Zakim, ack me
- # [18:23] <Zakim> I see no one on the speaker queue
- # [18:23] * Joins: arno (arno@192.150.10.200)
- # [18:23] <fantasai> antonp: I found it hard to get on the first read through. What could help is if someone maybe posts a summary of what's going on in Section 7, to orient the reader a bit?
- # [18:24] <Zakim> -bradk
- # [18:25] <Zakim> +bradk
- # [18:25] <fantasai> stearns: maybe I'll post an outline of the section to the list
- # [18:25] <fantasai> bradk: I thought Section 7 was easy to understand, esp with examples
- # [18:26] <fantasai> bradk: What was hard for me, doesn't have an exact definition of "fragment"
- # [18:26] <fantasai> bradk: There's no terminology section
- # [18:26] <fantasai> bradk: Afraid it might mean different things in different parts of the document
- # [18:26] <fantasai> Vincent: Referencing CSS3 Fragmentation Spec
- # [18:26] <fantasai> stearns: I think I have a task to go through the document and make sure we have all relevant spec links
- # [18:26] <fantasai> stearns: We should have more links to css3-break
- # [18:27] <fantasai> bradk: Fragmentation spec talks about portions that occur between breaking opportunities, right?
- # [18:27] <fantasai> bradk: Seemed like in some parts it meant something different, like portion of element that's within the region box or something like that
- # [18:27] <fantasai> bradk: Want to make sure it's consistent
- # [18:27] <fantasai> Vincent: If you have any places you notice, point us at them
- # [18:28] <sylvaing> http://lists.w3.org/Archives/Public/www-style/2012Apr/0239.html
- # [18:28] <glazou> sylvaing: and nothing related to animations and margin-collapsing ?-)
- # [18:28] <fantasai> Topic: Animaton-delay
- # [18:29] <Zakim> - +47.21.65.aadd
- # [18:29] <fantasai> sylvaing: Made a fix to clarify ...
- # [18:29] <fantasai> sylvaing: But case that's not covered -- negative animation delays
- # [18:29] <glazou> Zakim, mute me
- # [18:29] <Zakim> glazou should now be muted
- # [18:29] <fantasai> sylvaing: If you have a 2s animation and you have a -1s delay, your animation starts in the middle
- # [18:29] <glazou> Zakim, unmute me
- # [18:29] <Zakim> glazou should no longer be muted
- # [18:29] <fantasai> sylvaing: but if you have -5s animation, what does it mean?
- # [18:30] <fantasai> sylvaing: Implementations agree that if you have repetition of 1, and you have delay greater than duration, nothing happens
- # [18:30] <fantasai> sylvaing: However if you have more, and you ask for a delay, then you might skip repetitions
- # [18:30] * fantasai unsure if that was quite right
- # [18:31] <fantasai> Florian: Looks like you didn't test Opera. The behavior we have in Opera, we don't like it
- # [18:31] <fantasai> smfr: Need to define what happens if fill mode is greater than duration
- # [18:32] <fantasai> smfr: do you jump to last keyrame even though you didn't run the animation?
- # [18:32] <fantasai> smfr: For all cases where the animation either never runs or completes instantaneously, we need to decide what fill-mode does
- # [18:32] * Quits: vhardy_ (vhardy@206.80.17.29) (Connection reset by peer)
- # [18:32] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [18:32] <fantasai> smfr: Also define whether event fires
- # [18:32] <oyvind> I assume that should say "if you have fill mode and delay is greater than duration"
- # [18:33] * Quits: howcome (howcome@88.89.78.85) (Ping timeout)
- # [18:33] * fantasai wonders what happened to http://lists.w3.org/Archives/Public/www-style/2010Apr/0110.html
- # [18:33] <oyvind> or rather "if you have fill mode and negative delay of greater magnitude than duration"
- # [18:33] * fantasai wonders if it ever got filed
- # [18:33] <fantasai> plinss: Any objections?
- # [18:34] <smfr> fantasai: i don't think it did
- # [18:34] <fantasai> RESOLVED: Accept Sylvain's proposal
- # [18:34] <fantasai> smfr, :/
- # [18:34] <fantasai> Topic: Values and Units
- # [18:34] <TabAtkins_> ScribeNick: tantek
- # [18:34] <fantasai> ScribeNick: fantasai
- # [18:34] <tantek> ?
- # [18:34] <glazou> URL ?
- # [18:34] <fantasai> TabAtkins_: Awhile back, resolved to find minimum required ranges
- # [18:35] <fantasai> TabAtkins_: we asked arron for those numbers, but he didn't get back to us for awhile, so we made some numbers up
- # [18:35] <fantasai> TabAtkins_: yesterday he suggested 2^27-1 for all numeric types
- # [18:35] <glazou> is there a URL for the current topic ?
- # [18:35] <fantasai> TabAtkins_: He said it doesn't actually match minimums in IE in all places, but thinks it's reasonable
- # [18:36] <fantasai> Florian: Opera used to have extremely random sizes
- # [18:36] <Ms2ger> http://lists.w3.org/Archives/Public/www-style/2012Apr/0403.html
- # [18:36] <Ms2ger> glazou, ^
- # [18:36] <fantasai> Florian: We recently changed to use 32-bit, but considering moving to 24-bit representation
- # [18:36] <fantasai> Florian: So we might go back low
- # [18:36] <ChrisL> 2^24 -1 then?
- # [18:36] <fantasai> TabAtkins_: That still seems like a large limit
- # [18:36] <glazou> thanks Ms2ger
- # [18:37] <gsnedders> ChrisL: Yeah
- # [18:37] <fantasai> TabAtkins_: Should be more than needed for anything except z-index
- # [18:37] <fantasai> fantasai: The goal here is to be conservative, so low numbers should be fine
- # [18:37] <glazou> and we may need something expressing MAX_RANGE_VALUE
- # [18:37] * ChrisL z-index is an unrestrained binary coded decimal? z-index:-200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
- # [18:38] <fantasai> TabAtkins_: Ok, we'll use 2^24-1; if anyone has another concern bring it up within the week
- # [18:38] <fantasai> TabAtkins_: Another issue is repetitions of component values.
- # [18:38] <fantasai> TabAtkins_: We picked 30
- # [18:38] <fantasai> Florian: We used to have a limit of 32, but now limited only by memory
- # [18:38] <fantasai> Florian: So we're fine either way
- # [18:38] <fantasai> sylvaing: ???
- # [18:38] <bradk> Wasn't there some talk about making z-index into a float?
- # [18:38] <fantasai> TabAtkins_: Any time the grammar has a repetition, e.g. + or *, how many are required
- # [18:39] <glazou> chained lists in memory are so hard to implement ? ;-)
- # [18:39] <fantasai> Florian: I believe IE was limited to 20 in some cases
- # [18:39] <fantasai> TabAtkins_: calc(), I think
- # [18:39] <fantasai> TabAtkins_: Also have a 30-term min on calc
- # [18:39] <fantasai> TabAtkins_: So, we'll put this in, and people can object if it's too high; we'll lower it if necessary
- # [18:39] <Zakim> -krit
- # [18:40] <glazou> glazou: good strategy
- # [18:40] <fantasai> TabAtkins_: We can even do that in CR, since it won't make anyone invalid that was valid before
- # [18:40] * Joins: krit (Adium@192.150.10.201)
- # [18:40] <fantasai> RESOLVED: 2^24-1 minimum for numeric types, 30-component minimum for repetitions, 30-component minimum for calc(), adjust lower if necessary later
- # [18:40] <fantasai> glazou: Should that be tested?
- # [18:41] <fantasai> TabAtkins_: Yes, the whole point is to allow testing
- # [18:41] * sylvaing arronei had not slept for years due to the lack of normative limits on these.....now he's going to party for a month.
- # [18:41] <fantasai> talk about testing this
- # [18:42] <smfr> q+
- # [18:42] * Zakim sees smfr on the speaker queue
- # [18:42] <fantasai> TabAtkins_: nother issue
- # [18:42] <fantasai> TabAtkins_: Kenny brought up the really fun situation...
- # [18:42] <fantasai> TabAtkins_: Right now, when we have attr(), we do early syntax checking if the type and the fallback are appropriate for the place
- # [18:42] <fantasai> TabAtkins_: I can give an example, where this is still confusing
- # [18:42] * glazou W3C just changed my affiliaten to "Organization 1" !!!
- # [18:42] <TabAtkins_> box-shadow: attr(size px, inset) 5px 10px blue;
- # [18:43] <fantasai> TabAtkins_: So, in this, whether you interpret the attr() as a pixel size or the 'inset' keyword, but you get completely different meanings out of the two
- # [18:43] * sylvaing glazou, i guess that's a disruptive innovation...
- # [18:43] * glazou sylvaing: thank you sylvaing :)
- # [18:43] <fantasai> TabAtkins_: If you have multiple attrs(), you have to do combinatorial checking of possible values
- # [18:43] <fantasai> TabAtkins_: We went and restricted it to say that if attr() is the sole value of the property, you can do whatever you want
- # [18:44] <fantasai> TabAtkins_: But if you use it as a component value, the fallback has to be the same type as the declared attr type
- # [18:44] <fantasai> fantasai: I'd like to have dbaron check on this before we close
- # [18:44] <plinss> ack smfr
- # [18:44] * Zakim sees no one on the speaker queue
- # [18:44] <fantasai> smfr: Going back to ... sometime ago I proposed some text about roundtripping
- # [18:45] <fantasai> smfr: If you supply value that's too large, it gets truncated, you write it back out it shoudl roundtrip
- # [18:45] <fantasai> TabAtkins_: Could add some specific requirements if that's needed
- # [18:45] <fantasai> smfr: ... z-index ...
- # [18:45] <fantasai> TabAtkins_: Requirement is that you clamp to the nearest supported value
- # [18:45] <fantasai> smfr: So it clamps and then roundtrips, ok that's fine
- # [18:46] <fantasai> TabAtkins_: I don't think we have anything else right now
- # [18:46] <fantasai> fantasai: Stay tuned, we'll have lots of issues to resolve next week!
- # [18:46] <fantasai> Topic: Baselines of Flexbox
- # [18:46] <Zakim> +[Microsoft.a]
- # [18:46] <fantasai> TabAtkins_: The issue was a) we didn't define the baseline of a flexbox
- # [18:46] <fantasai> TabAtkins_: The possibilities are either baselin of first-child, or somehow do what tables do (don't remember what they do)
- # [18:47] <fantasai> alexmog_: We came to a conclusion for our implementation
- # [18:47] * Joins: PhilCupp (pcupp@131.107.0.114)
- # [18:47] <fantasai> alexmog_: Baseline of first child is baseline of flexbox
- # [18:47] <fantasai> alexmog_: But we didn't have per-item alignment
- # [18:47] <fantasai> alexmog_: I think what we had then is still ok
- # [18:47] <fantasai> alexmog_: If there are items with baseline-alignment sharing baseline, reasonable for that to be baseline of flexbox. Otherwise take first one
- # [18:48] <fantasai> RESOLVED: Baseline of flexbox is baseline of baseline-aligned boxes if any, otherwise take first child
- # [18:48] <fantasai> TabAtkins_: Second part is, how do you determine baseline of the first child
- # [18:49] <fantasai> TabAtkins_: Proposal is use baseline of first child's display type
- # [18:49] * glazou has a 30-seconds extra agenda item
- # [18:49] <fantasai> Florian: We'd prefer not to do that, becasue if we consider things in terms of display-inside, display-outside, your display-outside would be something like flexbox-item, so you can't distinguish inline-block and block
- # [18:49] * fantasai agrees with Florian
- # [18:50] <fantasai> TabAtkins_: So in practice, we could use the 2.1 conversion table for this
- # [18:50] <fantasai> TabAtkins_: I don't care much either way, but several implementers said using display type makes sense to them
- # [18:51] <TabAtkins_> http://www.w3.org/mid/87pqbfkcex.fsf@aeneas.oslo.osa
- # [18:51] <fantasai> fantasai: It's implementable, beacuse we can always look up the computed style, but that doesn't necessarily mean it makes sense
- # [18:52] * sylvaing alternative: flexbox item with the highest z-index wins!
- # [18:52] <fantasai> alexmog_: I think flexbox child would have it's display type, and just have an internal display-outside of flexbox-item
- # [18:53] <fantasai> Florian: In that case, you shouldn't be using display-outside of inline/block to determine different alignments
- # [18:53] <fantasai> alexmog_: That's what I'm saying, inline-block and block should behave the same
- # [18:53] <fantasai> alexmog_: Related issue is that suppose you have flexbox with one item, and that's inline-block or block or table with table cell
- # [18:53] <fantasai> alexmog_: each with different definition of baseline
- # [18:54] <fantasai> alexmog_: no way to make us actually ignore that internal baseline entirely and say that I want the baseline of that box be the bottom of the box
- # [18:54] <fantasai> alexmog_: Or can i?
- # [18:54] <fantasai> fantasai: I think there were some proposals for that. Might be added to Line Layout module
- # [18:55] <fantasai> TabAtkins_: Think we can defer that to later
- # [18:56] <fantasai> RESOLVED: Use the table for converting display types to block-level types to determine baselines; effectively this is using display-inside
- # [18:57] <fantasai> glazou: Announce that Backgrounds and Borders / Image Values moved to CR
- # [18:57] <fantasai> glazou: missing announcements
- # [18:57] <fantasai> TabAtkins_: yeah, fantasai and I were working all day on css3-values
- # [18:57] <fantasai> TabAtkins_: will get to that
- # [18:57] <TabAtkins_> https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=Flexbox&resolution=---
- # [18:58] <fantasai> TabAtkins_: I think there are less than 6 weeks of work left on Flexbox, so propose to move to LC
- # [18:58] <fantasai> fantasai: no
- # [18:58] <fantasai> TabAtkins_: If there are other issues to bring up, appreciate that happening now
- # [18:58] <ChrisL> that is being ready in 6 weeks
- # [18:59] <ChrisL> and there should be no open issues, so its a stable document for reviewers
- # [18:59] <fantasai> fantasai: ...
- # [19:00] <fantasai> TabAtkins_: I don't think there are any major issues left.
- # [19:01] <fantasai> ChrisL: If you think you have only one week of work left, then come back in a week and ask for Last Call
- # [19:01] <fantasai> alexmog_: I think we're done, we don't have anything else
- # [19:01] <ChrisL> I agree with fantasai that if there are pending edits, do them first before going to last call
- # [19:01] <fantasai> fantasai: I disagree, and I would like to see the alignment issues addressed before LC
- # [19:01] <fantasai> plinss: I agree with fantasai [...]
- # [19:02] <fantasai> plinss: Major issues / minor issues, whatever.
- # [19:02] <fantasai> plinss: Want to present things for people to review.
- # [19:02] <ChrisL> so defer that issue as out of scope
- # [19:03] <sylvaing> can we just accept/postpone LC?
- # [19:04] <fantasai> ....
- # [19:04] * ChrisL wishes we wouldn't try to rewrite the process every time
- # [19:04] <fantasai> Florian: zero bugs is hard to get to
- # [19:04] <fantasai> Florian: But you shouldn't go to LC with bugs that you aren't willing to defer to next level
- # [19:05] * sylvaing ChrisL, but if we fix up the z-index it'll work!
- # [19:05] <fantasai> fantasai: If you are making significant changes between LC and CR, you need to do another LC. You're not gaining anything there.
- # [19:05] <glazou> let's collapse the margins of the flex box spec first
- # [19:05] <Zakim> -ChrisL
- # [19:05] <stearns> it's not LC, it's -w3c-LC
- # [19:05] <fantasai> Anton: If you've got a bunch of pending edits you haven't made, then it's not really a Last Call, it's another Working Draft
- # [19:06] * vhardy_ need to step out.
- # [19:07] <Zakim> -vhardy_
- # [19:07] <fantasai> glazou: Going to LC is decision of the WG. Decisions of the WG is made base don review of the members. Asking for review before transition request
- # [19:07] <fantasai> is fair
- # [19:07] <fantasai> sylvaing: maybe we should talk about actual issues?
- # [19:07] * glazou does not see a consensus about going to LC anyway
- # [19:08] <fantasai> florian: have a small question, fantasai has said several times that shouldn't go to LC until dbaron reviews.
- # [19:08] <fantasai> TabAtkins_: AFAIK dbaron is deferring to dholbert
- # [19:08] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
- # [19:09] <fantasai> plinss: We don't have consensus to go to LC. So work on the issues, and we'll ...
- # [19:09] <fantasai> come back to it later
- # [19:09] * glazou has to run, sorry people, bye
- # [19:09] * stearns also has to go
- # [19:10] <fantasai> sylvaing: There's some issues that require WG discussion, e.g. renaming everything and going to LC are incompatible
- # [19:10] <Zakim> -glazou
- # [19:10] <Zakim> -stearns
- # [19:10] <fantasai> antonp: What do I need to review here?
- # [19:10] * Quits: glazou (glazou@85.168.27.11) (Quit: glazou)
- # [19:10] <fantasai> antonp: Is bugzilla + current editor's draft what's needed to review this thing?
- # [19:10] <fantasai> plinss: Everyone please review
- # [19:10] <Zakim> -Katie
- # [19:10] <Zakim> -[Microsoft.aa]
- # [19:10] <fantasai> Meeting closed.
- # [19:10] <Zakim> -TabAtkins
- # [19:11] <Zakim> -[Microsoft.a]
- # [19:11] <Zakim> -??P62
- # [19:11] * Quits: Katie (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:11] <Zakim> -[Microsoft]
- # [19:11] * Quits: JohnJansen (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:11] <Zakim> -sylvaing
- # [19:11] <Zakim> -plinss
- # [19:11] * Quits: PhilCupp (pcupp@131.107.0.114) (Quit: PhilCupp)
- # [19:11] <Zakim> -florianr
- # [19:11] <Zakim> -hober
- # [19:11] <Zakim> -dstorey
- # [19:11] <Zakim> -??P83
- # [19:11] * Quits: antonp (50a94e63@109.169.29.95) (Quit: http://www.mibbit.com ajax IRC Client)
- # [19:11] <Zakim> -bradk
- # [19:11] <Zakim> -smfr
- # [19:11] * Quits: bradk (bradk@99.7.175.117) (Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ )
- # [19:14] * Quits: tantek (tantek@76.115.51.221) (Quit: tantek)
- # [19:15] * Quits: dstorey (Adium@67.180.84.179) (Quit: Leaving.)
- # [19:16] <Zakim> disconnecting the lone participant, antonp, in Style_CSS FP()12:00PM
- # [19:16] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:16] <Zakim> Attendees were florianr, plinss, glazou, sylvaing, hober, smfr, stearns, arronei, antonp, +1.415.308.aaaa, +1.650.275.aabb, bradk, JohnJansen, +1.415.832.aacc, vhardy_, krit,
- # [19:16] <Zakim> ... alexmog_, +47.21.65.aadd, dstorey, [Microsoft], TabAtkins, ChrisL, Katie
- # [19:17] * Quits: ChrisL (ChrisL@128.30.52.169) (Quit: Fire on main board error, client combusted)
- # [19:26] * Parts: oyvind (oyvinds@213.236.208.22)
- # [19:27] * Joins: dstorey (Adium@67.180.84.179)
- # [19:29] * Parts: smfr (smfr@173.228.90.231)
- # [19:38] * Quits: dstorey (Adium@67.180.84.179) (Quit: Leaving.)
- # [19:41] * Quits: vhardy_ (vhardy@206.80.17.29) (Quit: vhardy_)
- # [19:41] * Quits: drublic (drublic@93.132.253.242) (Client exited)
- # [19:45] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [19:45] * Quits: florianr (florianr@213.236.208.22) (Quit: Leaving.)
- # [19:47] * Quits: vhardy_ (vhardy@206.80.17.29) (Quit: vhardy_)
- # [19:50] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [19:51] * Quits: vhardy_ (vhardy@206.80.17.29) (Quit: vhardy_)
- # [19:52] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [20:01] * Joins: drublic (drublic@95.115.28.183)
- # [20:13] * Joins: dstorey (Adium@144.189.101.1)
- # [20:20] * Quits: nimbu (Adium@192.150.10.201) (Quit: Leaving.)
- # [20:26] * Joins: nimbu (Adium@192.150.10.201)
- # [20:27] * Quits: alexmog_ (qw3birc@128.30.52.28) (Ping timeout)
- # [20:58] * Joins: leaverou (leaverou@207.239.114.206)
- # [20:58] * Joins: tantek (tantek@76.115.51.221)
- # [21:02] * Quits: nimbu (Adium@192.150.10.201) (Quit: Leaving.)
- # [21:08] * Quits: vhardy_ (vhardy@206.80.17.29) (Quit: vhardy_)
- # [21:22] * Quits: leaverou (leaverou@207.239.114.206) (Quit: leaverou)
- # [21:24] * Joins: leaverou (leaverou@207.239.114.206)
- # [21:27] * Quits: leaverou (leaverou@207.239.114.206) (Quit: ttyl laters everyone!)
- # [21:36] * sylvaing is now known as sylvaing_away
- # [21:43] * Quits: dstorey (Adium@144.189.101.1) (Quit: Leaving.)
- # [21:43] * Parts: ksweeney (ksweeney@63.119.10.10)
- # [22:10] * Joins: dstorey (Adium@144.189.101.1)
- # [22:42] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [22:47] * Quits: vhardy_ (vhardy@206.80.17.29) (Client exited)
- # [22:47] * Joins: vhardy_ (vhardy@192.150.10.201)
- # [22:48] * Joins: nimbu (Adium@192.150.10.201)
- # [23:08] * Joins: jet (jet@203.63.65.169)
- # [23:22] * Quits: Ms2ger (Ms2ger@91.181.73.47) (Connection reset by peer)
- # [23:23] * Joins: Ms2ger (Ms2ger@91.181.73.47)
- # [23:27] * Quits: Ms2ger (Ms2ger@91.181.73.47) (Quit: nn)
- # [23:37] * Joins: vhardy__ (vhardy@206.80.17.29)
- # [23:37] * Quits: vhardy__ (vhardy@206.80.17.29) (Quit: vhardy__)
- # [23:38] * Joins: vhardy__ (vhardy@206.80.17.29)
- # [23:40] * Quits: vhardy_ (vhardy@192.150.10.201) (Ping timeout)
- # [23:44] * Quits: nimbu (Adium@192.150.10.201) (Quit: Leaving.)
- # [23:44] * Joins: nimbu (Adium@192.150.10.201)
- # [23:47] * Joins: vhardy_ (vhardy@206.80.17.29)
- # [23:47] * Quits: vhardy__ (vhardy@206.80.17.29) (Connection reset by peer)
- # [23:57] * Quits: jet (jet@203.63.65.169) (Quit: jet)
- # Session Close: Thu Apr 19 00:00:00 2012
The end :)