Options:
- # Session Start: Wed Aug 01 00:00:00 2012
- # Session Ident: #css
- # [00:01] * Joins: glenn (gadams@174.29.115.20)
- # [00:08] <dbaron> TabAtkins, I renamed a few things, but otherwise looks good
- # [00:16] * Joins: Liam (liam@128.30.52.169)
- # [00:16] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [00:51] * Quits: drublic (drublic@93.132.245.252) (Client exited)
- # [01:03] <fantasai> alexmog: http://lists.w3.org/Archives/Public/www-style/2012Jul/0722.html
- # [01:03] <fantasai> dbaron: Cool. Think you're ready for an updated WD? :)
- # [01:04] <dbaron> fantasai, probably not quite
- # [01:04] <TabAtkins> dbaron: The common interface you talk about is shared by everything that I call "rule-filled" in Syntax.
- # [01:05] <TabAtkins> If that helps with naming at all...
- # [01:05] <dbaron> TabAtkins, I don't think it does.
- # [01:06] <dbaron> TabAtkins, Though I'm wondering about alternatives like cheese-filled or meat-filled.
- # [01:06] <TabAtkins> Excellent.
- # [01:06] <TabAtkins> CSSRuleFilledRule
- # [01:06] <TabAtkins> SO EASY TO UNDERSTAND
- # [01:07] <TabAtkins> I dislike supportsCSS, because it's not about CSS in general, just a single property.
- # [01:07] * Joins: glenn (gadams@174.29.115.20)
- # [01:08] * fantasai wonders if it's possible to co-opt "rule set"
- # [01:13] <stearns> dbaron: will you be able to respond to the exclusions issue posts soon?
- # [01:13] * heycam|away is now known as heycam
- # [01:16] <fantasai> CSSRuleSetRule
- # [01:20] <TabAtkins> stearns: Florian's response seems to be good.
- # [01:21] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [01:21] <stearns> TabAtkins: I like the collision property idea. I don't think it should be required for exclusions
- # [01:22] <stearns> an example of what gets fouled up by exclusions would be much more helpful than vague handwaving about broken layouts
- # [01:22] <TabAtkins> I was just referring to his phrasing of the issue, actually, that it's easy to produce abspos-exclusions that will fail badly in different size contexts.
- # [01:23] <TabAtkins> His assertion that authoring tools will probably use abspos seems apt.
- # [01:23] <stearns> I would say that it's easy to produce abspos elements that fail badly. Adding exclusions to the mix does not increase that failure
- # [01:24] <TabAtkins> This is true. The problem is that it seems that abspos exclusions will probably be the *easiest* type to author, particularly when tool-assisted.
- # [01:24] <TabAtkins> And that this will increase abspos usage in general, since it's suddenly much more useful.
- # [01:26] <stearns> exclusions are perfectly fine with flex, perfectly fine with grid, and can be used responsibly with other layouts
- # [01:31] <TabAtkins> Yes, that's been stated. I don't think that counters my assertions, though.
- # [01:31] <TabAtkins> Namely, that they work badly with abspos (as badly as abspos normally work) and that they'll be popular and commonly-used with abspos.
- # [01:33] <stearns> is there a technical argument in that statement that is possible to address in the exclusions specification?
- # [01:35] <stearns> (and while the fact that exclusions work fine in some cases has been stated, dbaron has not acknowledged this)
- # [01:35] * Quits: jet (jet@206.15.76.122) (Quit: jet)
- # [01:37] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [01:38] <TabAtkins> The technical argument is "abspos sucks, because they can easily collide all the time, so you should either forbid abspos from being exclusions, or define a collision model like floats do". I think that's dbaron's desire, exactly.
- # [01:40] * Joins: arno (arnog@192.150.10.201)
- # [01:41] <stearns> that would be a welcome, actionable issue that we could work over. I'd love to change the issue wording to something like that
- # [01:42] <stearns> but I'd note that overlapping abspos exclusion handling was one of the first things people on www-style asked to add to the spec :)
- # [01:48] * Quits: krit (krit@192.150.10.201) (Quit: Leaving.)
- # [01:56] * Joins: krit (krit@192.150.10.201)
- # [02:15] * Quits: krit (krit@192.150.10.201) (Ping timeout)
- # [02:16] * Joins: glenn (gadams@174.29.115.20)
- # [02:27] <stearns> the @media rule will be used to reposition abspos elements, particularly in tool-assisted scenarios. It encourages abspos use :)
- # [02:28] * Quits: Liam (liam@128.30.52.169) (Ping timeout)
- # [02:29] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [02:39] * Quits: leaverou (leaverou@203.167.141.74) (Quit: leaverou)
- # [02:50] * Joins: glenn (gadams@174.29.115.20)
- # [02:52] * Joins: leaverou (leaverou@131.203.92.135)
- # [02:53] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [02:55] * Joins: arno (arnog@192.150.10.201)
- # [03:16] * Joins: Liam (liam@128.30.52.169)
- # [03:17] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [03:35] * Joins: glenn (gadams@174.29.115.20)
- # [03:45] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [04:12] * Quits: dbaron (dbaron@206.15.76.122) (Ping timeout)
- # [04:25] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [05:03] * Joins: dbaron (dbaron@70.36.140.99)
- # [05:36] * Joins: glenn (gadams@174.29.115.20)
- # [05:40] * Quits: leaverou (leaverou@131.203.92.135) (Quit: leaverou)
- # [05:49] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [05:53] * Joins: leaverou (leaverou@131.203.92.135)
- # [05:57] * Quits: leaverou (leaverou@131.203.92.135) (Quit: leaverou)
- # [06:04] * heycam is now known as heycam|away
- # [06:05] * Joins: glenn (gadams@174.29.115.20)
- # [06:27] * heycam|away is now known as heycam
- # [06:43] * Joins: leaverou (leaverou@203.167.141.74)
- # [07:15] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [08:12] * Quits: leaverou (leaverou@203.167.141.74) (Quit: leaverou)
- # [10:16] * Quits: dbaron (dbaron@70.36.140.99) (Ping timeout)
- # [10:22] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [10:50] * Joins: leaverou (leaverou@203.167.141.74)
- # [10:57] * heycam is now known as heycam|away
- # [11:15] * Joins: drublic (drublic@80.152.164.43)
- # [11:16] * Quits: drublic (drublic@80.152.164.43) (Client exited)
- # [11:16] * Joins: drublic (drublic@80.152.164.43)
- # [11:50] * Joins: SimonSapin (simon@82.232.219.95)
- # [13:38] * Quits: drublic (drublic@80.152.164.43) (Client exited)
- # [13:41] * Joins: drublic (drublic@80.152.164.43)
- # [13:42] * Joins: florianr (florianr@91.203.97.251)
- # [16:17] * Joins: glenn (gadams@174.29.115.20)
- # [16:48] * Joins: Ankh (liam@128.30.52.169)
- # [16:53] * Quits: Liam (liam@128.30.52.169) (Ping timeout)
- # [17:04] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [17:05] * Joins: ksweeney (ksweeney@63.119.10.10)
- # [17:05] * Parts: ksweeney (ksweeney@63.119.10.10)
- # [17:08] * Joins: glenn (gadams@174.29.115.20)
- # [17:32] * Joins: Ms2ger (Ms2ger@81.242.172.208)
- # [17:38] * Joins: glazou (glazou@82.247.96.19)
- # [17:38] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [17:38] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
- # [17:38] <RRSAgent> logging to http://www.w3.org/2012/08/01-css-irc
- # [17:38] <glazou> Zakim, this will be Style
- # [17:38] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 31 minutes
- # [17:38] <glazou> RRSAgent, make logs public
- # [17:38] <RRSAgent> I have made the request, glazou
- # [17:39] <glazou> leaverou: congrats :-)
- # [17:39] <glazou> welcome onboard
- # [17:51] <glazou> Regrets: plinss
- # [17:57] * Joins: cabanier (cabanier@192.150.22.55)
- # [18:01] * Joins: lstorset (lastorset@91.203.96.240)
- # [18:04] * Quits: lstorset (lastorset@91.203.96.240) (Ping timeout)
- # [18:05] * Joins: dbaron (dbaron@70.36.140.99)
- # [18:05] <Zakim> Style_CSS FP()12:00PM has now started
- # [18:05] <Zakim> +fantasai
- # [18:06] <Zakim> +??P8
- # [18:06] <glazou> Zakim, ??P8 is me
- # [18:06] <Zakim> +glazou; got it
- # [18:08] * Joins: antonp (50a94e63@64.62.228.82)
- # [18:08] * Joins: dstorey (Adium@67.180.84.179)
- # [18:08] * Joins: lstorset (lastorset@91.203.96.240)
- # [18:08] <Zakim> + +1.206.675.aaaa
- # [18:09] <Zakim> +Bert
- # [18:09] <glazou> Zakim, aaaa is cabanier
- # [18:09] <Zakim> +cabanier; got it
- # [18:09] <cabanier> Zakim, 206.675.aaa is me
- # [18:09] <Zakim> sorry, cabanier, I do not recognize a party named '206.675.aaa'
- # [18:09] <Zakim> + +1.206.324.aabb
- # [18:09] <cabanier> Zakim, +206.675.aaa is me
- # [18:09] <Zakim> sorry, cabanier, I do not recognize a party named '+206.675.aaa'
- # [18:09] <sylvaing> Zakim, aabb is sylvaing
- # [18:09] <Zakim> +sylvaing; got it
- # [18:09] <glazou> cabanier: I already did it
- # [18:09] * Joins: florian (florianr@91.203.96.240)
- # [18:09] <cabanier> Thanks!
- # [18:09] <dstorey> I'll be on IRC only today. Don't have phone access right now
- # [18:10] <glazou> Zakim, who is noisy?
- # [18:10] <glazou> dstorey: ok
- # [18:10] <Zakim> glazou, listening for 10 seconds I could not identify any sounds
- # [18:10] <Zakim> + +47.23.69.aacc
- # [18:10] <Zakim> +??P24
- # [18:10] <Zakim> +[Microsoft]
- # [18:10] <Zakim> + +1.415.308.aadd
- # [18:10] <florian> Zakim, I am aacc
- # [18:10] <Zakim> +florian; got it
- # [18:10] * Joins: JohnJansen (qw3birc@128.30.52.28)
- # [18:11] * Joins: smfr (smfr@173.228.90.242)
- # [18:11] <JohnJansen> Zakim, Microsoft has JohnJansen
- # [18:11] <Zakim> +JohnJansen; got it
- # [18:11] <Zakim> + +1.206.390.aaee
- # [18:11] <Zakim> + +93550aaff
- # [18:11] <stearns> zakim, aaee is me
- # [18:11] <Zakim> +[Microsoft.a]
- # [18:11] <Zakim> + +1.604.312.aagg
- # [18:11] <antonp> Zakim, aaff is me
- # [18:11] <Zakim> +stearns; got it
- # [18:11] * Joins: Katie (qw3birc@128.30.52.28)
- # [18:11] <Zakim> +antonp; got it
- # [18:11] <fantasai> sylvaing: http://lea.verou.me/2012/08/lea-at-w3-org/
- # [18:11] <florian> Zakim, aacc has lstorset
- # [18:11] <Zakim> +??P43
- # [18:11] <Zakim> sorry, florian, I do not recognize a party named 'aacc'
- # [18:11] <glenn> zakim, ??p43 is me
- # [18:12] <Zakim> +??P45
- # [18:12] <Zakim> +glenn; got it
- # [18:12] <Zakim> + +1.408.636.aahh
- # [18:12] <smfr> Zakin, aahh is me
- # [18:12] <florian> Zakim, florian has lstorset
- # [18:12] <Zakim> +lstorset; got it
- # [18:12] <Zakim> +[Microsoft.aa]
- # [18:13] <arronei_> zakim, microsoft has me
- # [18:13] <Zakim> +arronei_; got it
- # [18:13] <smfr> maybe lea can get them to fix zakim
- # [18:13] <glazou> eheh
- # [18:13] <Zakim> + +1.415.766.aaii
- # [18:13] <dbaron> Zakim, aaii is dbaron
- # [18:13] <Zakim> +dbaron; got it
- # [18:13] <glazou> Zakim, who is here?
- # [18:13] <Zakim> On the phone I see fantasai, glazou, cabanier, Bert, sylvaing, florian, ??P24, +1.415.308.aadd, [Microsoft], stearns, antonp, [Microsoft.a], +1.604.312.aagg, glenn, ??P45,
- # [18:13] <Zakim> ... +1.408.636.aahh, [Microsoft.aa], dbaron
- # [18:13] <Zakim> [Microsoft] has arronei_
- # [18:13] <Zakim> florian has lstorset
- # [18:14] <Zakim> On IRC I see Katie, smfr, JohnJansen, florian, lstorset, dstorey, antonp, dbaron, cabanier, RRSAgent, Zakim, glazou, Ms2ger, glenn, Ankh, florianr, drublic, SimonSapin, leaverou,
- # [18:14] <fantasai> ScribeNick: fantasai
- # [18:14] <Zakim> ... SteveZ, krijnh, arronei_, isherman, TabAtkins, shepazu, decadance, alexmog, sylvaing, shans, vhardy, CSSWG_LogBot, logbot, Bert, jwir3, dglazkov, gsnedders, stearns, trackbot,
- # [18:14] <Zakim> ... heycam|away, paul___irish, hober, fantasai, plinss, Hixie
- # [18:14] <fantasai> glazou: any additions to agenda?
- # [18:14] * Joins: TabAtkins_ (qw3birc@128.30.52.28)
- # [18:14] <glazou> http://wiki.csswg.org/planning/sandiego-2012#participants
- # [18:14] * Joins: JohnJansen_ (qw3birc@128.30.52.28)
- # [18:14] <fantasai> glazou: If you plan to attend or not attend, please add your name to the wiki so we know who is coming / when / where
- # [18:14] <Zakim> -??P24
- # [18:14] <JohnJansen_> Zakim, Microsoft has JohnJansen
- # [18:14] <Zakim> +JohnJansen; got it
- # [18:14] <fantasai> Florian: For TPAC meeting, Opera is joining Adobe as a sponsor
- # [18:15] <fantasai> glazou: Thank you very much
- # [18:15] <fantasai> glazou: Any other organization?
- # [18:15] <Katie> zakim, [Microsoft.aa] has me
- # [18:15] <Zakim> +Katie; got it
- # [18:15] <Zakim> + +1.281.305.aajj
- # [18:15] <Zakim> +??P59
- # [18:15] * Quits: JohnJansen (qw3birc@128.30.52.28) (Ping timeout)
- # [18:15] <fantasai> Glenn: Sunday before or Sunday after?
- # [18:15] <fantasai> glazou: before
- # [18:15] <cabanier> link: https://dvcs.w3.org/hg/FXTF/rawfile/4b53107dd95d/compositing/index.html
- # [18:15] <fantasai> Topic: Compositing FPWD
- # [18:16] <glazou> https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html
- # [18:16] * Quits: JohnJansen_ (qw3birc@128.30.52.28) (Quit: Page closed)
- # [18:16] <fantasai> Rik: SVGWG already approved to move to FPWD
- # [18:16] <fantasai> Rik: Think the spec is in reasonable shape.
- # [18:16] <fantasai> Rik: need to get more consensus on CSS keywords
- # [18:16] <fantasai> Rik: There are many; some people requesed fewer
- # [18:17] <fantasai> Rik: As WD will get more exposure
- # [18:17] <fantasai> Rik: e.g. dbaron gave me very good feedback
- # [18:17] <fantasai> Rik: Think it's in readable shape, would like to move to WD
- # [18:17] <fantasai> glazou: Opinions?
- # [18:17] <fantasai> Florian: I haven't read everything, but I like it so, yeah
- # [18:17] <stearns> Tab: I approve
- # [18:17] <fantasai> dbaron: The biggest thing I was worried about was z-ordering stuff, possible I confused people
- # [18:17] <Zakim> +SteveZ
- # [18:18] <fantasai> dbaron: If it's either fixed, or there's a note that it needs to be fixed, I'm ok with it
- # [18:18] * Joins: krit (krit@24.4.186.73)
- # [18:18] <fantasai> Rik: I rewrote it with stacking context, like you said, and linked to Appendix E
- # [18:18] <krit> Zakim, who os here?
- # [18:18] <fantasai> Rik: ... add an example that shows what is happening, ppl will not get confused.
- # [18:18] <Zakim> I don't understand your question, krit.
- # [18:18] <krit> Zakim, who is here?
- # [18:18] <Zakim> On the phone I see fantasai, glazou, cabanier, Bert, sylvaing, florian, +1.415.308.aadd, [Microsoft], stearns, antonp, [Microsoft.a], +1.604.312.aagg, glenn, ??P45,
- # [18:18] <Zakim> ... +1.408.636.aahh, [Microsoft.aa], dbaron, +1.281.305.aajj, ??P59, SteveZ
- # [18:18] <TabAtkins_> ScribeNick: TabAtkins
- # [18:18] <Zakim> [Microsoft.aa] has Katie
- # [18:19] * sylvaing the kids love blending!
- # [18:19] <Zakim> florian has lstorset
- # [18:19] <Zakim> [Microsoft] has JohnJansen
- # [18:19] <TabAtkins_> glazou: So, no objections against FPWD of compositing?
- # [18:19] <Zakim> On IRC I see krit, TabAtkins_, Katie, smfr, florian, lstorset, dstorey, antonp, dbaron, cabanier, RRSAgent, Zakim, glazou, Ms2ger, glenn, Ankh, florianr, drublic, SimonSapin,
- # [18:19] <krit> Zakim, aadd is me
- # [18:19] <Zakim> ... leaverou, SteveZ, krijnh, arronei_, isherman, TabAtkins, shepazu, decadance, alexmog, sylvaing, shans, vhardy, CSSWG_LogBot, logbot, Bert, jwir3, dglazkov, gsnedders, stearns,
- # [18:19] <TabAtkins_> glazou: Okay, so let's do that.
- # [18:19] * Joins: JohnJansen (qw3birc@128.30.52.28)
- # [18:19] <Zakim> ... trackbot, heycam|away, paul___irish, hober, fantasai, plinss, Hixie
- # [18:19] <TabAtkins_> RESOLVED: Publish FPWD of the Compositing draft.
- # [18:19] <Zakim> -fantasai
- # [18:19] * Joins: rbetts (rbetts@24.84.208.90)
- # [18:19] <JohnJansen> Zakim, Microsoft has JohnJansen
- # [18:19] <Zakim> +krit; got it
- # [18:19] <Zakim> JohnJansen was already listed in [Microsoft], JohnJansen
- # [18:19] <Zakim> +fantasai
- # [18:20] <Zakim> + +1.619.846.aakk
- # [18:20] <fantasai> glazou: Anything else wrt compositing?
- # [18:20] <fantasai> Topic: Flexbox
- # [18:20] <TabAtkins_> Topic: Flexbox
- # [18:20] <fantasai> Bert: It's part of CSS and SVG, who does the publishing, is that me?
- # [18:20] <fantasai> Rik: I think it's part of CSS, so we opened a Bugzilla as part of CSS
- # [18:21] <fantasai> Rik: FX will not get as much exposure, and it's not specific to SVG, just adding CSS properties
- # [18:21] <fantasai> Rik: Let me know if I need to change anything
- # [18:21] <glazou> http://dev.w3.org/csswg/css3-flexbox/
- # [18:21] <hober> Zakim, aakk is me
- # [18:21] <Zakim> +hober; got it
- # [18:21] <fantasai> ACTION Bert: Publish Compositing FPWD
- # [18:21] * RRSAgent records action 1
- # [18:21] * trackbot noticed an ACTION. Trying to create it.
- # [18:21] <trackbot> Created ACTION-487 - Publish Compositing FPWD [on Bert Bos - due 2012-08-08].
- # [18:21] <fantasai> TOpic: Flexbox
- # [18:21] * sylvaing CR? We've run out of things to rename? YAY
- # [18:21] <fantasai> Tab: We concluded last week with some resolutions that should cover what we need to do, and left actual resolutions to me and fantasai
- # [18:21] * Ms2ger sylvaing: don't jinx it! ;)
- # [18:22] <fantasai> Tab: We tried to go with Option D, and to match it thematically with how abspos works in block layout
- # [18:22] <fantasai> Tab: You look for your next/previous item and attach it there
- # [18:22] <fantasai> Tab: fantasai worked out how to treat it as a placeholder and just do some packing-space suppression
- # [18:22] <fantasai> Florian: As long as Morten is happy, it's good with me
- # [18:23] <fantasai> szilles: If there's a sequence of abspos, they are processed and attached to the same edge
- # [18:23] <fantasai> fantasai: yes
- # [18:23] <fantasai> szilles: And order means that I don't choose the adjacent edge until after I've finished reordering.
- # [18:23] <fantasai> szilles: If you could make the wording a little more obvious in that direciton, would be helpful
- # [18:23] <fantasai> Tab: wrt first one, we do talk about in-flow items--abspos is out of flow
- # [18:23] <fantasai> Tab: Second one, we're explicit that you run reordering first.
- # [18:24] <fantasai> Florian: Maybe clarify in a note or something
- # [18:24] <fantasai> Morten's response - http://lists.w3.org/Archives/Public/www-style/2012Aug/0023.html
- # [18:24] <fantasai> szilles: great job
- # [18:24] <fantasai> Tab: One bit that's important, last week WG officially resolved that 'order' doesn't apply to abspos
- # [18:25] <fantasai> Tab: Wanted to ask WG if ok with reverting that.
- # [18:25] <fantasai> Tab: As written right now, order affects the abspos.
- # [18:25] <fantasai> Florian: Sounds fine to me. Was only concerned about applying to placeholders.
- # [18:25] * Joins: arno (arnog@192.150.10.201)
- # [18:25] <fantasai> Tab: Morten's ok with it, and chrome is ok today
- # [18:26] * fantasai notes bzbarsky said it would be easy for Gecko
- # [18:26] <fantasai> Anton: I'm wondering, do we expect abspos static positioning to work with layout models in this way?
- # [18:26] <fantasai> Anton: It's ok, but I think we need to think about the consequences with other layout models
- # [18:26] <fantasai> Anton: Note also that float or clear doesn't affect abspos
- # [18:27] <fantasai> Anton: Might decide that's an anomaly
- # [18:27] <fantasai> fantasai: or maybe it was added for compat
- # [18:28] <fantasai> Tab: Could have principle that do layout, then position abspos
- # [18:28] <fantasai> dbaron: Concerned about that. Don't really want to do layout
- # [18:28] <fantasai> ...
- # [18:29] <fantasai> Florian: I think it's in line with what we called the Rossen Principle. In block layout, if you abspos and don't give coordinates it goes where it would have been
- # [18:29] <fantasai> Florian: Flexbox does roughly the same thing
- # [18:29] <fantasai> Florian: Don't think anything very different here wrt high-level view
- # [18:29] <fantasai> Tab: I think dbaron just wants a clarification of whether for future models you do any work
- # [18:30] <fantasai> Florian: Hard to discuss without a specific case in mind
- # [18:30] <fantasai> Rossen: Wrt Grid, we always position in the origin of a grid cell in Grid
- # [18:30] <fantasai> Rossen: You honor grid-row/grid-column positioning, but otherwise put in origin
- # [18:31] <fantasai> Rossen: I do agree that higher-order question of should follow block/flow layout model in other layout models, where that doesn't make any sense?
- # [18:31] <fantasai> Rossen: Or go with something simpler, like Tab was suggesting (origin of flex container) last week
- # [18:32] <dbaron> Rossen: I'm still in favor of going for something simpler in layout models that have no concept of flow.
- # [18:32] * fantasai thanks
- # [18:32] <fantasai> ...
- # [18:32] * krit Yet another flexbox discussion http://en.wikipedia.org/wiki/Groundhog_Day_(film) :)
- # [18:32] <fantasai> szilles: Positioning of flexboxes is ...
- # [18:32] * fantasai reminds everyone that we should close the topic
- # [18:32] <dbaron> For reference, my position in last week's straw poll would have been A.
- # [18:33] <fantasai> Tab: Want to request resolution of reversing order, and of going to CR
- # [18:33] <fantasai> RESOLVED: order affects abspos, Flexbox goes to CR
- # [18:33] <fantasai> ACTION Bert: send Flexbox CR transition request
- # [18:33] * trackbot noticed an ACTION. Trying to create it.
- # [18:33] * RRSAgent records action 2
- # [18:33] <trackbot> Created ACTION-488 - Send Flexbox CR transition request [on Bert Bos - due 2012-08-08].
- # [18:34] <fantasai> dbaron: The idea of this model is that you apply order to the abspos to figure out where it goes in the order, and then use that as the static positoin?
- # [18:34] <fantasai> Tab: yes
- # [18:35] <fantasai> Anton: You're not really treating it as a flex item, you're using order to figure out which item is the next/previous item to attach its position to
- # [18:35] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [18:35] <fantasai> dbaron: So I'm not really happy with adding 100 lines of code for something I haven't heard a use case for
- # [18:35] <fantasai> Tab: Brad produced some things in the mail thread
- # [18:36] <fantasai> fantasai: ...
- # [18:36] <fantasai> glazou: But you are not objecting to the change?
- # [18:36] <fantasai> dbaron: No. Close to it, but no.
- # [18:36] <fantasai> glazou: Ok, let's move on
- # [18:36] <fantasai> Topic: Transforms
- # [18:36] * sylvaing #dbaron { objection: 0.99; /* that was close */ }
- # [18:36] <glazou> http://wiki.csswg.org/topics/transform-interpolation
- # [18:36] * sylvaing weren't we going to go to CR?
- # [18:36] <fantasai> Krit: Issue was ...
- # [18:37] * fantasai fails to catch enough
- # [18:37] <fantasai> Krit: Request from implementers that we don't do that, that we interpolate on each function pair
- # [18:37] <fantasai> Krit: So changed the spec to do interpolate on function pairs
- # [18:37] <fantasai> Krit: For perspective we do matrix decompse then interpolate [??]
- # [18:37] <fantasai> Krit: Thought it'd be a perf issue, but browsers didn't think so
- # [18:38] * stearns sylvain: look a bit upstream - there's a resolution there
- # [18:38] <fantasai> Krit: Have request from smfr that functions along same axis are interpolated, not matrix
- # [18:38] <fantasai> glazou: In thread WebKit says they can't change to the preferred way anyway
- # [18:38] <fantasai> smfr: Could, but would prefer not to
- # [18:38] <fantasai> dbaron: I was originally askin ght espec change back to what it used to be
- # [18:39] <glazou> s/in thread/in wiki
- # [18:39] <fantasai> dbaron: Also worried in general that this spec changes too much in ways that are incompatible with Web content
- # [18:39] * sylvaing stearns: yes, my bad. thanks!
- # [18:39] <fantasai> dbaron: Afraid might have to come back 3 months and have to request revert of changes
- # [18:39] <fantasai> dbaron: But can't say sooner than 3 months
- # [18:39] <fantasai> Krit: Can you be more specific?
- # [18:39] <fantasai> dbaron: There's a lot of content using this
- # [18:40] <fantasai> dbaron: They stuff the result of all prefixed values into the same variable and use it the same way
- # [18:40] <fantasai> dbaron: prefixes isn't getting us anything ehre
- # [18:40] <fantasai> smfr: Risk of interpolating transforms is in cases where we used to not do convert then decompose, cases where we would now if we change the spec
- # [18:40] <fantasai> smfr: The spec is going away from using matrix interpolation, which is a good thing
- # [18:40] <fantasai> dbaron: Yes, worried about changing things *to* matrix interpolation
- # [18:41] <fantasai> Krit: ... feedback on specific part that need changed, I change it
- # [18:41] <fantasai> dbaron: was specified when I implemented it. If it's not anynmore, someone deleted it
- # [18:41] <fantasai> smfr: notion of premitives and derived
- # [18:41] <sylvaing> I am also worried about making incompatible changes at this point
- # [18:41] <fantasai> smfr: e.g. translateX will interolated with translate
- # [18:41] <fantasai> smfr: WebKit didn't implement that
- # [18:41] <fantasai> Krit: ...
- # [18:42] <fantasai> Florian: I'm not very up to speed on how this behaves, but do completely agree with dbaron
- # [18:42] <dbaron> Gecko implemented that a few weeks ago, but we haven't shipped it yet.
- # [18:42] <sylvaing> at a minimum testcases showing some level of interop are warranted
- # [18:42] <fantasai> Florian: Used too much to be changed without trouble
- # [18:42] <sylvaing> (or lack thereof)
- # [18:42] <fantasai> Florian: Need to document things, but not change suboptimal behavior
- # [18:42] <fantasai> smfr: But whose implementation do we pick? Webkit, Gecko, Opera, IE?
- # [18:42] <fantasai> sylvaing: Need to write some test cases to figure that out
- # [18:43] <fantasai> Krit: These changes several months ago,
- # [18:43] <fantasai> Krit: even translatex and translate, was something not specified before, just sayd "transform function of he same type", had to address, what does "same type" even mean
- # [18:43] <fantasai> Krit: So we said "transform function with same name"
- # [18:43] <fantasai> Krit: This is different from editors
- # [18:43] <fantasai> Krit: I'm fine with changing everything to match transform names
- # [18:44] <fantasai> Krit: Still think it's useful for translate functions to interpolate
- # [18:44] <fantasai> Krit: e.g. you have translate() and translateX()
- # [18:44] <fantasai> Krit: with your interpretation we need to decompose to a matrix
- # [18:44] <fantasai> Krit: whereas I would prefer a numeric intrpolation
- # [18:44] <fantasai> smfr: I agree, that's better
- # [18:44] <fantasai> smfr: I think that's safe, because in the direction of less matrix interpolation
- # [18:44] <fantasai> Krit: Same issue with scaleX
- # [18:45] <krit> http://dev.w3.org/csswg/css3-transforms/#transform-primitives
- # [18:45] <fantasai> Krit: Things that are affected are scale(), translate3D() and ??
- # [18:45] <fantasai> Krit: Not sure that's implemented by browsers, I don't think so
- # [18:45] <fantasai> Krit: But from our pov seems useful
- # [18:45] <fantasai> smfr: Seems unlikely that these changes break content
- # [18:45] <fantasai> smfr: one thing that happens when you fall into matrix interpolation is that you lose rotations greater than 360 deg
- # [18:46] <fantasai> smfr: So if someone has a high deg rotation and has one of these functions, you fall into matrix interpolation
- # [18:46] <fantasai> smfr: might be ppl doing that now
- # [18:46] <fantasai> Krit: second request, you said you'd like to interpolate between that and ....??????
- # [18:46] <fantasai> Krit: so rotations around same axis, would like to interpolate
- # [18:46] <fantasai> smfr: WebKit will interpolate between rotate?() and rotate??()
- # [18:47] <fantasai> smfr: And for rotate3d() will check if axes match, otherwise go to matrix path
- # [18:47] <fantasai> smfr: that's just for that 1 function
- # [18:47] <fantasai> smfr: I believe it will fill due to transform individualy in the list if there are rotate3Ds in corresponding places even if axes are different
- # [18:47] * fantasai has no idea what's going on and hopes the minutes sortof make sense
- # [18:47] <fantasai> dbaron is fine with that
- # [18:47] <fantasai> Krit: Everything else, implementers requested it. So should be ok
- # [18:48] <fantasai> Florian: In general I would like to see test cases for these, to check if we are picking the interoperable solution
- # [18:48] * Quits: JohnJansen (qw3birc@128.30.52.28) (Ping timeout)
- # [18:49] <fantasai> Florian: If there is a difference, we need to figure out whether we want good or compatible
- # [18:49] <dbaron> It's really easy to write script tests for interpolation by using a negative transition-delay.
- # [18:49] <fantasai> Florian: These are used a lot out there, so we can't break compatibility
- # [18:49] <fantasai> some question of how to write testcases
- # [18:49] * Quits: drublic (drublic@80.152.164.43) (Client exited)
- # [18:49] <fantasai> fantasai: Can always write a manual test
- # [18:49] * Joins: drublic (drublic@80.152.164.43)
- # [18:49] <fantasai> fantasai: That's good enough to see what browsers are doing for purpose of speccing it
- # [18:50] * Joins: jet (jet@67.169.43.128)
- # [18:50] <fantasai> Topic: CSS2.1
- # [18:50] <glazou> https://lists.w3.org/Archives/Member/w3c-css-wg/2012JulSep/0090.html
- # [18:50] * Joins: JohnJansen (qw3birc@128.30.52.28)
- # [18:50] <fantasai> https://lists.w3.org/Archives/Member/w3c-css-wg/2012JulSep/0101.html
- # [18:51] <glazou> first issue is marked as [A] ?!? shocking :-)
- # [18:51] <fantasai> Anton: First one is follow-up on adding concept of formatting contexts
- # [18:51] <fantasai> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17121#c2 https://www.w3.org/Bugs/Public/show_bug.cgi?id=17121#c5 https://www.w3.org/Bugs/Public/show_bug.cgi?id=17122#c1 https://www.w3.org/Bugs/Public/show_bug.cgi?id=15686#c2
- # [18:51] <fantasai> Anton: Rossen wanted it clearer when a box establishes an inline formatting context
- # [18:51] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
- # [18:51] <fantasai> fantasai: Those edits all look good to me
- # [18:52] <fantasai> Anton: proposal to satisfy Rossen is https://www.w3.org/Bugs/Public/show_bug.cgi?id=17121#c5
- # [18:52] <fantasai> Anton: This was what was implied in the text before, now just explicitly stating it
- # [18:52] <fantasai> Rossen: Change sounds good to me
- # [18:52] * Quits: drublic (drublic@80.152.164.43) (Ping timeout)
- # [18:52] <stearns> looks good to me
- # [18:53] <fantasai> RESOLVED: Accept edits listed above
- # [18:53] <fantasai> Item B
- # [18:53] <fantasai> Anton: We raised issue that there was no interop on whether overflow affects wrapper box or table box
- # [18:53] <fantasai> Anton: Agreed to implement whatever most widely implemented
- # [18:53] <fantasai> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17121#c5
- # [18:53] <antonp> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17505#c6
- # [18:54] <fantasai> Anton: Answer was some UAs are using the table box (Gecko and Trident) whereas WebKit and Opera 12 seemd to apply to wrapper box but doing something weird
- # [18:54] <fantasai> Anton: Which one resolve to?
- # [18:55] <fantasai> fantasai: height applies to table box, so makes sense for overflow to also apply to table box
- # [18:55] <fantasai> dbaron: What values of overflow apply to the table box?
- # [18:55] <fantasai> Anton: Didn't investigate that one. Personally tested overflow: hidden
- # [18:55] <fantasai> Florian: We'll align with whatever sensible behavior we agree on
- # [18:56] <fantasai> fantasai: Do we want to resolve that 'overflow' applies to the table box, and later figure out whether 'overflow: scroll' applies?
- # [18:56] <fantasai> dbaron: I'm reading the spec, and the spec says overflow doesn't apply to tables
- # [18:57] <fantasai> Anton: We have bugs, we know that is kind-of wrong
- # [18:57] <fantasai> Anton: In reality it does apply to tables, it's a question of which box it applies to
- # [18:57] <fantasai> Anton: The formatting context edits will fix the Applies to line
- # [18:57] <fantasai> Anton: But first we have to resolve on is the table box or table wrapper box
- # [18:58] <fantasai> Florian: Test results sound good enough reason to say apply to table box
- # [18:58] * Joins: Rossen (Rossen@131.107.192.20)
- # [18:58] <Zakim> -krit
- # [18:58] <fantasai> Florian: Is anyone disagreeing?
- # [18:58] * krit needs to go
- # [18:59] <fantasai> Bert: Don't see how it would affect table
- # [18:59] <Zakim> -??P45
- # [18:59] <fantasai> fantasai: could have a fixed-height div inside a cell, that has overflowing content
- # [18:59] <Zakim> +[Microsoft.aaa]
- # [18:59] <fantasai> Anton: Question is where do we truncate it, or where do we put the scroll bar
- # [18:59] * Joins: arno (arnog@192.150.10.201)
- # [18:59] <Rossen> Zakim, [Microsoft.aaa] is me
- # [18:59] <Zakim> +Rossen; got it
- # [18:59] <fantasai> Bert: Isn't it easiest to say it doesn't apply?
- # [19:00] <fantasai> glazou: I'm still not hearing any important change or removal on this issue...
- # [19:01] <fantasai> glazou: Do we need more time?
- # [19:01] <fantasai> dbaron: I'm trying to figure out why we do anything for overflow on tables
- # [19:01] <fantasai> dbaron: I haven't found the code yet
- # [19:02] <fantasai> dbaron: I'm concerned about saying that overflow applies to tables
- # [19:03] <fantasai> dbaron: Not sure anyone applies values other than 'hidden' to tables
- # [19:03] <sylvaing> +1
- # [19:03] <fantasai> Anton: The spec used to say it applied to tables, but during the terminology fixes, it accidentally got removed
- # [19:03] <fantasai> Anton: Separate question of whether we want that or not
- # [19:04] <fantasai> Florian: Not exactly excited for 'overflow: paged' applying to tables
- # [19:04] <fantasai> dbaron: Found list of where we support 'overflow: hidden' but not other overflow values --
- # [19:04] <fantasai> dbaron: table cells, tables, and SVG stuff
- # [19:05] <dbaron> table, table cell, svg:svg, svg:foreignObject
- # [19:05] <fantasai> Florian: Is anyone interested in other values on table
- # [19:05] <fantasai> Florian: Or should we just spec that only 'hidden' applies
- # [19:07] <Zakim> -Rossen
- # [19:07] <Zakim> -[Microsoft]
- # [19:07] <fantasai> glazou: suggest deferring to next week
- # [19:07] * Quits: JohnJansen (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:07] <fantasai> Arronei offers to help Anton work on testcases
- # [19:09] <fantasai> Topic: CSS3 Text
- # [19:09] * Rossen can't re-join the call for whatever reason
- # [19:09] <glazou> because it's almost ended
- # [19:09] <fantasai> fantasai: Thinking about publishing WD
- # [19:09] <fantasai> fantasai: Would like people to review
- # [19:09] * sylvaing Rossen, Zakim considers you an invalid declaration
- # [19:09] <Rossen> in that case - talk to you next week :-)
- # [19:09] <Zakim> - +1.604.312.aagg
- # [19:10] <fantasai> fantasai: Also thinking about splitting it, with text decoration parts in separate module
- # [19:10] <Zakim> -dbaron
- # [19:10] <Zakim> -glenn
- # [19:10] <Zakim> -hober
- # [19:10] <rbetts> Zakim, aagg was rbetts
- # [19:10] <Zakim> -SteveZ
- # [19:10] <Zakim> I don't understand 'aagg was rbetts', rbetts
- # [19:10] <Zakim> - +1.281.305.aajj
- # [19:10] <Zakim> -fantasai
- # [19:10] <stearns> antonp: I have a couple questions on your item [C] we didn't get to today
- # [19:10] <Zakim> - +1.408.636.aahh
- # [19:10] <fantasai> szilles: where would parts common to both go?
- # [19:10] <Zakim> -[Microsoft.aa]
- # [19:10] <Zakim> -[Microsoft.a]
- # [19:10] <fantasai> fantasai: There aren't really any
- # [19:10] * Quits: Rossen (Rossen@131.107.192.20) (Quit: Rossen)
- # [19:10] * Quits: Katie (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:10] * Quits: rbetts (rbetts@24.84.208.90) (Quit: rbetts)
- # [19:11] <fantasai> fantasai: It's a very long module
- # [19:11] <fantasai> glazou: Everyone, please add agenda items to F2F wiki
- # [19:11] <Zakim> -florian
- # [19:11] <Zakim> -Bert
- # [19:11] <Zakim> -antonp
- # [19:11] <Zakim> -glazou
- # [19:11] <Zakim> -sylvaing
- # [19:11] <fantasai> Meeting closed.
- # [19:11] <Zakim> -stearns
- # [19:11] <Zakim> -cabanier
- # [19:11] * fantasai requests someone to look over the minutes of the transforms stuff and fix the ??? bits?? please??
- # [19:11] <glazou> fantasai: ask cabanier
- # [19:11] <Zakim> -??P59
- # [19:11] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:11] <Zakim> Attendees were fantasai, glazou, +1.206.675.aaaa, Bert, cabanier, +1.206.324.aabb, sylvaing, +47.23.69.aacc, +1.415.308.aadd, JohnJansen, +1.206.390.aaee, +93550aaff, [Microsoft],
- # [19:11] <Zakim> ... +1.604.312.aagg, stearns, antonp, glenn, +1.408.636.aahh, lstorset, arronei_, +1.415.766.aaii, dbaron, Katie, +1.281.305.aajj, SteveZ, krit, +1.619.846.aakk, hober, Rossen
- # [19:12] * glazou runs
- # [19:12] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
- # [19:12] <stearns> s/cabinier/krit/
- # [19:12] <stearns> for transforms stuff
- # [19:12] <stearns> grr - cabanier
- # [19:13] <cabanier> :-)
- # [19:13] <stearns> antonp: ping
- # [19:15] * Quits: smfr (smfr@173.228.90.242) (Quit: smfr)
- # [19:15] <krit> stearns: was my name on transforms stuff?!?
- # [19:16] <fantasai> krit: I need help fixing holes in the minutes :)
- # [19:16] <krit> oh, looking
- # [19:16] <stearns> krit: look back for ??? in the minutes when you were speaking, and see if you can fill in the details
- # [19:18] <krit> s/So we said "transform function with same name"/So we say "transform function with same name"?/
- # [19:18] * Joins: miketaylr (miketaylr@70.112.101.224)
- # [19:18] <fantasai> lol
- # [19:18] <fantasai> I can fix all the typos and things :)
- # [19:18] <fantasai> it's the missing info that I can't fix!
- # [19:18] <stearns> you can make stuff up
- # [19:18] <krit> s/Things that are affected are scale(), translate3D() and ??/Things that are affected are scale(), translate(), translate3d() and scale3d()
- # [19:19] <krit> stearns: ?
- # [19:19] <stearns> (sorry, lame attempt at humor)
- # [19:19] <krit> ahhh. Don't use make-up :P
- # [19:20] * Quits: lstorset (lastorset@91.203.96.240) (Ping timeout)
- # [19:20] * Quits: florian (florianr@91.203.96.240) (Ping timeout)
- # [19:22] <krit> s/second request, you said you'd like to interpolate between that and ….??????/second request, you said you'd like to interpolate between rotate3d along same axis?/
- # [19:23] <stearns> antonp: added my questions to https://www.w3.org/Bugs/Public/show_bug.cgi?id=18346
- # [19:23] <krit> s/WebKit will interpolate between rotate?() and rotate??()/WebKit will interpolate between rotateZ() and rotate()/
- # [19:24] <krit> fantasai: think that are the important information
- # [19:24] <fantasai> thanks krit!
- # [19:26] <antonp> Thanks Alan, I'll address them
- # [19:27] * Quits: TabAtkins_ (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:31] * Parts: antonp (50a94e63@64.62.228.82)
- # [19:43] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [20:01] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [20:15] * Joins: arno (arnog@192.150.10.201)
- # [20:18] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [20:47] * Joins: jet (jet@67.169.43.128)
- # [20:47] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [20:53] * Joins: jet (jet@67.169.43.128)
- # [20:54] * Quits: dbaron (dbaron@70.36.140.99) (Ping timeout)
- # [20:59] * Joins: aharon (chatzilla@216.239.45.4)
- # [21:11] * sylvaing is now known as sylvaing_away
- # [21:11] <fantasai> TabAtkins: I'm heading to MV to meet up with aharon tomorrow. Want to hang out afterwards and work on stuff?
- # [21:21] * Quits: krit (krit@24.4.186.73) (Ping timeout)
- # [21:31] * sylvaing_away is now known as sylvaing
- # [21:31] * Joins: glenn (gadams@174.29.115.20)
- # [21:41] * Zakim excuses himself; his presence no longer seems to be needed
- # [21:41] * Parts: Zakim (rrs-bridgg@128.30.52.169)
- # [21:58] * Quits: leaverou (leaverou@203.167.141.74) (Quit: leaverou)
- # [22:00] * Joins: drublic (drublic@95.115.37.162)
- # [22:01] * Quits: dstorey (Adium@67.180.84.179) (Quit: Leaving.)
- # [22:12] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [22:14] * Quits: arno (arnog@192.150.10.201) (Quit: Leaving.)
- # [22:18] * Joins: glenn (gadams@174.29.115.20)
- # [22:27] * Joins: dbaron (dbaron@206.15.76.122)
- # [22:29] * Joins: arno (arnog@192.150.10.201)
- # [22:35] * Quits: cabanier (cabanier@192.150.22.55) (Quit: Leaving.)
- # [22:57] * Quits: glenn (gadams@174.29.115.20) (Client exited)
- # [23:27] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [23:42] * Joins: dstorey (Adium@67.180.84.179)
- # [23:54] * Parts: aharon (chatzilla@216.239.45.4)
- # [23:56] * Quits: Ms2ger (Ms2ger@81.242.172.208) (Quit: nn)
- # Session Close: Thu Aug 02 00:00:00 2012
The end :)