Options:
- # Session Start: Fri May 20 00:00:00 2011
- # Session Ident: #css
- # [00:40] * Joins: arno1 (arno@192.150.10.200)
- # [00:41] * Quits: arno (arno@192.150.10.200) (Ping timeout)
- # [00:52] * Quits: shepazu (schepers@128.30.52.169) (Quit: shepazu)
- # [01:08] * Quits: arno1 (arno@192.150.10.200) (Quit: Leaving.)
- # [01:11] * Joins: arno (arno@192.150.10.201)
- # [03:32] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [04:19] * fantasai waves to jdaggett
- # [04:19] <jdaggett> hiya
- # [04:19] <jdaggett> when do you arrive? late next week?
- # [04:21] <fantasai> the day before the meeting
- # [04:22] <fantasai> actually
- # [04:22] <fantasai> late on the 31st
- # [04:22] <fantasai> Newark -> NRT -> ITM
- # [04:22] <fantasai> I'll be around the week after, though
- # [04:22] <fantasai> Flying home on the 11th from Tokyo
- # [04:22] <jdaggett> wow, hard schedule
- # [04:22] <fantasai> could've been worse
- # [04:22] <jdaggett> "scrape me off the plane and slap me in a meeting"
- # [04:23] <fantasai> I /could/ have had to fly the day before
- # [04:23] <fantasai> to arrive on the 30th
- # [04:23] <fantasai> which would mean a level of sleep deprivation I have rarely experienced outside working on my thesis
- # [04:23] <fantasai> :)
- # [04:23] <jdaggett> is the flight from NRT to ITM (i.e. not Haneda --> ITM)?
- # [04:23] <fantasai> yeah
- # [04:24] <jdaggett> that's good
- # [04:24] <fantasai> yes!
- # [04:24] <fantasai> otherwise I wouldn't make it :P
- # [04:25] <jdaggett> yeah, for lots of places in japan, it's easier to fly via korea because you can simply change planes in seoul
- # [04:25] <jdaggett> rather than hassling with NRT to HND
- # [04:25] <jdaggett> crazy
- # [04:26] <fantasai> huh, yeah
- # [04:30] <jdaggett> just sent a correction regarding the minutes
- # [04:30] <jdaggett> i think you really want to stay in tokyo the whole time
- # [05:47] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [05:47] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [07:07] * Quits: hober (ted@174.143.153.77) (Client exited)
- # [07:07] * Joins: hober (ted@174.143.153.77)
- # [07:44] <fantasai> jdaggett: oh, oops
- # [07:45] <jdaggett> hehe
- # [07:45] <jdaggett> funny how some things become habits...
- # [07:45] <fantasai> probably doesn't help that they're the same two syllables swapped around :)
- # [07:48] <jdaggett> well, the kyo part is the same in both words, "capital"
- # [07:48] <fantasai> yeah
- # [07:48] <fantasai> I know :)
- # [07:49] <fantasai> it's the same as the "jing" in Beijing
- # [07:53] <jdaggett> btw, you must go here: http://en.wikipedia.org/wiki/Ry%C5%8Dan-ji
- # [08:12] * Joins: homata (homata@113.34.70.146)
- # [08:13] * Quits: homata___ (homata@58.158.182.50) (Ping timeout)
- # [08:26] <fantasai> ok
- # [08:26] <fantasai> :)
- # [08:32] * Joins: homata_ (homata@58.158.182.50)
- # [08:33] * Quits: homata (homata@113.34.70.146) (Ping timeout)
- # [08:33] * Joins: homata (homata@58.158.182.50)
- # [08:33] * Quits: homata (homata@58.158.182.50) (Connection reset by peer)
- # [08:35] * Quits: homata_ (homata@58.158.182.50) (Ping timeout)
- # [08:50] * Joins: homata (homata@113.34.70.146)
- # [10:17] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [10:24] * Joins: homata_ (homata@58.158.182.50)
- # [10:26] * Quits: homata (homata@113.34.70.146) (Ping timeout)
- # [10:59] * Joins: szilles (chatzilla@85.86.191.226)
- # [11:12] * Quits: homata_ (homata@58.158.182.50) (Quit: Leaving...)
- # [11:13] * Quits: szilles (chatzilla@85.86.191.226) (Ping timeout)
- # [11:18] * Joins: homata (homata@58.158.182.50)
- # [13:08] * Quits: homata (homata@58.158.182.50) (Quit: Leaving...)
- # [15:14] * Joins: Ms2ger (Ms2ger@91.181.12.117)
- # [15:19] * Quits: unomi (unomi@125.26.199.82) (Ping timeout)
- # [15:23] * Joins: dbaron (dbaron@74.103.171.70)
- # [15:33] * Joins: unomi (unomi@125.26.199.82)
- # [16:30] * Joins: Martijnc (Martijnc@84.192.44.100)
- # [16:44] * Quits: Ms2ger (Ms2ger@91.181.12.117) (Quit: bbl)
- # [18:02] * Joins: arronei (arronei@131.107.0.71)
- # [18:03] * Quits: arronei_ (arronei@131.107.0.81) (Ping timeout)
- # [19:05] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
- # [19:08] * Quits: arronei (arronei@131.107.0.71) (Quit: arronei)
- # [19:14] * Joins: arronei (arronei@131.107.0.109)
- # [19:38] * Joins: arno (arno@192.150.10.201)
- # [19:38] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
- # [19:51] <TabAtkins> Bert: The preprocessor is stripping the alt attributes off my images. I assume this is because I'm using the boolean syntax, since it's just empty alts.
- # [19:51] * Joins: arno (arno@192.150.10.201)
- # [19:56] * Joins: shepazu (schepers@128.30.52.169)
- # [20:04] * Quits: shepazu (schepers@128.30.52.169) (Quit: shepazu)
- # [20:04] <TabAtkins> fantasai: I've run through pubrules and it seems fine - the only complaints were things about generating as WD (I don't commit the voodoo to make the preprocessor generate correctly to my brain), and some dumb errors about the capitalization of SotD and ToC that the preprocessor makes.
- # [20:45] <fantasai> TabAtkins: ok, I'll run the voodoo for you
- # [21:01] <fantasai> TabAtkins: Alright, your draft is prepped for 24 May 2011
- # [21:01] <fantasai> http://dev.w3.org/csswg/css3-lists/
- # [21:02] <fantasai> Bert: The preprocessor's property-index generator is not working well with the descriptors in Tab's draft. Not sure what's the right way to fix it, probably they should be excluded from the property table...
- # [21:02] * fantasai studies css3-fonts
- # [21:03] <fantasai> TabAtkins: jdaggett uses class="descref" instead of "propdef" for his descriptors
- # [21:08] * fantasai tries this
- # [21:11] <fantasai> ok, that worked
- # [21:11] <fantasai> now to fix the 'display' propdef
- # [21:11] * fantasai copies pattern from css3-ui
- # [21:12] * Quits: dbaron (dbaron@74.103.171.70) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [21:21] <fantasai> TabAtkins: Dude, you are missing all kinds of fields from your propdef tables >:/
- # [21:25] * fantasai finally gets a working property index table
- # [21:28] <fantasai> ok, I guess that's good enough
- # [21:31] <fantasai> TabAtkins: Check the diffs? http://dev.w3.org/cvsweb/csswg/css3-lists/Overview.src.html
- # [21:57] <TabAtkins> fantasai: Looks good to me. I didn't realize descdef was a thing either.
- # [22:23] <fantasai> TabAtkins: ok, shall I send in the pub request?
- # [22:24] <TabAtkins> Yes please! Also cc me, so maybe I can do this in the future instead of being a baby and getting you to do it for me?
- # [22:24] <fantasai> Of course I'll CC you!
- # [22:25] * fantasai runs pubrules checker to make sure it's all good
- # [22:26] <fantasai> uh
- # [22:26] <fantasai> it's throwing an exception
- # [22:26] <fantasai> ~_~
- # [22:26] <TabAtkins> Try it again. I had to hit it twice.
- # [22:27] <fantasai> Nope, not working
- # [22:27] <TabAtkins> Okay, well I've got another copy up.
- # [22:28] <fantasai> ?
- # [22:28] <TabAtkins> I mean that I was able to get it working, so I'm looking at the results right now.
- # [22:29] * fantasai just runs regular validation
- # [22:29] <TabAtkins> The results are simply that I either fail with 1 error in HTML4 validation mode, or like 8 in HTML5.
- # [22:29] <TabAtkins> (The 8 are the fault of the preprocessor.)
- # [22:30] <fantasai> Bert: Can you remove 'valign=baseline' from the propdef tables, please? It's deprecated, use 'vertical-align' :)
- # [22:30] <TabAtkins> The CSSWG stylesheet uses background-clip, which is not part of 2.1, so we fail CSS validation according to pubrules. ^_^
- # [22:30] <TabAtkins> And that's it.
- # [22:30] <fantasai> yeah, that's a bug
- # [22:30] <fantasai> in the validator
- # [22:31] * fantasai tries to get the HTML to validate, at least
- # [22:31] <TabAtkins> HTML validation is easy. Just switch the preprocessor to not output @valign, and use <abbr> instead of <acronym>
- # [22:32] <fantasai> yeah, well, I can't do that right now :)
- # [22:32] <TabAtkins> We can do those fixes manually for the purpose of publishing if necessary.
- # [22:33] <fantasai> OK, should validate
- # [22:33] * fantasai switched it to HTML 4.01
- # [22:33] <TabAtkins> type="css", fantasai? Really?
- # [22:33] <fantasai> it's required in HTML4
- # [22:33] <TabAtkins> type=text/css
- # [22:33] <fantasai> oh
- # [22:33] <fantasai> how'd that validate??
- # [22:34] <TabAtkins> It shouldn't have. The html5 validator barfs on it.
- # [22:34] <fantasai> yeah, hsivonen's a lot more thorough ^_^
- # [22:34] <fantasai> ok, should be fixed
- # [22:34] <TabAtkins> Yup.
- # [22:35] <fantasai> Alrighty then, let's send this over
- # [22:38] * Quits: Martijnc (Martijnc@84.192.44.100) (Quit: Martijnc)
- # [22:39] * fantasai collects the files, fixes the stylesheet link, etc
- # [22:44] <TabAtkins> fantasai: Fiddling with Images again. I don't like the way we're preventing nested image(). The way it's written, only a whitelist of <image> types are allowed in the final fallback, which means we'll have to keep it updated.
- # [22:45] <TabAtkins> I'd rather just say "<color> | <image>", and then disallow image() in the prose.
- # [22:46] <TabAtkins> It's also too restrictive - the way you rewrote it, <image-combination> isn't allowed, even if there's no reference to image() in the arguments to cross-fade().
- # [22:50] <fantasai> TabAtkins: why wouldn't you just cross-fade(image(),image()) in that case?
- # [22:51] <fantasai> TabAtkins: I see what you mean about updates, let me think on that a bit
- # [22:51] <TabAtkins> I'm not saying you wouldn't. I'm saying that as it's written, you can't do an image("foo", cross-fade(url("bar"), blue, 50%)) or something.
- # [22:51] <fantasai> is that useful?
- # [22:52] <TabAtkins> It's not clearly useless, and I don't think there's any simplicity benefits from disallowing it.
- # [22:53] <fantasai> I'd ask dbaron on that
- # [22:53] <fantasai> I don't work on the parser/data side
- # [22:54] <TabAtkins> Well, I'll say that you don't gain anything from disallowing that while allowing, say, nested cross-fade()s.
- # [22:54] <fantasai> we allow nested cross-fade()s?
- # [22:54] <fantasai> ~_~
- # [22:54] <TabAtkins> Sure. An image is an image.
- # [22:54] <fantasai> do we have to?
- # [22:54] <TabAtkins> Why wouldn't you?
- # [22:54] <TabAtkins> It lets you fade three images together.
- # [22:55] <fantasai> Hm.
- # [22:55] <fantasai> I
- # [22:55] <fantasai> I'd like to get implementer feedback on all this nesting stuff
- # [22:56] <fantasai> If it's easy, fine
- # [22:56] <fantasai> if it's extra work, I'd like to keep nesting out of this level
- # [22:56] <fantasai> it's definitely more complicated to test
- # [22:56] <TabAtkins> Other than the fact that more image manipulation = more CPU load, there's no problem from doing so.
- # [22:56] <TabAtkins> Sure.
- # [22:56] <fantasai> It's definitely possible to extend in that direction in the future
- # [22:57] <TabAtkins> But if we disallow nested cross-fades, you can still, say, filter() a cross-fade(), or vice versa, which is roughly equivalent in difficulty.
- # [22:57] <fantasai> so I'm kindof biased towards not allowing nesting
- # [22:57] <TabAtkins> I'm biased toward not putting in artificial restrictions just because it makes testing more difficult.
- # [22:57] <fantasai> TabAtkins: I think you should ask Arron about that. He might disagree
- # [22:58] * fantasai doesn't see filter() in this draft
- # [22:58] <TabAtkins> We'd have to invent a notion of a <plain-image> versus <constructed-image> or something, and only allow some functions to take <plain-image> as arguments.
- # [22:58] <TabAtkins> No, filter() will be in Filters.
- # [22:58] <fantasai> good
- # [22:58] <fantasai> :)
- # [22:58] <TabAtkins> Along with maybe noise(), I dunno.
- # [22:58] <fantasai> I was like, I think we have enough crazy stuff here already!
- # [22:58] <TabAtkins> noise() won't be in this draft, at least.
- # [22:58] <TabAtkins> Either Filters or Images 4.
- # [23:03] <fantasai> TabAtkins: actually...
- # [23:03] <fantasai> TabAtkins: I think we should also remove <element-reference> from image()
- # [23:04] <TabAtkins> Really? Why?
- # [23:04] <fantasai> why would you fall back to an element reference?
- # [23:04] <TabAtkins> What do you gain from removing it?
- # [23:05] <fantasai> simplicity
- # [23:05] <fantasai> I'm kindof thinking we should remove everything except <image-decl> and <color>
- # [23:05] <fantasai> the last is only there to provide enough contrast in case stuff fails
- # [23:05] <TabAtkins> That's silly. Then I can't fall back to a gradient, for example.
- # [23:06] <fantasai> you're already in a failure mode if your images don't load
- # [23:06] <fantasai> if you can fall back to a gradient, then why not fall back to a full <background> declaration
- # [23:07] <fantasai> where you can create whatever image you want with gradients?
- # [23:07] <fantasai> like
- # [23:07] <fantasai> that's not the point here
- # [23:07] <fantasai> the only reason <color> is there is to provide adequate contrast
- # [23:07] <fantasai> in case images are turned of or don't load
- # [23:07] <TabAtkins> Hm. Actually, I'd probably be okay with dropping down to that level of simplicity.
- # [23:07] <fantasai> Ok, let's do that.
- # [23:08] <fantasai> We can add things back in CSS4 if we find it's really really needed
- # [23:08] <TabAtkins> I just didn't like the seemingly-artificial distinctions in what types of images were allowed.
- # [23:08] <TabAtkins> Yeah.
- # [23:10] <fantasai> k, css3-lists pub request sent
- # [23:11] <TabAtkins> Thank you!
- # [23:11] <fantasai> Good job with the module!
- # [23:11] <fantasai> It's way more coherent and awesome now :)
- # [23:12] <fantasai> But, definitely needs another cycle or two of WD-level review :)
- # [23:12] <fantasai> I noticed a bunch of stuff while scanning through it
- # [23:15] <TabAtkins> Yeah, definitely. I just think it's feature-complete now, so I'm happy.
- # [23:15] <hober> yay
- # [23:18] <fantasai> yeah
- # Session Close: Sat May 21 00:00:00 2011
The end :)