Options:
- # Session Start: Wed Mar 21 00:00:00 2012
- # Session Ident: #css
- # [00:00] * Quits: arronei_ (arronei@131.107.0.116) (Quit: arronei_)
- # [00:02] * Quits: jet (jet@67.169.43.128) (Ping timeout)
- # [00:04] * Joins: arronei (arronei@131.107.0.89)
- # [00:10] * Joins: jet (jet@67.169.43.128)
- # [00:11] * Quits: lgombos__ (Laszlo@86.217.58.90) (Ping timeout)
- # [00:24] * Quits: tantek (tantek@70.36.139.112) (Quit: tantek)
- # [00:32] * Quits: arronei (arronei@131.107.0.89) (Quit: arronei)
- # [00:52] <TabAtkins_> fantasai: I'm revising the wiki page to remove mentions of the out-of-document element() stuff.
- # [00:53] <TabAtkins_> Wait, nm, got it.
- # [00:56] * Quits: danielfilho (danielfilh@187.31.77.7) (Ping timeout)
- # [01:00] * Joins: danielfilho (danielfilh@187.31.77.7)
- # [01:02] * Quits: drublic (drublic@93.132.228.5) (Client exited)
- # [01:02] <fantasai> TabAtkins_: btw, I think we'll need to drop rtl/ltr as well
- # [01:03] <fantasai> TabAtkins_: Kenny raised some good design-level issues against it
- # [01:06] <fantasai> TabAtkins_: There was also an issue on whether image-orientation should be inherited
- # [01:06] <fantasai> TabAtkins_: which seems like a reasonable idea...
- # [01:06] <TabAtkins_> That'll make the bidi folk sad, but I"m not overly against it.
- # [01:07] <fantasai> yeah, I know, but I think making it a better-designed feature is worth the wait :)
- # [01:07] <TabAtkins_> kk
- # [01:07] <TabAtkins_> What's this about inheriting image-orientation?
- # [01:07] <fantasai> image-orientation doesn't inherit
- # [01:07] <TabAtkins_> Yes.
- # [01:07] <fantasai> Kenny suggested maybe it should
- # [01:07] <TabAtkins_> Where?
- # [01:07] * fantasai looks for the email
- # [01:08] * fantasai needs to update the DoC with all of Kenny's off-hand comments that raise major issue.s..
- # [01:08] <TabAtkins_> hehe
- # [01:08] <fantasai> http://lists.w3.org/Archives/Public/www-style/2012Mar/0397.html
- # [01:09] <TabAtkins_> I don't see anything about inheriting ther.
- # [01:09] <TabAtkins_> Oh wait, now I see it.
- # [01:09] <fantasai> right :)
- # [01:10] <TabAtkins_> I have no problem with making it inherit.
- # [01:10] <fantasai> k
- # [01:10] <fantasai> I'll file it and update the spec.
- # [01:11] <fantasai> Looks like the old draft of css3-page marked "inherited" as "N/A", so we're not even conflicting with it ^_^
- # [01:11] * fantasai supposes the editors didn't know "N/A" is not a valid value for "inherited"...
- # [01:19] * Joins: glenn_ (gadams@71.218.126.59)
- # [01:20] <TabAtkins_> I'd suppose that as well.
- # [01:21] * Quits: glenn (gadams@71.218.126.59) (Ping timeout)
- # [01:23] <fantasai> k, checked in change, DoC update, and wiki update http://wiki.csswg.org/spec/css3-images#inheritance-of-image-orientation
- # [01:23] <fantasai> hopefully it's non-controversial...
- # [01:26] * Joins: arronei (arronei@131.107.0.98)
- # [01:34] <fantasai> use case that object-fit's weird rules is trying to solve:
- # [01:34] <fantasai> photo album
- # [01:34] <fantasai> each picture gets a square to sit in
- # [01:35] <TabAtkins_> I absolutely understand the use-case.
- # [01:35] <TabAtkins_> I just think this is 100% the wrong way to do it.
- # [01:35] <fantasai> must fit inside the square
- # [01:35] <fantasai> must maintain aspect ratio
- # [01:35] <fantasai> want to give photo a drop-shadow
- # [01:35] * fantasai knows, just making notes to self
- # [01:35] <TabAtkins_> kk
- # [01:35] <fantasai> or put a border around it
- # [01:37] <fantasai> Maybe we can solve this by adding a 'resize' keyword that asks object-fit to resize the content box to match the concrete object size?
- # [01:37] * fantasai not now, in the future
- # [01:40] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [01:41] <TabAtkins_> Using object-fit at all is a mistake.
- # [01:42] <TabAtkins_> It assumes that only "objects" will ever have intrinsic aspect ratios.
- # [01:42] * Joins: jet (jet@67.169.43.128)
- # [01:43] <fantasai> we picked the name to be generic enough that SVG could use it on arbitrary SVG elements
- # [01:43] <fantasai> so I think it's fine to use it for anything else we need it for in the future
- # [01:44] * fantasai is opposed to making a new property just because you want to apply it to <div>s with an aspect-ratio
- # [01:46] <TabAtkins_> Do you have a reasonable argument as to why it *shouldn't* apply?
- # [01:59] <TabAtkins_> fantasai: Of course, it's possible to inject the same kind of keyword into aspect-ratio, so you just have the same ability (hopefully triggered in the same way) from two different properties, depending on what kind of element you are.
- # [02:06] <TabAtkins_> fantasai: Do we just want to drop ltr/rtl and file it as an issue to look at?
- # [02:13] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [02:20] * Quits: lhnz (lhnz@188.223.83.48) (Ping timeout)
- # [02:20] * Joins: lhnz (lhnz@188.223.83.48)
- # [02:32] * sylvaing is now known as sylvaing_away
- # [02:49] * Joins: jet (jet@67.169.43.128)
- # [02:52] * Quits: jet (jet@67.169.43.128) (Ping timeout)
- # [02:57] * Joins: jet (jet@67.169.43.128)
- # [03:00] * Quits: jet (jet@67.169.43.128) (Ping timeout)
- # [03:06] * Quits: lhnz (lhnz@188.223.83.48) (Ping timeout)
- # [03:06] * Joins: lhnz (lhnz@188.223.83.48)
- # [03:27] * Joins: jet (jet@67.169.43.128)
- # [03:54] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [04:00] * Joins: jet (jet@67.169.43.128)
- # [04:03] * Joins: jet_ (jet@67.169.43.128)
- # [04:03] * Quits: jet (jet@67.169.43.128) (Connection reset by peer)
- # [04:03] * jet_ is now known as jet
- # [04:06] * Quits: lhnz (lhnz@188.223.83.48) (Connection reset by peer)
- # [04:06] * Joins: lhnz (lhnz@188.223.83.48)
- # [04:12] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [05:03] <fantasai> TabAtkins_: Yes, that's what I said
- # [05:03] <fantasai> TabAtkins_: what shouldn't apply? /me confused
- # [06:23] * Joins: kennyluck (kennyluck@114.43.114.30)
- # [07:10] * Joins: jet (jet@67.169.43.128)
- # [07:11] * Joins: jet_ (jet@67.169.43.128)
- # [07:11] * Quits: jet (jet@67.169.43.128) (Connection reset by peer)
- # [07:11] * jet_ is now known as jet
- # [07:12] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [07:18] * Joins: jet (jet@67.169.43.128)
- # [07:20] * Quits: jet (jet@67.169.43.128) (Connection reset by peer)
- # [07:20] * Joins: jet (jet@67.169.43.128)
- # [07:30] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [07:31] * Joins: shepazutoo (shepazu@128.30.52.169)
- # [07:33] * Quits: shepazu (shepazu@128.30.52.169) (Ping timeout)
- # [07:33] * shepazutoo is now known as shepazu
- # [07:42] * Quits: glenn_ (gadams@71.218.126.59) (Client exited)
- # [08:51] * Quits: leaverou (leaverou@67.180.84.179) (Quit: leaverou)
- # [09:02] * Joins: logbot (logbot@110.173.227.145)
- # [09:08] * Joins: jet (jet@67.169.43.128)
- # [09:11] * Quits: jet (jet@67.169.43.128) (Ping timeout)
- # [09:15] * Joins: jet (jet@67.169.43.128)
- # [09:16] * Joins: lgombos_ (Laszlo@86.217.58.90)
- # [09:22] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [09:58] * Joins: miketaylr (miketaylr@213.236.208.247)
- # [10:07] * Joins: florianr (florianr@213.236.208.22)
- # [10:34] * Joins: drublic (drublic@95.115.62.191)
- # [10:42] * Joins: SimonSapin (simon@82.232.219.95)
- # [10:54] * Joins: Ms2ger (Ms2ger@193.190.253.146)
- # [12:25] * Quits: Ms2ger (Ms2ger@193.190.253.146) (Quit: Leaving)
- # [12:25] * Joins: Ms2ger (Ms2ger@193.190.253.146)
- # [12:58] * miketaylr is now known as miketaylr|
- # [13:43] * Quits: Ms2ger (Ms2ger@193.190.253.146) (Ping timeout)
- # [15:27] * miketaylr| is now known as miketaylr||
- # [15:35] * Joins: ChrisL (ChrisL@128.30.52.169)
- # [15:38] * Quits: logbot (logbot@110.173.227.145) (Client exited)
- # [15:38] * Joins: logbot (logbot@110.173.227.145)
- # [15:43] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
- # [15:46] * Joins: SimonSapin (simon@82.232.219.95)
- # [15:47] * Quits: ChrisL (ChrisL@128.30.52.169) (Ping timeout)
- # [15:48] * Joins: Ms2ger (Ms2ger@81.242.178.33)
- # [15:48] * Joins: ChrisL (ChrisL@128.30.52.169)
- # [16:04] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
- # [16:04] * Joins: ChrisL2 (ChrisL@128.30.52.169)
- # [16:07] * Joins: SimonSapin (simon@82.232.219.95)
- # [16:08] * Quits: ChrisL (ChrisL@128.30.52.169) (Ping timeout)
- # [16:10] * Joins: glenn (gadams@71.218.126.59)
- # [16:14] * Quits: ChrisL2 (ChrisL@128.30.52.169) (Quit: Fire on main board error, client combusted)
- # [16:27] * Joins: mollydotcom (mollyh@68.231.165.244)
- # [16:27] * Joins: glazou (glazou@82.247.96.19)
- # [16:28] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [16:28] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
- # [16:28] <RRSAgent> logging to http://www.w3.org/2012/03/21-css-irc
- # [16:28] <glazou> Zakim, this will Style
- # [16:28] <Zakim> I don't understand 'this will Style', glazou
- # [16:28] <glazou> Zakim, this will be Style
- # [16:28] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 40 minutes
- # [16:28] <glazou> RRSAgent, make logs public
- # [16:28] <RRSAgent> I have made the request, glazou
- # [16:58] * sylvaing_away is now known as sylvaing
- # [17:01] <Zakim> Style_CSS FP()12:00PM has now started
- # [17:01] <Zakim> +??P0
- # [17:02] * Joins: dstorey_ (qw3birc@128.30.52.28)
- # [17:02] <glenn> zakim, ??p0 is me
- # [17:02] <Zakim> +glenn; got it
- # [17:02] * Quits: dstorey_ (qw3birc@128.30.52.28) (Quit: Page closed)
- # [17:02] * Joins: tantek (tantek@70.36.139.112)
- # [17:02] <Zakim> +sylvaing
- # [17:03] <Zakim> +??P12
- # [17:03] <glazou> Zakim, ??P12 is me
- # [17:03] <Zakim> +glazou; got it
- # [17:04] <Zakim> +[IPcaller]
- # [17:04] <florianr> Zakim, I am [IPcaller]
- # [17:04] <Zakim> ok, florianr, I now associate you with [IPcaller]
- # [17:04] <Zakim> +Molly_Holzschlag
- # [17:05] * Joins: dstorey (Adium@67.180.84.179)
- # [17:05] * Joins: antonp (50a94e63@64.62.228.82)
- # [17:05] * Joins: dbaron (dbaron@173.228.85.36)
- # [17:05] <Zakim> -glenn
- # [17:06] <Zakim> +??P0
- # [17:06] <glenn> zakim, ??p0 is me
- # [17:06] <Zakim> +glenn; got it
- # [17:06] <glenn> zakim, mute me
- # [17:06] <Zakim> glenn should now be muted
- # [17:06] * Joins: smfr (smfr@173.228.90.231)
- # [17:07] <Zakim> +??P31
- # [17:07] <Zakim> +[Microsoft]
- # [17:07] <Zakim> + +1.415.766.aaaa
- # [17:07] <dbaron> Zakim, aaaa is dbaron
- # [17:07] <Zakim> +dbaron; got it
- # [17:08] <Zakim> + +1.206.550.aabb
- # [17:08] <Zakim> +hober
- # [17:08] <stearns> zakim, aabb is me
- # [17:08] <Zakim> +stearns; got it
- # [17:08] <Zakim> +smfr
- # [17:08] * Joins: JohnJansen (qw3birc@128.30.52.28)
- # [17:08] <JohnJansen> Zakim, Microsoft has JohnJansen
- # [17:08] <Zakim> +JohnJansen; got it
- # [17:09] * Joins: bradk (bradk@99.7.175.117)
- # [17:09] * Joins: oyvind (oyvinds@213.236.208.22)
- # [17:09] <Zakim> + +1.408.421.aacc
- # [17:10] * dbaron Zakim, who is on the phone?
- # [17:10] <dstorey> zakim, +1.408.421.aacc is dstorey
- # [17:10] <Zakim> + +8521616aadd
- # [17:10] <antonp> having trouble dialing in....
- # [17:10] * Zakim sees on the phone: sylvaing, glazou, [IPcaller], Molly_Holzschlag, glenn (muted), ??P31, [Microsoft], dbaron, stearns, hober, smfr, +1.408.421.aacc, +8521616aadd
- # [17:10] * Zakim [Microsoft] has JohnJansen
- # [17:10] <antonp> I'm in!
- # [17:10] * Joins: krit (Adium@192.150.10.201)
- # [17:11] <Zakim> +dstorey; got it
- # [17:11] <Zakim> + +1.415.832.aaee
- # [17:11] <krit> Zakim, aaee is me
- # [17:11] <Zakim> +antonp
- # [17:11] <krit> Zakim, +1.415.832.aaee is me
- # [17:12] <Zakim> +krit; got it
- # [17:12] <Zakim> sorry, krit, I do not recognize a party named '+1.415.832.aaee'
- # [17:12] * Zakim hears +8521616aadd's hand up
- # [17:12] * Zakim sees +8521616aadd on the speaker queue
- # [17:12] <fantasai> Zakim, aadd is me
- # [17:12] <Zakim> +fantasai; got it
- # [17:12] <Zakim> +[Microsoft.a]
- # [17:14] <glazou> ScribeNick: mollydotcom
- # [17:14] <sylvaing> extra agenda item from overtime 2 weeks ago: whether to move gradients to css3-gradients
- # [17:14] * Joins: Rossen (Rossen@131.107.174.165)
- # [17:14] <Zakim> +bradk
- # [17:14] <mollydotcom> Daniel: Asking for comments about proposal
- # [17:15] <dbaron> Dirk: propose publishing new draft of css3-transforms
- # [17:15] <Zakim> +[Microsoft.aa]
- # [17:15] <mollydotcom> Simon: clarifying language
- # [17:15] <Zakim> -hober
- # [17:15] <mollydotcom> Daniel: Objections? Comments?
- # [17:15] <glazou> smfr: remove green section
- # [17:15] * fantasai notes that Flexbox, Variables, and Grid Layout were supposed to be published already, how many are going to make it for Thursday?
- # [17:15] * fantasai because they're not published yet
- # [17:15] <mollydotcom> Resolution: New Working Draft for Transforms
- # [17:16] <mollydotcom> Daniel: Next up Sylvain and Gradients
- # [17:16] <dbaron> Zakim, who is on the phone?
- # [17:16] <Zakim> On the phone I see sylvaing, glazou, [IPcaller], Molly_Holzschlag, glenn (muted), ??P31, [Microsoft], dbaron, stearns, smfr, dstorey, fantasai, krit, antonp, [Microsoft.a], bradk,
- # [17:16] <Zakim> ... [Microsoft.aa]
- # [17:16] <Zakim> [Microsoft] has JohnJansen
- # [17:16] * Joins: ChrisL (ChrisL@128.30.52.169)
- # [17:16] <Rossen> Zakim, [Microsoft] has me
- # [17:16] <Zakim> +Rossen; got it
- # [17:16] <mollydotcom> Daniel: conversation regarding Elika's concerns re Flexbox, Variables and Grid Layout
- # [17:17] * glazou will sort that out with Bert
- # [17:17] <mollydotcom> Sylvain: Open issues on all the features in the spec
- # [17:17] <Zakim> +ChrisL
- # [17:17] <glazou> s/spec/gradients
- # [17:17] <mollydotcom> Sylvain: Only one implementation, so maybe we want to take gradients into their own draft
- # [17:17] <Zakim> +[Apple]
- # [17:17] <mollydotcom> Sylvain: We should make a decision on this
- # [17:18] <hober> Zakim, Apple has hober
- # [17:18] <Zakim> +Bert
- # [17:18] <Zakim> +hober; got it
- # [17:18] * mollydotcom says say your name before you speak for your poor scribe please
- # [17:18] * fantasai this is Florian
- # [17:18] <mollydotcom> Florian: CR itself doesn't have to be rushed
- # [17:19] <mollydotcom> Sylvain: I think that the feature has been around long enough, we're sitting on our hands waiting
- # [17:19] <mollydotcom> Florian: Discussion of CR v. PR and where resolutions should go
- # [17:20] <mollydotcom> Sylvain: In violent agreement, but I want to get it to CR as soon as we can
- # [17:20] <Zakim> +SteveZ
- # [17:20] <mollydotcom> Fantasai: Can we focus on resolving issues?
- # [17:20] <dbaron> um, that makes what order we discuss the issues in a pretty big factor
- # [17:20] <mollydotcom> Daniel: Moving to issues right now
- # [17:21] <ChrisL> link to issues list?
- # [17:21] <florianr> http://wiki.csswg.org/spec/css3-images
- # [17:22] <mollydotcom> Link to issues list: http://wiki.csswg.org/spec/css3-images
- # [17:22] <mollydotcom> Elika: Directional images - design issues we can't address correctly that quickly, defer?
- # [17:22] * ChrisL that was me
- # [17:22] <mollydotcom> Daniel: No Objections
- # [17:23] * hober and then me
- # [17:23] <mollydotcom> RESOLVED: defer directional images
- # [17:23] <mollydotcom> Elika: Object-fit / Changing size of content box
- # [17:24] * Ms2ger fantasai the page says "Dispositin of Comments.", needs an 'o' in there :)
- # [17:24] <Zakim> + +47.21.65.aaff
- # [17:25] <glazou> mollydotcom: are you correctly minuting this?
- # [17:25] * ChrisL suggests asking Florian to summarise in IRC
- # [17:26] <mollydotcom> no
- # [17:26] <mollydotcom> Florian: please summarize
- # [17:26] <fantasai> ScribeNick: fantasai
- # [17:27] <mollydotcom> Florian: Two concerns. 1st case seems useful, but not always the desired behavior
- # [17:27] <fantasai> Florian: We have two concerns about the effect. First, the use case that's described for it seems useful, but I'm not convinced that's always the behavior you want. Might want to turn it on or off.
- # [17:28] * glazou grrrs
- # [17:28] <fantasai> Florian: Second case is if you have max-width to 100px and width is less that, it will enlarge the image up to 100px
- # [17:29] <mollydotcom> Florian: Second case is if you have max-width to 100px and width is less that, it will enlarge the image up to 100px
- # [17:29] <fantasai> Florian: Among the ppl who understand this text, am I wrong to think that it says that?
- # [17:29] <mollydotcom> Florian: Am I wrong to think that the text says that?
- # [17:29] <fantasai> dbaron: It does say that you enlarge images in a bunch of cases, but I think... you're talking about wanting a constraint that shrinks/enlarges only if necessary?
- # [17:30] <mollydotcom> dbaron: It does say that you enlarge images in a bunch of cases, but I think... you're talking about wanting a constraint that shrinks/enlarges only if necessary?
- # [17:30] <fantasai> Florian: max-width + object-fit: contain causes your image to grow.
- # [17:30] <fantasai> Florian: It might be useful, but certainly counter-intuitive
- # [17:30] <mollydotcom> Florian: max-width and object: fit: contain doesn't seem useful, counter-intuitive
- # [17:30] <fantasai> Florian: So my conclusion based on that, I think we should split that behavior out of object-fit so that you have that behavior but it's not confused with object-fit contain and cover
- # [17:31] <fantasai> Molly: Sounds like a language problem
- # [17:31] <mollydotcom> Molly: Sounds like a language problem to me
- # [17:31] <mollydotcom> Florian: So my conclusion based on that, I think we should split that behavior out of object-fit so that you have that behavior but it's not confused with object-fit contain and cover
- # [17:31] <mollydotcom> Elika: Add a keyword that determines the behavior
- # [17:31] <mollydotcom> Elika: to control resizing the box (in level four)
- # [17:31] <fantasai> fantasai: Drop the paragraph, add a keyword in level 4
- # [17:32] <mollydotcom> Florian: Drop the paragraph, add a keyword in level 4
- # [17:32] <fantasai> dbaron: I think it's good to drop this to L4
- # [17:32] <fantasai> dbaron: I have comments on the feature for L4, not spend time on that right now.
- # [17:32] <Rossen> +1 for moving it to level 4
- # [17:32] <sylvaing> not clear on what the resolution is....
- # [17:32] <fantasai> sfmr: We have a scale-down keyword...
- # [17:32] <mollydotcom> Elika: Do we have a resolution on dropping the text?
- # [17:33] <tantek> scribe, I am on IRC only this morning for today's meeting
- # [17:33] <fantasai> Florian: The first paragraph of contain and cover is dropped, use cases it solves moved to L4
- # [17:33] <mollydotcom> Florian, the paragraph goes away, add a keyword in level 4
- # [17:33] <mollydotcom> Daniel: No objection?
- # [17:33] <fantasai> RESOLVED: Dropped
- # [17:33] * dbaron Zakim, who is noisy?
- # [17:33] <mollydotcom> RESOLVED: Paragraph Dropped
- # [17:33] * Zakim dbaron, listening for 10 seconds I heard sound from the following: fantasai (89%), [IPcaller] (37%)
- # [17:34] * mollydotcom says thanks tantek
- # [17:34] <fantasai> fantasai summarizes issue about image-fit/image-position aliases of object-fit/object-position
- # [17:34] <fantasai> which were allowed for printers
- # [17:35] <fantasai> Florian: I think it's useful to specify such things so that new UAs can be backwards-compatible
- # [17:35] <fantasai> Florian: But also at the F2F we discussed what an alias means, and we don't have a definition.
- # [17:35] <fantasai> Florian: If we allow an alias, we should define it, and discussing that might take awhile.
- # [17:36] <fantasai> Florian: This is not the spec to spend this time.
- # [17:36] <dbaron> fantasai: How about we shift this to the print profile
- # [17:36] <dbaron> fantasai: It's printer specific -- not a backwards-compat issue on the Web
- # [17:37] <fantasai> dbaron: I'd also prefer not having aliases here.
- # [17:37] <fantasai> dbaron: I would prefer C to B, but I don't think we need to make that decision right now.
- # [17:37] <fantasai> Florian: We can drop it from Print Profile later if it's problematic
- # [17:37] <fantasai> glazou: Can you live with B?
- # [17:37] <fantasai> dbaron: I suppose so.
- # [17:38] <fantasai> RESOLVED: Shift to Print Profile
- # [17:39] <fantasai> fantasai summarizes issue 14
- # [17:40] <fantasai> Florian: Don't know enough about the topic. Sounds reasonable to me.
- # [17:40] <Zakim> -krit
- # [17:40] <fantasai> dbaron: Sounds reasonable to me, should probably run it by the Media Fragments group
- # [17:40] * Quits: krit (Adium@192.150.10.201) (Quit: Leaving.)
- # [17:40] <fantasai> ChrisL: We could; should I take an action to do that?
- # [17:41] <mollydotcom> Florian: Is there another solution?
- # [17:41] <mollydotcom> dbaron: Has anyone read the media fragments enough to understand?
- # [17:41] <fantasai> http://www.w3.org/TR/media-frags/#error-uri
- # [17:41] <mollydotcom> dbaron: If there isn't any behavior there I don't see any need to run it by the group
- # [17:42] <fantasai> RESOLVED: Edits approved for issue 14
- # [17:42] <florianr> http://wiki.csswg.org/spec/css3-images
- # [17:42] <mollydotcom> :)
- # [17:42] <florianr> http://wiki.csswg.org/spec/css3-images#image-and-invalid-fragments
- # [17:42] <dbaron> "If a URL uses a fragment identifier syntax that the implementation does not understand, or which the implementation does not consider valid for that type of image, the URL must be treated as representing an invalid image. This error-handling is limited to image(), and not in the definition of URL, for legacy compat reasons."
- # [17:42] <mollydotcom> Fantasai: Image orientation overview
- # [17:43] * miketaylr|| is now known as miketaylr|||
- # [17:43] * miketaylr||| is now known as miketaylr||||
- # [17:43] <fantasai> fantasai summarizes issue 42
- # [17:44] <mollydotcom> RESOLVED: Is inheritable
- # [17:44] <mollydotcom> Fantasai: Elements, lot of issues here - 2 options: Resolve all issues; or move to Level 4
- # [17:45] <mollydotcom> Fantasai: Tab removed element references - if anyone has any objection to that, please speak up
- # [17:45] * sylvaing pops the champagne for howcome
- # [17:45] * glazou this is a day to remember !
- # [17:45] <Zakim> -??P31
- # [17:46] <mollydotcom> Hakon: It seems that this other issue with the elements - I would agree this doesn't sound highly intuitive
- # [17:46] <Zakim> +??P14
- # [17:46] <Zakim> - +47.21.65.aaff
- # [17:46] <Zakim> -SteveZ
- # [17:46] <fantasai> Florian: I think I actually prefer proposal B, which is to defer element() to CSS4. I am not convinced we can go through all that in a short amount of time.
- # [17:46] <mollydotcom> Florian: Before we get into all issues, I think we might consider moving to Level 4 - I am not convinced
- # [17:46] <mollydotcom> we have enough time
- # [17:46] * Quits: miketaylr|||| (miketaylr@213.236.208.247) (Quit: Leaving...)
- # [17:46] <fantasai> Florian: Wrt short, I mean a number of telecons we can agree to right now
- # [17:46] <Zakim> + +47.21.65.aagg
- # [17:47] <fantasai> glazou: Still discussing the intimacy(?) of this feature; probably means it's not stable enough in everyone's mind.
- # [17:47] <dbaron> Zakim, aagg is howcome
- # [17:47] <Zakim> +howcome; got it
- # [17:47] <fantasai> Florian: We're discussing whether we need to discuss what you (howcome) said
- # [17:47] <fantasai> dbaron: I think a bunch of these issues aren't all that hard.
- # [17:47] <fantasai> dbaron: we've put them to the end of the list
- # [17:48] <fantasai> Florian: If we can handle by end of next telecon or 3, fine. But not unbounded number of telecons.
- # [17:48] <fantasai> glazou: let's not spend time on meta-discussion
- # [17:48] <fantasai> dbaron: So I don't think the GCPM and Images conflict. One defines... well, ok, yeah.
- # [17:49] <fantasai> dbaron: nevermind
- # [17:49] <fantasai> dbaron: I think the element name makes more sense in almost all the contexts its used. The one exception is 'content', which takes images and a bunch of other things.
- # [17:50] <fantasai> dbaron: Could say that element() only works inside image() for 'content', but everywhere else ok on it's own.
- # [17:50] <fantasai> fantasai: that seems weird
- # [17:50] <stearns> the number of reviews being solicited suggests to me that more issues will crop up, which pushes me towards deferral
- # [17:50] * Joins: krit (Adium@192.150.10.201)
- # [17:51] <fantasai> fantasai: So.. options include defining away the conflict in 'content' somehow, dbaron's proposal, renaming one or the other, or maybe merging the element() functionality into image() somehow.
- # [17:52] <fantasai> Florian: should we move to other issues?
- # [17:53] <glazou> http://dev.w3.org/csswg/css3-images/#decorated-bounding-box
- # [17:53] * sylvaing reads bounding box as 'bouncing box' almost every single time. Very distracting.
- # [17:53] <fantasai> fantasai: Issue was bounding box is undefined. So we added a definition, and used the border image area as the basis of that definition
- # [17:53] <fantasai> fantasai: So the question is, does the WG approve of this.
- # [17:53] <fantasai> fantasai: we chose the border image area rather than the border box so that border images wouldn't get clipped if they were outset
- # [17:54] <Zakim> -[Microsoft]
- # [17:54] <fantasai> Florian: Sounds ok to me, but far from sure I have my head around all the implications.
- # [17:54] <fantasai> dbaron: I want to run this by roc
- # [17:54] <dbaron> dbaron: possible that it should be a little more related to 'overflow'
- # [17:55] * Parts: krit (Adium@192.150.10.201)
- # [17:56] <fantasai> fantasai: This parallels the SVG concept of "decorated bounding box", which includes not just the geometry of the of the svg element, but also the half of the stroke that sits outside it.
- # [17:56] <fantasai> bradk: Should this include outline?
- # [17:56] <ChrisL> outline takes no space (or at least does not cause reflow)
- # [17:56] <fantasai> bradk: Wouldn't want outline to clip
- # [17:56] <fantasai> fantasai: That would make the behavior undefined, since outline position is not defined.
- # [17:57] <fantasai> Rossen: outline doesn't include scrolling extents, so why include it here
- # [17:57] <fantasai> smfr: Then you get into issues of should it include box-shadow, filter effects that cause spilling, etc.
- # [17:57] <fantasai> Rossen: Seems odd to me to take into account outines for bounding boxes
- # [17:58] <fantasai> dbaron: What is this used for?
- # [17:58] <fantasai> fantasai: calculating the size of the element and its clipping bounds
- # [17:58] <fantasai> s/element/image/
- # [17:59] <dbaron> Brad: I don't see how 'outline' is different from 'border-image'
- # [17:59] <dbaron> Florian: I'm sure I don't want outlines in there
- # [17:59] <glenn> pixels from rasterizing glyphs also (may and often do) fall outside their bounding box; would another term be needed for this?
- # [18:00] <fantasai> dbaron: What does Gecko do?
- # [18:00] <Zakim> +??P17
- # [18:00] * fantasai doesn't know
- # [18:00] <Zakim> -howcome
- # [18:00] <glenn> zakim, ??p17 is me
- # [18:00] <Zakim> +glenn; got it
- # [18:01] <fantasai> fantasai: Also a question of what's the right behavior here. In most cases border image area matches border area. Question is what's best to do in cases where they mismatch
- # [18:01] <fantasai> No conclusion here, moving on.
- # [18:01] <dbaron> fantasai: next issue is issue 27, Allow image() to accept element() so that authors can specify fallbacks
- # [18:02] <dbaron> dbaron: sounds good to me
- # [18:02] <dbaron> Florian: sounds ok
- # [18:02] <fantasai> RESOLVED: accept changes for issue 27
- # [18:02] <dbaron> fantasai: Next issue is issue 26, specifying handling of varying size pages
- # [18:03] <dbaron> fantasai: propose align page content boxes by their start content edges before taking the bounding box.
- # [18:04] <dbaron> dbaron: sounds reasonable to me
- # [18:04] <fantasai> fantasai: Other possible options are center-alignment, or end-alignment, or left-alignment, or right-alignment
- # [18:04] <dbaron> Glenn: so the border on a page is more like outline than border in the normal CSS box model?
- # [18:05] <dbaron> fantasai: It's like border, but it's not part of the document formatting.
- # [18:05] <fantasai> fantasai: it's more like decorating the window or chrome of the browser; doesn't play with document at all
- # [18:06] <bradk> re: "In most cases border image area matches border area." Without border-image, wouldn't the image be clipped to the curves when there is border-radius? Would the corner behavior depend on if there was a non-initial value of border-image?
- # [18:06] <fantasai> bradk, bounding box is always rectangular
- # [18:07] <fantasai> RESOLVED: accept text for issue 26 pending alexmog and vincents' approval
- # [18:07] <bradk> OK. Actually, if border box is used, it would still be rectangular, but with transparent areas outside the borde-radius corners. So, never mind.
- # [18:08] <fantasai> Florian: I don't think we can solve all these issues. I'm fine if we can solve all the issue by next telecon. but not if it's an unbounded task
- # [18:08] <fantasai> dbaron: I suppose so
- # [18:08] <dbaron> I'd sort of like to hear Tab's opinion
- # [18:08] <oyvind> I find it a bit hard to believe that these are the only issues...
- # [18:08] <fantasai> sylvain +1 to Florian
- # [18:09] * Joins: danielweck (danielweck@86.158.25.225)
- # [18:09] <mollydotcom> "editor doesn't mean decider" - Glazou
- # [18:09] * mollydotcom likes that quote
- # [18:10] * sylvaing editing: with great responsibility comes no power
- # [18:10] <dbaron> dbaron: element() is NOT the only section of this spec that's been substantially rewritten since last call
- # [18:11] <glenn> editor's propose, we members dispose
- # [18:12] <fantasai> discussion of whether to push element() to L4
- # [18:13] <fantasai> - how much time is necessary to resolve issues and get necessary reviews
- # [18:13] <fantasai> - how unstable is the feature, how many more issues might show up
- # [18:13] <fantasai> - etc.
- # [18:13] <danielweck> great...I misread the UTC/GMT concall time ... <idiot-emoticon>
- # [18:14] <Zakim> -ChrisL
- # [18:14] <fantasai> glazou: gradients is urgent. element() is not.
- # [18:14] <ChrisL> @danielweck never mind its all back to normal next week
- # [18:14] <dbaron> (argument between glazou and molly)
- # [18:14] <fantasai> glazou: Given remaining issues and discussion today, I support deferring element.
- # [18:14] <fantasai> Florian: how do we resolve on this?
- # [18:14] <mollydotcom> I support deferring element.
- # [18:14] * Bert wondering if a generic way to duplicate elements wouldn't make both versions of element() redundant. Something like: body {grid: "a . b"} div.dup {flow: a, b} /* flow into both a and b */
- # [18:15] <fantasai> Straw poll
- # [18:15] <stearns> +1 to defer
- # [18:15] <glazou> Zakim, who is on the phone ?
- # [18:15] <Zakim> On the phone I see sylvaing, glazou, [IPcaller], Molly_Holzschlag, glenn (muted), dbaron, stearns, smfr, dstorey, fantasai, antonp, [Microsoft.a], bradk, [Microsoft.aa], [Apple],
- # [18:15] <danielweck> ChrisL: okay thanks
- # [18:15] <Zakim> ... Bert, ??P14, glenn.a
- # [18:15] <Zakim> [Apple] has hober
- # [18:15] <fantasai> Poll: defer or work on element(
- # [18:15] <fantasai> sylvaing: defer
- # [18:15] <glenn> defer
- # [18:15] <fantasai> glazou: defer
- # [18:15] <fantasai> Florian: defer
- # [18:15] <fantasai> Molly: defer
- # [18:15] <fantasai> glenn: defer
- # [18:15] <arronei> arronei: defer
- # [18:15] <fantasai> dbaron: work on it, but ok with deferring
- # [18:15] <fantasai> alan: defer
- # [18:15] <fantasai> smfr: defer
- # [18:15] <fantasai> dstorey: defer
- # [18:15] <bradk> I said defer
- # [18:15] <fantasai> fantasai: I think I would prefer to defer
- # [18:16] <fantasai> anton: defer
- # [18:16] <fantasai> Rossen: defer
- # [18:16] <fantasai> ?: defer
- # [18:16] <fantasai> Bert: defer
- # [18:16] <stearns> that's the most consistent straw-poll I've seen from this group yet
- # [18:16] <hober> s/?/hober/
- # [18:16] <fantasai> RESOLVED: element() deferred to L4
- # [18:16] <sylvaing> so moving to CR?
- # [18:17] <Rossen> Zakim, [Microsoft.a] is me
- # [18:17] <Zakim> +Rossen; got it
- # [18:17] <fantasai> dbaron: Substantial sections have been rewritten in last week.5, and should have time to review those before CR
- # [18:17] <fantasai> +1
- # [18:17] <fantasai> glazou: So let's make decision to move to CR at beginning of next concall
- # [18:17] <fantasai> Florian: Is that long enough for you, dbaron?
- # [18:17] <fantasai> dbaron: I'll see.
- # [18:18] * Quits: ChrisL (ChrisL@128.30.52.169) (Quit: Fire on main board error, client combusted)
- # [18:18] <fantasai> fantasai: Let's go for 1 week and see where we get to.
- # [18:18] <Zakim> -smfr
- # [18:18] <Zakim> -bradk
- # [18:18] <Zakim> -glazou
- # [18:18] * Quits: bradk (bradk@99.7.175.117) (Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ )
- # [18:18] <Zakim> -[Apple]
- # [18:18] <Zakim> -antonp
- # [18:18] <fantasai> Meeting closed.
- # [18:18] <Zakim> -stearns
- # [18:18] <Zakim> -[Microsoft.aa]
- # [18:18] <Zakim> -sylvaing
- # [18:18] * Quits: Rossen (Rossen@131.107.174.165) (Quit: Rossen)
- # [18:18] * Parts: antonp (50a94e63@64.62.228.82)
- # [18:18] <Zakim> -dstorey
- # [18:18] <Zakim> -dbaron
- # [18:18] <Zakim> -Rossen
- # [18:18] <Zakim> -Molly_Holzschlag
- # [18:18] <Zakim> -Bert
- # [18:18] <Zakim> -glenn.a
- # [18:18] <Zakim> -??P14
- # [18:18] <Zakim> -fantasai
- # [18:18] * Parts: mollydotcom (mollyh@68.231.165.244)
- # [18:19] <Zakim> -[IPcaller]
- # [18:19] * Quits: arronei (arronei@131.107.0.98) (Quit: arronei)
- # [18:19] * florianr felt a bit lonely arguing for defering, but the straw poll showed that wasn't quite the situation. Interesting
- # [18:19] <tantek> good to see the sense of urgency to move things forward encouraging swifter consensus with what to wrap-up vs. what to defer.
- # [18:21] <fantasai> florianr: straw polls are useful like that :) that's why we have them
- # [18:21] * Joins: arronei (arronei@131.107.0.69)
- # [18:21] * fantasai still needs to review Tab's complete rewrite of the object sizing algo :/
- # [18:21] * fantasai already had to revert some of his changes to that section...
- # [18:22] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
- # [18:23] * Quits: dstorey (Adium@67.180.84.179) (Quit: Leaving.)
- # [18:24] <Zakim> disconnecting the lone participant, glenn, in Style_CSS FP()12:00PM
- # [18:24] <Zakim> Style_CSS FP()12:00PM has ended
- # [18:24] <Zakim> Attendees were glenn, sylvaing, glazou, [IPcaller], Molly_Holzschlag, +1.415.766.aaaa, dbaron, +1.206.550.aabb, hober, stearns, smfr, JohnJansen, +8521616aadd, dstorey,
- # [18:24] <Zakim> ... +1.415.832.aaee, antonp, krit, fantasai, [Microsoft], bradk, Rossen, ChrisL, Bert, SteveZ, +47.21.65.aaff, +47.21.65.aagg, howcome
- # [18:25] * Quits: danielweck (danielweck@86.158.25.225) (Quit: danielweck)
- # [18:29] * Parts: oyvind (oyvinds@213.236.208.22)
- # [18:30] * Quits: arronei (arronei@131.107.0.69) (Quit: arronei)
- # [18:32] * Joins: arronei (arronei@131.107.0.94)
- # [18:38] * Quits: JohnJansen (qw3birc@128.30.52.28) (Quit: Page closed)
- # [18:39] * Quits: smfr (smfr@173.228.90.231) (Quit: smfr)
- # [18:43] * Joins: dstorey (Adium@144.189.101.1)
- # [18:56] * Quits: drublic (drublic@95.115.62.191) (Client exited)
- # [19:02] <shepazu> dbaron: who would be a good person to talk to about Developer Relations at Mozilla?
- # [19:03] * Joins: jet (jet@67.169.43.128)
- # [19:03] <shepazu> Christian? Beard? Stormy?
- # [19:04] * Joins: jet_ (jet@67.169.43.128)
- # [19:04] * Quits: jet (jet@67.169.43.128) (Connection reset by peer)
- # [19:04] * jet_ is now known as jet
- # [19:06] <dbaron> shepazu, Stormy
- # [19:06] <shepazu> dbaron: ok, thanks
- # [19:19] * Quits: florianr (florianr@213.236.208.22) (Quit: Leaving.)
- # [19:28] * Quits: glenn (gadams@71.218.126.59) (Client exited)
- # [19:28] * Joins: glenn (gadams@71.218.126.59)
- # [19:30] * Quits: dstorey (Adium@144.189.101.1) (Quit: Leaving.)
- # [19:48] <fantasai> sylvaing: Can you poke Phil about linking the issues list from http://dev.w3.org/csswg/css3-grid-layout/?
- # [19:56] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [19:58] * Joins: jet (jet@67.169.43.128)
- # [20:00] <sylvaing> fantasai: will do
- # [20:01] * Joins: jet_ (jet@67.169.43.128)
- # [20:01] * Quits: jet (jet@67.169.43.128) (Ping timeout)
- # [20:01] * Quits: jet_ (jet@67.169.43.128) (Connection reset by peer)
- # [20:01] * Joins: jet (jet@67.169.43.128)
- # [20:12] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
- # [20:15] <sylvaing> fantasai: he seems to have done so already; it points to https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=Grid+Layout&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED, which is legit
- # [20:24] * Zakim excuses himself; his presence no longer seems to be needed
- # [20:24] * Parts: Zakim (rrs-bridgg@128.30.52.169)
- # [20:28] * Joins: drublic (drublic@77.2.139.51)
- # [20:49] <fantasai> sylvaing: yeah, I found the bugzilla list shortly afterward and edited it in...
- # [20:50] <sylvaing> damn, you're good...
- # [20:50] <fantasai> I have to be, right? Otherwise nothing would ever get published. :/
- # [20:51] <Ms2ger> All too true
- # [20:55] * Quits: dbaron (dbaron@173.228.85.36) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [21:37] * Joins: leaverou (leaverou@67.180.84.179)
- # [21:45] * Joins: dbaron (dbaron@159.63.23.38)
- # [21:49] <sylvaing> fair point
- # [21:49] <sylvaing> the day you move to france and pick up on strikes and 35-hour weeks, we are screwed
- # [21:50] * fantasai used to clock in at ~30hrs/wk of billable time, actually
- # [21:51] <fantasai> I'm still in the process of recalibrating to employee clocking.
- # [21:51] <fantasai> Hard to do with so much travel, though. I always work more hours on work trips than I do when I'm home...
- # [21:57] <sylvaing> well, i'm not just talking billable time. i mean, you don't bill the WG for all the stuff you do, right?
- # [21:57] <fantasai> no, but I've billed HP, MS, Mozilla, and Antenna House for WG work...
- # [21:59] * Joins: arno (arno@192.150.10.200)
- # [22:00] <fantasai> billable hours doesn't include the time I spend being distracted
- # [22:00] <fantasai> or otherwise unproductive
- # [22:00] <fantasai> or handling overhead
- # [22:00] <sylvaing> right
- # [22:01] <TabAtkins_> My billable hours do.
- # [22:02] <fantasai> TabAtkins_: you're an employee
- # [22:02] <TabAtkins_> I consider it a good day when I get four hours of productive work done.
- # [22:02] <Ms2ger> fantasai, so are you! :)
- # [22:02] <TabAtkins_> Thought that obviously doesn't count time spent reading emails at home.
- # [22:02] <fantasai> I am now! But I wasn't until last year. :)
- # [22:02] <TabAtkins_> fantasai: I'm going to rewrite that paragraph you rewrote. ^_^ I hated that language originally, and was happy to replace it, but now you've brought back most of it!
- # [22:02] <sylvaing> Tab, yes. Office time is not the whole story.
- # [22:03] <fantasai> TabAtkins_: well don't regress things this time!
- # [22:03] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [22:03] <TabAtkins_> I don't actually understand what I regressed.
- # [22:04] <TabAtkins_> Oh, was there a <dfn> around those terms before?
- # [22:04] <fantasai> http://lists.w3.org/Archives/Public/www-style/2012Mar/0494.html
- # [22:04] <fantasai> http://lists.w3.org/Archives/Public/www-style/2012Mar/0496.html
- # [22:05] <TabAtkins_> Yes, I'm looking at those emails.
- # [22:05] <fantasai> ping me when you're done rewriting, so I can review it
- # [22:05] <TabAtkins_> I just didn't understand what you said in them.
- # [22:06] <fantasai> Ok, let me break it down for you.
- # [22:06] <fantasai> "But you've lost all consideration of images with only a width
- # [22:06] <fantasai> > or only a height"
- # [22:07] <fantasai> Theses are the possible cases:
- # [22:07] <fantasai> * has width + height + aspect ratio
- # [22:07] <fantasai> * has width
- # [22:07] <fantasai> * has height
- # [22:07] <fantasai> * has aspect ratio
- # [22:07] <fantasai> * has no intrinsic sizes
- # [22:07] <fantasai> Your rewrite is clear about 1, 4, and 5. The old text is clear that all five exist
- # [22:07] <fantasai> "you've dropped the mention of embedded documents,
- # [22:07] <fantasai> > which is a useful example."
- # [22:07] <fantasai> I don't understand how this point is unclear...
- # [22:08] <fantasai> "This rewrite also drops the definitions of 'intrinsic width', 'intrinsic
- # [22:08] <fantasai> height', and 'intrinsic aspect ratio'.
- # [22:08] <fantasai> "
- # [22:08] <fantasai> nor this part
- # [22:08] <fantasai> I can paraphrase them for you if that would help?
- # [22:09] <fantasai> First one is "The old text mentioned embedded documents as an example of an object without intrinsic dimensions. The new text does not have this example. It would be better to have this example, unless you have a good reason for deleting it."
- # [22:09] <fantasai> Second one is
- # [22:09] <fantasai> "The old text has definitions for 'intrinsic width', 'intrinsic height', and 'intrinsic aspect ratio
- # [22:10] <fantasai> '. The new text does not have such definitions, leaving the various instances of these terms undefined."
- # [22:10] <fantasai> Is it clear now?
- # [22:10] <fantasai> If not, point out which bit is unclear, and I will try a differen paraphrase......
- # [22:31] <TabAtkins_> You could have just said "you dropped the sentence explicitly talking about an image having only a width or height".
- # [22:32] <TabAtkins_> And "you accidentally dropped the part of the markup that actually had <dfn>s around 'intrinsic width' etc."
- # [22:32] <TabAtkins_> All fixed now in my rewrite, btw.
- # [22:32] <fantasai> I don't care about that sentence. I care that the concept is clear
- # [22:32] <fantasai> And the <dfn>s aren't the point; the old text actually had some semblance of a definition as well
- # [22:33] <TabAtkins_> The preceding paragraph has a definition.
- # [22:33] <fantasai> no, it defines "intrinsic"
- # [22:33] <TabAtkins_> It's informal, because, well, the concept is kinda informal.
- # [22:34] <fantasai> s/may/can/g;
- # [22:34] <fantasai> this isn't an rfc2119 use
- # [22:34] <TabAtkins_> Oh, whoops.
- # [22:34] <fantasai> the object is not out-of-conformance if it fails to comply
- # [22:34] <fantasai> it just can't
- # [22:35] <fantasai> s/all raster/raster/ please
- # [22:35] <TabAtkins_> Hm, why?
- # [22:35] <fantasai> less words is better?
- # [22:35] <TabAtkins_> Sounds reasonable.
- # [22:36] * fantasai is also suspicous that someone has/will invent a raster format that only has an aspect ratio somehow
- # [22:36] * fantasai or something like that
- # [22:36] <TabAtkins_> That sounds impossible on its face.
- # [22:36] <TabAtkins_> Given the definition of "raster image".
- # [22:37] <fantasai> pixellated graphics designed to be pixellated but scalable? :)
- # [22:37] <TabAtkins_> That'd still be a vector format, no?
- # [22:37] * fantasai has no idea
- # [22:38] * fantasai thinks <span class="note"> plus parens is excessive
- # [22:38] <TabAtkins_> Hm, probably.
- # [22:39] <fantasai> I also don't see why it can't be normative like it was in the previous version
- # [22:39] <fantasai> Like, seriously, you didn't have to revert *everything*
- # [22:39] <fantasai> :)
- # [22:39] <fantasai> I think what bothers me about your rewrite is that it's one very long sentence with parentheticals that in some cases are themselves long sentences
- # [22:40] <TabAtkins_> Because I'm not making a normative statement, just giving a reminder that you can't have two.
- # [22:40] <TabAtkins_> What bothered me about my old text was that it was just a pile of sentence fragments *and* still had long parentheticals.
- # [22:40] <fantasai> hehehe
- # [22:40] * fantasai doesn't have a good solution to this
- # [22:40] <TabAtkins_> Also: MY INBOX WON'T GO DOWN
- # [22:40] <fantasai> ?
- # [22:41] <fantasai> TabAtkins: statements of fact are allowed in the spec. They don't need to be marked in a Note
- # [22:41] <TabAtkins_> I keep trying to clean my inbox in between talking with you and making edits, and when I return it's back up to where it was before.
- # [22:41] <fantasai> lol
- # [22:41] * fantasai should send you some email simultaneously ;)
- # [22:41] * Joins: arno (arno@192.150.10.200)
- # [22:41] <TabAtkins_> fantasai: Sure, but I feel it can be mistaken here for attempting to ill-define something.
- # [22:41] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
- # [22:42] * TabAtkins_ thinks it's time to adjust his public-html filter to auto-archive.
- # [22:42] <fantasai> I don't see how adding "An object cannot have only two intrinsic dimensions, as any two automatically imply the third. For example, an image with a defined width and aspect ratio also has a defined height implied by the width and aspect ratio."
- # [22:42] <fantasai> could be problematic
- # [22:42] <TabAtkins_> Less words is better?
- # [22:42] * Quits: jet (jet@67.169.43.128) (Quit: jet)
- # [22:43] * fantasai deleted the "Note"
- # [22:43] * fantasai thinks that makes it less
- # [22:43] <fantasai> :)
- # [22:43] <TabAtkins_> It's in our style guide!
- # [22:43] * fantasai also took out the <span class="note"> and it is therefore compliant with the style guide
- # [22:43] <TabAtkins_> nuuuuuu!
- # [22:44] * tantek scrolls up
- # [22:44] <fantasai> The other thing that's a bit troublesome imo is that we start by describing objects with no intrinsic dimensions
- # [22:44] <fantasai> and finishing by describing ones that have all three
- # [22:44] <fantasai> whereas the reader is most likely to be familiar with the latter
- # [22:44] <TabAtkins_> It felt better that way.
- # [22:44] <TabAtkins_> But I can try reordering.
- # [22:45] <fantasai> I know. It's because of the exact wording you used. >_<
- # [22:45] * TabAtkins_ just likes going from 0 up.
- # [22:46] <fantasai> Probably need to solve the excessively long parentheticals inside excessively long sentence along with the reordering.
- # [22:46] <tantek> looks like another nice fantasai/TabAtkins back/forth. good times. pass the popcorn.
- # [22:46] <fantasai> This is the trouble with wording... there's subtle things about it that get tangled when you do simple things like reordering
- # [22:46] <tantek> +1
- # [22:46] <TabAtkins_> Let me poke at it a bit.
- # [22:47] <fantasai> kk
- # [22:47] * fantasai will continue trying to tweak the wording on the minutes ;)
- # [22:47] <TabAtkins_> Also: grr, I got in a stupid inconsistent state in Hg yesterday and had to reset the whole repo.
- # [22:47] * fantasai trying to make it understandable to ppl who weren't there
- # [22:47] <TabAtkins_> stupid merge conflicts.
- # [22:47] <fantasai> ummm
- # [22:47] <fantasai> TabAtkins_: http://wiki.csswg.org/tools/hg ?
- # [22:47] <TabAtkins_> Or rather, stupid documentation that doesn't explain how to solve merge conflicts during a rebase properly.
- # [22:48] <fantasai> it suggests hg rebase --abort and then using hg merge
- # [22:48] <fantasai> which seems fair if you have complicated merge conflicts...
- # [22:49] * fantasai wrote a chapter on hg resolve on the flight back from sxsw
- # [22:49] <fantasai> "The more frequently you synchronize, the less likely you are to encounter merge issues. " ^_^
- # [22:50] * fantasai uses mercurial queues instead of rebase, never could figure out rebase
- # [22:53] <Ms2ger> All I've figured out about rebase is that it tends to break stuff
- # [22:54] <fantasai> heh
- # [22:54] <Ms2ger> Removing random files, stuff like that
- # [22:54] <fantasai> :/
- # [22:55] <Ms2ger> But hey, maybe it handles repos that are smaller than mozilla-central better
- # [22:55] <fantasai> that seems like an odd problem to have on scaling
- # [22:56] <fantasai> http://fantasai.inkedblade.net/tools/mq
- # [22:56] <fantasai> They day I sat down to learn Mercurial for mozilla-central, I wrote myself a perl script out of my notes.
- # [22:57] <Ms2ger> Eww, perl ;)
- # [23:00] * fantasai suspects howcome's comments didn't get minuted correctly, and has no idea how to fix them
- # [23:04] <TabAtkins_> fantasai: It wasn't a complicated conflict at all. The Overview.html had two lines in the header different. AND EVERYTHING WENT RETARDED.
- # [23:04] <fantasai> TabAtkins_: Did you figure out how to use hg resolve?
- # [23:04] <TabAtkins_> I use rebase because that's how I learned to use git, to keep a prettier history.
- # [23:05] <Ms2ger> MQ gives you a pretty history as well
- # [23:05] <TabAtkins_> fantasai: I'm not sure. Like I said, it all went pear-shaped, so I just blew away the repo and started over.
- # [23:05] <fantasai> TabAtkins_: Yeah, if you have merge conflicts, you need to use hg rebase.
- # [23:05] <fantasai> rebase or merge, doesn't matter
- # [23:05] * fantasai didn't know how to solve conflicts in hg until she wrote the docs for it last week
- # [23:06] <Ms2ger> Yay docs!
- # [23:06] <fantasai> TabAtkins_: http://wiki.csswg.org/tools/hg#resolving-conflictshg-resolve
- # [23:06] <TabAtkins_> I eventually got to a state where I had no pending commits that it would tell me about, no pending *un*committed changes, and I was synced against latest head, but it still failed to rebase.
- # [23:06] <fantasai> TabAtkins_: use MQ? :)
- # [23:06] * fantasai offers her perl script as documentation
- # [23:06] <fantasai> :) :)
- # [23:06] <TabAtkins_> fantasai: Yeah, I did what that page describes, but I think I'd already screwed things up by then.
- # [23:07] <TabAtkins_> Anyway, if I just don't screw around and use resolve properly, I think I'll be okay.
- # [23:07] * Quits: lgombos_ (Laszlo@86.217.58.90) (Ping timeout)
- # [23:07] <fantasai> okay
- # [23:14] <TabAtkins_> fantasai: In my rewrite of that paragraph, I realized that the whole point is just to present those examples, so I'm removing all the non-parenthetical text.
- # [23:15] <stearns> and the parentheses, I hope
- # [23:15] <TabAtkins_> You'd think so, yes.
- # [23:23] * Quits: Ms2ger (Ms2ger@81.242.178.33) (Quit: nn)
- # [23:50] * sylvaing is now known as sylvaing_away
- # [23:54] * Quits: drublic (drublic@77.2.139.51) (Client exited)
- # Session Close: Thu Mar 22 00:00:00 2012
The end :)