02:21
<OreoCookie>
can anyoner point me to where on whatwg <a name> has been depriciated? It just started showing as a warning in the validator, I have no idea
02:21
<OreoCookie>
had*
05:17
<jacobolus>
is there any way to save the current canvas path and fetch it back later?
05:18
<MikeSmith>
jacobolus: if you don't get an answer here, you might also try asking over on #html5
05:18
<jacobolus>
huh. I didn't know that existed. I guess I can join it :)
05:19
<jacobolus>
in this particular question, I'm not necessarily needing that function, just trying to figure out what's possible
05:19
<jacobolus>
I'm having a lot of fun writing canvas code in coffeescript
05:19
<MikeSmith>
coffeescript seems pretty cool
05:20
<MikeSmith>
I've not messed around with it yet at all
05:20
<jacobolus>
MikeSmith: I can do this kind of thing http://pastie.textmate.org/private/mwt5aikrepgnsl3eaz8cq
05:20
<MikeSmith>
pretty clean
05:21
<jacobolus>
and then later on http://pastie.textmate.org/private/nww6wsqfpftshry6pt0jg
05:21
<jacobolus>
MikeSmith: yeah, it's possible to make the code very clean
05:21
<jacobolus>
because creating anon functions is so syntactically cheap
05:22
<jacobolus>
it means I start using a lot more of them everywhere
05:23
<sharksoda>
it looks like pseudocode almost
05:23
<MikeSmith>
it's funny how syntax differences can affect programming style
05:23
<jacobolus>
yeah, it makes a huge difference
05:24
<jacobolus>
`function (args) { return foo; }` vs `(args) -> foo`
05:24
<jacobolus>
or in the case w/o args, even better, `function () { return foo; }` vs `-> foo`
05:24
<jacobolus>
makes it so that code doing tricky functional stuff is actually readable, instead of buried in a mass of syntax
05:25
<jacobolus>
I think for instance if you took the code in John Resig's Ninja book and translated to coffeescript, understanding what it was doing would be much less mental effort
05:26
<jacobolus>
[obviously doesn't apply to the whole book, some of which uses JS features like `with` not used in CS]
05:27
<jacobolus>
[though actually it would be possible to bring those features into CS by making a couple helper functions for them, as in CS it's possible to wrap raw JS in backticks]
05:29
<MikeSmith>
there does seem to be a lot of momentum behind CS now
05:29
<jacobolus>
I really like it
05:29
<MikeSmith>
one of those things that makes it a lot easier to program Web applications now then it used to be
05:30
<MikeSmith>
it's hard to imagine now writing a Web app without having Firebug or Web Inspector or whatever for debugging
05:30
<jacobolus>
I'm still not entirely convinced about any of the client-side structured GUI frameworks around, but that might just be lack of close familiarity
05:31
<jacobolus>
yes, with no debugger/repl programming is awful
05:31
<jacobolus>
that goes for pretty much any language
05:31
<MikeSmith>
yeah
05:32
<MikeSmith>
it was that way for Javascript for a long time though
05:32
<jacobolus>
I even think C would be a lot nicer to write code in if it had a widespread repl
05:32
<MikeSmith>
before Firebug
05:32
<jacobolus>
yeah, back when men were men &c.
05:32
<MikeSmith>
heh
05:32
<jacobolus>
also, browser inconsistencies were a lot more obnoxious at that point
05:33
<jacobolus>
and everything was semi-broken, it was easy to accidentally cause crashes or memory leaks, &c. &c.
05:33
<jacobolus>
JS in the browser is getting pretty nice
05:33
<jacobolus>
it's still not python, but it's getting better :)
05:34
<MikeSmith>
yeah, it's come a long way
05:34
<MikeSmith>
as far as a C repl, I guess I've never used a shell environment with a compiled language and don't have such a clear idea of how it would work
05:35
sharksoda
writes C daily
05:36
<jacobolus>
Hixie: we were talking about color spaces &c. the other day; I'm almost at the point where this CIECAM02 color picker is minimally useful http://imgur.com/pwlsn
05:37
<MikeSmith>
sharksoda: what kind of apps do you work on?
05:37
<sharksoda>
MikeSmith: games
05:38
<MikeSmith>
sharksoda: for what kinds of platforms?
05:39
<sharksoda>
win/mac/linux, no consoles
05:39
<MikeSmith>
ok
05:39
<MikeSmith>
have you done much browser-based game development? HTML+JS, I mean
05:40
<sharksoda>
not yet, it's on my list of things to check out though
05:40
<MikeSmith>
I ask because it's always useful to hear where game developers see deficiencies in the Web platform that would prevent them from developing Web-based games
05:41
<jacobolus>
MikeSmith: there are some things that are currently slow that it would be nice to speed up. I think getting the fast arrays and array math from webgl will be very nice
05:42
<jacobolus>
[though I haven't really played with it yet]
05:42
<jacobolus>
also, this isn't games exactly, but it'd be nice to have some native crypto accessible from JavaScript APIs
05:43
<jacobolus>
also, I'll be somewhat excited when more of the nifty parts of SVG are actually supported across browsers
05:48
<MikeSmith>
jacobolus: which parts of SVG?
05:48
<MikeSmith>
about crypto, I remember seeing a proposal about that on the whatwg list some time back
05:49
<sharksoda>
MikeSmith, a few common needs for games I can see being troublesome would be need for gamepads and fullscreen
05:49
<jacobolus>
MikeSmith: for example, the filter effects
05:50
<sharksoda>
(of course, I don't think i.e. flash can do gamepads either)
05:51
<jacobolus>
MikeSmith: for my part, I also really really wish there was a color-profile-supporting web drawing API
05:52
<jacobolus>
MikeSmith: I think I might at some point end up writing code for parsing PNG images and adding a profile to them (or when possible just setting the 'sRGB' flag), and then just draw on a canvas off-screen, get the PNG, add the profile, and show it w/ a data: url
05:53
<jacobolus>
but I haven't gotten around to reading enough of the PNG spec to figure out how to do the bits needed to accomplish that
05:54
<jacobolus>
oh, wow, it looks like the filter effects support in webkit has made substantial progress since last I looked
05:54
<jacobolus>
http://www.webkit.org/projects/svg/status.xml
05:54
<jacobolus>
[although "Requires build-webkit --filters to enable"]
05:54
<jacobolus>
[so still not really usable in production]
05:56
<MikeSmith>
I didn't know that code had made it in yet
05:56
<MikeSmith>
that was the big remaining thing the Webkit SVG support was lacking, I think
06:13
<ako>
<MikeSmith> [...] deficiencies in the Web platform [...] <- Audio is awful, lack of Ogg/Vorbis support in IE9+ and Safari is also annoying
06:14
<aho>
also missing: full screen and mouse grabbing
06:14
<aho>
and yea... gamepad support :>
06:14
<MikeSmith>
there is ongoing discussion about full screen
06:14
<MikeSmith>
and has been some about mouse grabbing
06:15
<MikeSmith>
gamepad support, I dunno
06:16
<aho>
it's also annoying that there isn't a lossy rgba format
06:16
<aho>
i still blame mozilla for that, by the way
06:16
<aho>
:>
06:17
<aho>
http://kaioa.com/node/104 <- splicing images together kinda works though
06:17
<aho>
but it's not really an option for background-images or regular images
06:18
<aho>
http://kaioa.com/b/1102/svgjng/index.html <- emulating it via svg also doesnt really work due to some quirk in the svg specs :/
06:19
<aho>
about 50% of the renderers use linerRGB (which is technically correct, but silly) and the other half uses sRGB (which is technically wrong, but it's like masking works everywhere)
06:20
<MikeSmith>
a good place to discuss gamepad events would be on the public-webevents⊙wo mailing list
06:20
<MikeSmith>
http://lists.w3.org/Archives/Public/public-webevents/
07:20
<MikeSmith>
hsivonen: http://bugzilla.validator.nu/ seems to be responding really really slowly the last couple days
07:24
<hsivonen>
MikeSmith: it responds reasonably to me, but let's see what's going on
07:25
<hsivonen>
MikeSmith: The validator process on that host is consuming > 90% of CPU
07:25
<MikeSmith>
wow
07:26
<MikeSmith>
some bot hitting it, maybe?
07:26
<hsivonen>
let's see...
07:31
<hsivonen>
looks like there's been a Firefox extension hitting it
07:31
<hsivonen>
but now the hits have stopped but the process still consumes CPU resources excessively
07:33
<hsivonen>
MikeSmith: it should be better now.
07:34
<hsivonen>
this looks bad, though, since it seems there's a way to get the validator entangled in excessive compute for at least 15 minutes after the validation request
07:42
<MikeSmith>
hsivonen: that does sound less than ideal
07:45
<MikeSmith>
hsivonen: coincidentally, I notice that the instance I have running on w3.org/html/check was right now logging massive numbers of messages like this:
07:45
<MikeSmith>
Desired survivor size 44695552 bytes, new threshold 7 (max 15)
07:45
<MikeSmith>
[PSYoungGen: 21029K->128K(305856K)] 34967K->14066K(1004928K), 0.0010770 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
07:45
<MikeSmith>
1005653.545: [Full GC (System) [PSYoungGen: 128K->0K(305856K)] [PSOldGen: 13938K->13990K(699072K)] 14066K->13990K(1004928K) [PSPermGen: 16922K->16922K(21248K)], 0.0715880 secs] [Times: user=0.07 sys=0.00, real=0.08 secs]
07:45
<MikeSmith>
1005653.635: [GC
07:45
<MikeSmith>
oh wait
07:46
<MikeSmith>
that's another process
07:46
<MikeSmith>
which I just killed…
07:46
<MikeSmith>
oops
07:47
<MikeSmith>
somebody else was running it under the screen session I have set up for the validator.nu instance
07:47
<MikeSmith>
so, their bad for doing that
07:58
<micheil>
any editors of http://www.w3.org/TR/2011/WD-messaging-api-20110414/ about?
07:59
<MikeSmith>
micheil: I don't think any of them hang out on IRC on freenode, but dom is on #dap and #webapps on irc.w3.org, port 6665
08:00
<MikeSmith>
oh
08:00
<MikeSmith>
maxf is on freenode on #w3c
08:03
<micheil>
hmm..
08:03
<micheil>
well, yeah, essentially I really think that the API there is kinda crap.
08:04
<jacobolus>
oh, aho left. you can do lossy rgba by doing a jpg and then adding a mask
08:04
<jacobolus>
at least in webkit
08:05
<MikeSmith>
micheil: send comments to public-device-apis⊙wo
08:05
<MikeSmith>
http://lists.w3.org/Archives/Public/public-device-apis/
08:06
<MikeSmith>
micheil: "This draft proposes a vastly different approach to the previously published version, using URI schemes as a way to address different messaging protocols instead of using separate methods. The group is specifically looking for feedback on which approach is felt like the most useful."
08:07
<MikeSmith>
I guess the previous version is http://www.w3.org/TR/2011/WD-messaging-api-20110120/
08:08
<micheil>
hmm..
08:08
<micheil>
I feel like the messaging interface should inherit from DOM Events
08:08
<micheil>
like the WebSocket object.
08:08
<MikeSmith>
that would be useful feedback I think
08:09
<MikeSmith>
looking at the commit logs for that draft, it seems like Dominique is the main one working on it these days
08:09
<MikeSmith>
so chatting with him about it might be useful
08:09
<micheil>
okay
08:10
<hsivonen>
http://news.ycombinator.com/item?id=2095083 interesting
08:10
<MikeSmith>
micheil: I don't think that draft has gotten much review outside of the DAP WG yet
08:10
<micheil>
okay
08:10
<micheil>
I just saw it through the latest Weekly WHATWG
08:11
<MikeSmith>
"Google just hired him full-time for a year to work solely on xvp8"
08:12
<MikeSmith>
micheil: I'll ask Dom to consider posting a message to the public-webapps list asking for comments
08:12
<micheil>
xvp8?>
08:16
<MikeSmith>
https://github.com/rbultje/x264/tree/xvp8 has still not be updated, though
08:17
<MikeSmith>
so if he's been working on it again for the last month, he must be maintaining the code elsewhere
08:31
<MikeSmith>
ah, it's 選挙カー season in Japan once again
08:31
<MikeSmith>
public nuisance
08:32
<ezoe>
it's shave we still use such old way.
08:32
<ezoe>
shame
08:32
<ezoe>
we can't use internet for policitial activities.
08:33
<ezoe>
oh wait, this is #whatwg. why there is a japanese in here.
08:42
<micheil>
MikeSmith: did I manage to send you a message before my connection dropped at 09:43?
08:43
<micheil>
(time based on log time)
08:43
<micheil>
so, about 5 minutes ago.
08:43
<MikeSmith>
micheil: last message I got here from you was at :18
08:44
<MikeSmith>
or :17
08:44
<micheil>
okay, would you be able to review a proposal for the messaging WebIDL?
08:44
<MikeSmith>
sure
08:44
<micheil>
cheers
08:44
<micheil>
just working on it.
08:44
<MikeSmith>
OK
08:44
<MikeSmith>
can't promise I can review it today/tonight
08:44
<MikeSmith>
but can tomorrow
08:45
<MikeSmith>
I have a bunch of phone conferences tonight
08:45
<MikeSmith>
and trying to get some validator changes in today
08:46
<MikeSmith>
which reminds me…
08:46
<MikeSmith>
hsivonen: I have a review request out to you still
08:46
<MikeSmith>
the one for checking URLs in meta refresh values
08:47
<MikeSmith>
there's still no rush on getting it reviewed
08:47
<MikeSmith>
because it's not blocking me on anything else
08:48
<MikeSmith>
just hadn't heard back from you on it, so wasn't sure if you remembered
08:48
<jacobolus>
I don't understand the mozGetAsFile / toBlob thing
08:48
<jacobolus>
what's wrong w/ PNGs?
08:50
<hsivonen>
MikeSmith: I didn't realize that there's an outstanding review request. sorry
08:50
<MikeSmith>
no problem
08:50
<MikeSmith>
should I re-send it?
08:52
<hsivonen>
MikeSmith: no, r=hsivonen.
08:52
<MikeSmith>
cool
08:52
<MikeSmith>
thanks
08:52
<hsivonen>
MikeSmith: sorry about missing it when you sent it
08:53
<MikeSmith>
no worries
08:53
<MikeSmith>
I forgot about it too, til now :)
08:57
<micheil>
what's the difference between a sequence<DOMString> and DOMString[]
08:57
<micheil>
?
08:58
<Lachy>
micheil, that difference was just discussed on public-webapps recently
08:58
<micheil>
okay..
08:59
<Lachy>
I'll get a link.
08:59
<micheil>
k, cheers
09:00
<Lachy>
micheil, start here http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0203.html
09:00
<Lachy>
and read the rest of the messages in that thread
09:04
<micheil>
so, for something like an set of file attachments
09:04
<micheil>
I'd probably go with sequence<Blob>
09:04
<micheil>
or sequence<File>
09:05
<micheil>
(referencing the File API where needed)
09:18
<MikeSmith>
the "clearly state that there must be only one character encoding declaration in a document" spec bug I filed has been open for a month now with no response
09:18
<MikeSmith>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12054
09:18
<MikeSmith>
two months
09:35
<jgraham>
MikeSmith: You should talk to the team contact aboput how to escalate
09:35
<MikeSmith>
heh
09:36
<micheil>
MikeSmith: I think this is right: https://gist.github.com/ebd79f6cd4f620fc4fa7
09:37
MikeSmith
looks now
09:37
<micheil>
Essentially the previous draft had a good API (only instead of create* they become constructors)
09:38
<micheil>
as we don't do:
09:38
<micheil>
createXMLHTTPRequest
09:38
<micheil>
we just do:
09:38
<micheil>
new XMLHTTPRequest()
09:40
MikeSmith
compares with IDL in that previous draft
09:41
<micheil>
The main changes are:
09:41
<micheil>
- the additional DOMEvents inheritance
09:42
<micheil>
- the change of things from being required DOMString[]'s to being optionally a DOMString or an Array of DOMString's
09:42
<micheil>
- same with EmailAddress[]
09:42
<micheil>
- uses sequence<Blob> for attachments
09:43
<MikeSmith>
yeah
09:43
<micheil>
SMSMessage should inherit from both SMSMessageProperties and Message
09:43
<micheil>
I wasn't sure whether the syntax for that was:
09:43
<MikeSmith>
what's the use case of allowing an Array?
09:43
<micheil>
SMSMessage : Message, SMSMessageProperties {}
09:44
<micheil>
MikeSmith: multiple recipients
09:44
<micheil>
I want to send a message directly to john, fred, and bob
09:44
<MikeSmith>
it seems strange they didn't allow for that before
09:44
<hsivonen>
dear lazy IRC, does XHR support XML parsing only for XML content types?
09:45
<hsivonen>
or does it allow, e.g. text/plain or text/html to be parsed as XML?
09:45
<micheil>
MikeSmith: the previous draft did.
09:45
<MikeSmith>
oh, OK
09:45
<micheil>
hsivonen: hmm.. I don't think it does even support XML parsing, does it?
09:45
<hsivonen>
micheil: it sure does
09:45
<micheil>
actually, yeah, it does: http://www.w3.org/TR/XMLHttpRequest/#document-response-entity-body
09:46
<micheil>
so, it has to have +xml in it.
09:46
<micheil>
text/xml, application/xml, text/foo+xml
09:47
<hsivonen>
ok. so in which spec will annevk be setting override MIME type to non-null?
09:48
<hsivonen>
http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#dom-xmlhttprequest-overridemimetype
09:49
<micheil>
MikeSmith: any thoughts on syntax?
09:50
<hsivonen>
I suppose there will be no one explaining XHR Level 2 design decisions to me until annevk returns
09:50
<MikeSmith>
micheil: no, it looks sane to me overall
09:50
<hsivonen>
yay for getting stuff done in Q2
09:50
<micheil>
okay.
09:51
<MikeSmith>
micheil: I never looked at the original draft at all before today, so I don't have much to go on. but I think what you have at https://gist.github.com/ebd79f6cd4f620fc4fa7 is worth more review and discussion
09:51
<hsivonen>
I'm rather unhappy about the prospect of the MIME type of XHR getting overridden *after* the request has been initiated
09:51
<micheil>
MikeSmith: Do most of the JavaScript specs actually have people who write javascript on a daily or weekly basis on their authors list?
09:53
<micheil>
:/ I have a very awful feeling that my internet speed has been shaped
09:55
<MikeSmith>
micheil: if you mean the EcmaScript specs, I dunno
09:55
<micheil>
no, the JavaScript API's
09:55
<MikeSmith>
if you mean the W3C specs that have APIs with JS bindings
09:55
<MikeSmith>
oh
09:55
<MikeSmith>
no, those don't I guess
09:55
<MikeSmith>
mostly
09:55
<micheil>
eg, Geolocation, WebSockets, etc.
09:56
<jgraham>
micheil: Inevitably spec editors (of all types) tend to be langauge geeks rather than working authors
09:56
<jgraham>
Since working authors are, well, working as authors
09:56
<micheil>
if they don't, then they should probably put out an open hand to get people on board who use the languages
09:56
<jgraham>
In theory the open hand is there
09:56
<MikeSmith>
well, Hixie doesn't write JS on a weekly basis, but he seems to be able to write sane APIs
09:56
<jgraham>
Although the W3C hand is "open except where it isn't"
09:57
<jgraham>
And in general the problem is not that feedback is unwelcome but that there is a barrier to entry
09:57
<MikeSmith>
I guess the DAP list has less participation from working Web developers
09:57
<MikeSmith>
though they are trying to get more
09:57
<jgraham>
Caused by the fact that people don't know that feedback is welcome or don't have time to participate or whatever
09:57
<micheil>
MikeSmith: on hixie, "saner APIs"
09:58
<micheil>
I'd really love to see the W3C become entirely open.
09:59
<micheil>
So that individual developers have a say, rather than just individuals backed by corporations.
09:59
<MikeSmith>
I think the current crop of APIs in Web-platform specs are way better than ones we have had in the past, at least
09:59
<micheil>
there should be no private and public email lists, just public lists.
10:00
<MikeSmith>
as far as the area of W3C work that I'm involved in, we already pretty much have no private lists
10:00
<MikeSmith>
all technical discussion takes place on public lists that anyone can subscribe to and post to
10:00
<_o>
micheil, w3c feels pretty open to me, have never had a problem that way, and I am just an individual developer not backed by any corporation
10:00
<MikeSmith>
well, with the exception of the public-html list, which only members of the HTML WG can post to
10:01
<MikeSmith>
but there are good reasons for that
10:01
<webr3>
likewise public-rdf is the same, but both rdf and html have *-comments lists for community feedback
10:01
<micheil>
MikeSmith: to me, a lot of the working groups always have seemed incredibly closed communities.
10:01
<jgraham>
-comments lists are badness I think
10:01
<webr3>
(and are still publi)
10:02
<micheil>
at least public-html is publicly viewable.
10:02
<webr3>
micheil, strange, I agree - always thought the same, however found different when I put my assumptions to one side - wonder what it is that conveys that to the masses
10:03
<hsivonen>
I'm at times annoyed at charter reviews being secret and (especially) Team responses to charter review comments being secret
10:03
<othermaciej>
hsivonen: did this happen to one of your personal charter review comments?
10:04
<MikeSmith>
micheil: that culture has changed significantly during the last few years
10:04
<webr3>
sure as hell there are /many/ more people that are interested and would contrib to the work, but they don't even consider it as being a possibility - perhaps a throw back of older closed up tech groups for geeks-we-know only - as people do openly join and comment on open source projects all the time
10:04
<micheil>
I think all lists should be public (other wise we could almost have a cable-gate style hacker search for answers :P)
10:05
<hsivonen>
othermaciej: well, I don't send personal charter review comments
10:05
<MikeSmith>
e.g., the WebApps WG isn't really a unique community at all -- it's sorta several sometimes overlapping communities, and many of the same people who participate on the whatwg mailing list, and here
10:05
<hsivonen>
othermaciej: let's say it has happened with charter review comments that I am interested in
10:06
<MikeSmith>
micheil: some of the people who post the most useful technical feedback on W3C mailing lists -- stuff that actually results in spec changes -- are not members of any W3C working groups
10:07
<MikeSmith>
micheil: that lists that matter are all public
10:07
<micheil>
I think all lists fullstop should be public.
10:08
<micheil>
there shouldn't be that veil of secrecy
10:08
<hsivonen>
othermaciej: basically, I've never noticed any other organization than Mozilla making their charter review comments public
10:08
<jgraham>
MikeSmith: There are some things that are still very much closed e.g. only capital-M Members get any substantive voice in the spec licensing
10:08
<hsivonen>
othermaciej: and all responses to charter review comments are secret
10:08
<MikeSmith>
jgraham: yeah, true
10:08
<MikeSmith>
jgraham: well, not totally true
10:09
<jgraham>
Sure, there is feedback from the community
10:09
<micheil>
For instance, it's only recently that I've started asking questions and suggesting things in the WebSocket's discussions, as I didn't feel as though any of my comments were ever being heard, unless I spoke to hixie directly
10:09
<MikeSmith>
yeah, I would not say that are the only ones that get a substantive voice
10:09
<jgraham>
But it is possible for the Members to ignore that entirely if they choose
10:10
<MikeSmith>
jgraham: not exactly. because it's not being put a simple vote
10:10
<jgraham>
Oh, well maybe it is even more complex than I thought.
10:11
<MikeSmith>
micheil: not sure what to suggest about that. That's not a problem unique to W3C working groups. You can post to the whatwg list and never get responses either. It's mostly just a question of timing and people being too busy to respond
10:12
<MikeSmith>
micheil: have you posted to the hybi list?
10:12
<jgraham>
MikeSmith: (Hixie will later point out that he responds to all substantive comments to whatwg)
10:12
<hsivonen>
doh. I failed to put [XHR2] in the subject line of my email to public-webapps
10:12
<jgraham>
MikeSmith: (I can't verify this)
10:13
<MikeSmith>
jgraham: yeah, in my experience, he actually does
10:13
<MikeSmith>
though it may be a year or two before he does
10:14
<jgraham>
Indeed, the latency can be quite high
10:15
<MikeSmith>
I think it's lower these days, though
10:15
<MikeSmith>
for the last couple years
10:15
<jgraham>
It depends what you comment on, I think
10:15
<MikeSmith>
sure
10:18
<benschwarz>
MikeSmith: You're right about too busy. I'd love to be as involved as I was even a few months ago
10:18
<benschwarz>
so I think the answer is that organisations like the w3c and whatwg need to make it clear about the feedback that they're looking for…
10:18
<benschwarz>
in micro updates
10:18
<benschwarz>
perhaps tweets to discussion threads about given things here or there
10:19
<MikeSmith>
that requires people who have some time and enthusiasm for doing that
10:19
<benschwarz>
because I know what peices of web technology I feel strongly about if I see them in my twitter feed
10:19
<MikeSmith>
karl was great about getting information out when he was on the W3C team
10:19
<benschwarz>
and would act at the time
10:20
<benschwarz>
MikeSmith: perhaps its time that the w3c employed some "developer evanglists" like technology companies do
10:20
<benschwarz>
budgetry is hard, of course
10:21
<benschwarz>
there does need to be a change of mindset though
10:21
<benschwarz>
amongst the greater web™
10:22
<benschwarz>
also, I've posted to whatwg and never had any replies
10:22
<benschwarz>
I guess you wonder why you bothered when that happens
10:23
<MikeSmith>
developer evangelism is something that everybody on the team is expected to do as part of their job, I guess
10:23
<jgraham>
benschwarz: The thing about microupdates is that the s/n is too low for people to follow
10:23
<MikeSmith>
I suppose Philippe and Doug do a lot more of it than I do
10:24
<jgraham>
benschwarz: If you are only interested in one message out of 100 you aren't going to subscribe
10:24
<jgraham>
And if you are interested in 50 / 100 then you should probably be on the list instead
10:24
<jgraham>
Plus the world isn't really organised like that
10:25
<jgraham>
I mean specs develop in parallel, so it's not like there is exactly one thing at any given time
10:25
<MikeSmith>
I think the focus more should be on trying to get features in specs actually implemented on deployed on a large scale
10:26
<MikeSmith>
anyway, I need to step away for a bit
10:26
<MikeSmith>
back later
10:32
<micheil>
benschwarz: I'd probably do it for free, in the vein that I want a better web.
10:32
<micheil>
Just like I contribute to Open-Source software, I want better software, libraries, platforms, frameworks, etc.
10:35
<benschwarz>
micheil, the very fact that you log here somewhat proves that
10:36
<benschwarz>
but thats true of all of us, isn't it?
10:36
<micheil>
benschwarz: fair point
10:49
<jacobolus>
so I'm finding in my current application that I really want to get at the content of the current transformation matrix in several places
10:49
<jacobolus>
in canvas
10:50
<jacobolus>
I think I'm going to just write helper functions wrapping up all the canvas transformation functions and simultaneously saving the current matrix in jquery.data
10:50
<jacobolus>
in a stack, that gets pushed to/popped from when I do save/restore
10:51
<jacobolus>
then I'll be able to get the current transformation at any time, and do various useful stuff with it, like figuring out the nearest pixel to a point so that I can draw along pixel boundaries and avoid antialiasing
10:53
<jacobolus>
and keeping the translation but resetting the scale/rotation, so that I can draw relative to device pixels, but at a given point in the current transformation space
10:54
<jacobolus>
I don't think using stuff that looks like "translate(context, ...)" will be too much worse than "context.translate(...)"
10:54
<jacobolus>
in terms of code readability
10:55
<jacobolus>
though it might make more sense to just make a "canvas wrapper" object and make all these things methods
10:56
<jacobolus>
in which case I wouldn't have to bother with jquery.data for saving the state
11:43
<jacobolus>
typo in css 2d transforms spec
11:43
<jacobolus>
"The CSSMatrix interface represents a 4x4 homogeneous matrix"
11:43
<jacobolus>
.... "Each of these attributes represents one of the values in the 3x2 matrix."
11:44
<karlcow>
benschwarz: does the work of shelley powers on the blog http://blog.whatwg.org/ or mine on http://www.w3.org/QA/archive/open_web/ help?
11:44
<karlcow>
Would you prefer something in addition of that?
11:50
<hsivonen>
browser vendors who maintain XML parsing capability might be interested in http://lists.w3.org/Archives/Public/public-xml-processing-model-comments/2011Apr/0005.html
11:51
<jacobolus>
who was it that was telling me yesterday about canvas matrices being written in column-major order? well bah, svg matrices are written row-major
11:51
<jacobolus>
annoying
11:52
<jacobolus>
is it possible to create/manipulate CSSMatrix objects from JavaScript?
11:53
<jgraham>
hsivonen: I presume we would collectively ignore any attempt to require procesing external entities
11:54
<hsivonen>
jgraham: they aren't really *requiring* it. they are using words that give more ammo to people who want to argue in bug reports.
11:54
<jacobolus>
oh, I guess that's not a typo in the css 2d transform spec; it's just really confusing
11:54
<jacobolus>
confusing since that spec doesn't explain why 4x4
11:57
<jgraham>
hsivonen: Yeah. I am unconvinced that the cost of arguing upfront is not greater than the cost of wontfixing the bugs but maybe I am wrong
11:58
<zcorpan>
hsivonen: i see little value in the xml profiles spec to begin with
11:58
<zcorpan>
so i've put it on my ignore list
11:59
<jacobolus>
oh, I see, it's called WebKitCSSMatrix
12:00
<jacobolus>
I guess if I'm writing code for doing matrix math I should defer to that where available?
12:07
<Philip`>
jacobolus: You could probably override CanvasRenderingContext2D.prototype.translate or something, maybe, though that's probably evil
12:08
<jacobolus>
Philip`: override it?
12:09
<Philip`>
Like set it to a different function
12:09
<Philip`>
which will get called when you do ctx.translate()
12:09
<jacobolus>
hmm, I don't want to do that
12:09
<jacobolus>
that seems evil :)
12:09
<Philip`>
(I don't know if all browsers support that, though)
12:09
<Philip`>
It is :-)
12:09
<jacobolus>
I think the wrapper way is best maybe
12:09
<jacobolus>
just make a "SnazzyCanvas" class
12:10
<jacobolus>
Philip`: did you see some of my nifty coffeescript canvas bits?
12:10
<Philip`>
Someone should make a standard canvas wrapper class with all the nice API features that people ever ask for
12:10
<Philip`>
rather than everybody either writing their own or asking for it to be in the spec
12:11
<jacobolus>
Philip`: I've got helper functions like these: http://pastie.textmate.org/private/igg5gtdbue68crt6jjdrra
12:11
<jacobolus>
so I can then write stuff like http://pastie.textmate.org/private/o96lu7ppljzjd1feijzg
12:13
<jacobolus>
Philip`: I think a standard canvas wrapper is a good idea, though if I was writing it I'd be tempted to use a lot of anonymous functions that people using javascript instead of coffeescript might not be the biggest fans of, in in JS they're kind of syntactically heavy
12:16
<jacobolus>
[whoops, a couple typos in those, but they give the right idea]
12:24
<MikeSmith>
hsivonen: I see at least that "minimum XML processor profile" has at least changed to not require external entity processing
12:24
<MikeSmith>
originally, it did
12:24
<MikeSmith>
so there was no profile that browsers could match
12:24
<hsivonen>
MikeSmith: whoa. that was a pretty bad "originally" starting point
12:24
<MikeSmith>
yeah
12:25
<zcorpan>
i think it was in that state when i looked at it before
12:25
<MikeSmith>
http://www.w3.org/TR/2010/WD-xml-proc-profiles-20100518/#minProfile
12:25
<MikeSmith>
I remember commenting on that at time
12:25
<MikeSmith>
well, "commenting" here at least
12:25
<MikeSmith>
not on any list
12:33
<jacobolus>
Philip`: oh wow, speaking of canvas wrappers: in may 2008, john resig's processing.js was 1.7 KLOC. Now it's 19 KLOC
12:34
<jacobolus>
(700 KB. ooph)
12:36
<jacobolus>
anyway, though, if there are obvious "nice API features that people ask for", I'd love to hear about them
12:49
<MikeSmith>
hsivonen: anyway, it seems like the XML Profiles "Recommended" thing is a bit of a naming issue
12:49
<MikeSmith>
they could label it something else
12:50
<MikeSmith>
and it might actually be worthwhile to suggest another label for it
12:50
<zcorpan>
anyone know what problem they're solving with that spec?
12:50
<zcorpan>
MikeSmith: hsivonen already suggested 'Legacy'
12:51
<MikeSmith>
heh
12:51
<MikeSmith>
ah, I see that now
12:52
<zcorpan>
maybe rename the minimal profile to 'Minimal legacy'
12:52
<MikeSmith>
I guess I should have read his whole message, rather than jumping around
12:52
<MikeSmith>
I don't think "Legacy" is going to fly with that WG
12:52
<zcorpan>
jumping around is good for blood circulation
12:52
<MikeSmith>
heh
13:51
<jacobolus>
Philip`: oh, you probably know about this thing, but it's kind of neat http://code.google.com/p/canto-js/source/browse/trunk/canto.js
14:14
<_bga>
function C, function T, ...
14:14
<_bga>
APLer
14:16
<_bga>
also good smile ._.
15:21
<wilhelm>
Oh, this will be fun. Opera handles 204 MIME-types natively, of which only a limited subset should be overridable by registerContentHandler().
15:22
<hsivonen>
wilhelm: whoa! is there a public list of the mime types?
15:22
<wilhelm>
hsivonen: Not at the moment. I'm grepping source code. (c:
15:22
<hsivonen>
wilhelm: does that include weird stuff like mechanisms that *ask* the cellular provider's transparent proxy to MITM HTTP connections for acceleration
15:23
<hsivonen>
BTW, that request header is pure bloat when the user is on a network that doesn't have that kind of transparent proxy
15:23
<wilhelm>
hsivonen: No, I don't think so.
15:24
<wilhelm>
Oh, it seems it's just 102.
15:24
wilhelm
digs in.
15:50
<MikeSmith>
wilhelm: nice catch (about Disallowing dots in the protocol argument of registerProtocolHandler()
15:51
<erlehmann>
hsivonen, usually, cell providers do that without asking. or so i experienced in in the germanies.
15:52
<hsivonen>
erlehmann: do what exactly?
15:52
<wilhelm>
MikeSmith: Thanks. register*Handler() are very nice, but they're disasters waiting to happen. We have to step very carefully here. (c:
15:53
<hsivonen>
erlehmann: Opera Mobile 11 sends an X-EBO-UA request header
15:54
<MikeSmith>
wilhelm: true, but it's a very useful feature, and most very useful features often seem to have some gotchas waiting
15:54
<erlehmann>
hsivonen, MITM HTTP connections.
15:54
<erlehmann>
i switched away from t-mobile for that reason.
15:54
<wilhelm>
MikeSmith: Absolutely.
15:54
<erlehmann>
the O2 salesman apparently figured out he can get me with „we respect net neutrality“
15:54
<hsivonen>
erlehmann: If my googling skills work, this tells some proprietary product hosted by the network provider that Opera accepts stuff that has been munged by this EBO thing
15:54
<erlehmann>
hehehe
15:55
<hsivonen>
erlehmann: isn't there a law against the network conduit tampering with the messages in transit?
15:56
<hsivonen>
the value of the X-EBO-UA header is remarkably long
15:56
<erlehmann>
hsivonen, there should be, but i have no idea how it would apply. t-mobile also actually seemed to block voip and instant messaging services back then, charging to „enable it“ (probably still do it now)
15:57
<hsivonen>
erlehmann: wow. that sounds like U.S. badness--not something that should be happening in the EU
15:57
<wilhelm>
hsivonen: I wish there was. My favourite operator MITH munging bug was the one where an operator proxy looked at the DOCTYPE of the loaded document. If it was XHTML, it would serve it with an XML MIME type instead of text/html.
15:58
<hsivonen>
the European style is tampering with DNS to change the records of domains that the police doesn't approve of
15:58
<wilhelm>
s/MITH/MITM
15:58
<hsivonen>
wilhelm: bad craziness. what was that supposed to accomplish?
15:58
<wilhelm>
Since there are only five valid XHTML documents on the Web, every single Web page broke.
15:59
<wilhelm>
hsivonen: I have no idea. (c:
15:59
<erlehmann>
hsivonen, what i dislike most about those compressing proxies is that they use assumptions that work in 90% of cases and break stuff in the rest of cases. like, the admin tools for an imageboard i shall not name did not work anymore (we switched to HTTPS later)
16:00
<wilhelm>
So, uh, there are a couple of old Opera OEM deliveries that will always parse XML as HTML. :P
16:00
<wilhelm>
That was the lesser evil.
16:00
<erlehmann>
wilhelm, i find that funny.
16:00
<erlehmann>
those who live by the XHTML doctype, die by it.
16:01
<wilhelm>
Well, it was just Opera that did the dying. :P
16:01
<erlehmann>
oh well, yeah, some compressing proxies actually manage to invalidate perfectly fine XML documents by inserting bogus markup.
16:03
<wilhelm>
A related, very fun bug is that some IIS servers insist on sending text/xml instead of text/html to Opera.
16:03
<erlehmann>
>IIS
16:03
<erlehmann>
i see what you did there
16:03
<wilhelm>
Based on accept headers? No. Browser sniffing.
16:03
<wilhelm>
So all other browsers get text/html, and all works well.
16:06
<wilhelm>
Here's an example: http://home.mcafee.com/campaign.aspx?cid=77419&affid=0&ctst=1
17:31
<karlcow>
wilhelm: sounds like http://my.opera.com/ODIN/blog/2011/03/30/improving-interoperability-the-story-of-a-bug
17:32
<karlcow>
yup
17:32
<karlcow>
Server: Microsoft-IIS/7.0
17:32
<karlcow>
X-Powered-By: ASP.NET
17:33
<karlcow>
for curl -sI "http://home.mcafee.com/campaign.aspx?cid=77419&affid=0&ctst=1";
17:33
<karlcow>
http://www.rohanradio.com/getting-aspnet-to-play-nice-with-opera-wget
17:36
<TabAtkins>
Sigh. Abstraction is hard.
17:36
<jgraham>
Let's go shopping?
17:36
<GarethAdams|Home>
TabAtkins: Abstraction is (a kind of) hard
17:36
<TabAtkins>
Heh.
17:37
<TabAtkins>
Anyway, one of my team just found a problem with my Animations proposal, so I'm drawing a diagram to more clearly illustrate it (and have an excuse to improve my SVG), then I'll have to brainstorm around the issue.
17:40
<hober>
Hixie: you might get to publish HTML5 in HTML5 after all: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9961#c3
17:40
jgraham
learns to his amuement that the PC alternative to "brainstorm" is "mindshower"
17:40
<jgraham>
*amusement
17:41
<TabAtkins>
jgraham: Wut.
17:44
<jgraham>
TabAtkins: Apparently someone somewhere thinks that brainstorm might be offensive due to the fact that it can also mean "seziure"
17:44
<TabAtkins>
Someone is retarded.
17:45
<TabAtkins>
Also: anyone who calls a seizure a "brainstorm" is an idiot, because the term was already taken.
17:45
jgraham
always wonder if they do carefully controlled studies to determine stasistically significant deltas in offence taken for these cases
17:45
<jgraham>
*statistically
17:47
<jgraham>
TabAtkins: If I had access to the proper OED I could probably find out if you are right about the order in which the term was given each meaning
17:47
<gsnedders>
TabAtkins: And anyone who uses any euphemism is also an idiot, because all terms already existed?
17:47
<gsnedders>
jgraham: heh, good thought. *logs onto OED*
17:48
<TabAtkins>
gsnedders: Anyone who uses a euphemism that's already taken, and then gets offended by the previous usage, is.
17:48
<jgraham>
(obviously I agree that being offened in this case would be ridiculous)
17:48
<TabAtkins>
Similar to people getting offended by british-english speakers saying "fag".
17:48
<jgraham>
(but not nearly as ridiculous as using the term "mindshower" in public)
17:50
<jgraham>
(I mean honestly, "mindshower"?!)
17:50
<gsnedders>
TabAtkins: brainstorm seems to have meant a seizure first, so the term was already taken when it came to have its common meaning now
17:51
<jgraham>
(the only possible use of that has is "I just accidentially looked at goatse and now I need a mindshower")
17:51
<TabAtkins>
gsnedders: Darn, okay. Well then I have an alternate way to be offended!
17:52
<TabAtkins>
It's similar to the kerfuffle over Tiger Woods referring to himself as a "spaz", when the term has lost all negative connotations in american english (to the point where nearly all americans are unaware there even *is* a medically pejorative meaning).
17:53
<jcranmer>
there is a medically pejorative meaning?
17:54
<TabAtkins>
It refers to people who are spastic, with that referring to some type of neural disorder.
17:54
<jcranmer>
I that spazzing just meant freaking out
17:54
<gsnedders>
TabAtkins: What sense you use a word in is what determines whether it is offensive or not. Certainly, I think "fag" as an insult is still frequently used in much the same way as something more direct like "homo" is, at least when I've had it shouted at me.
17:54
<jgraham>
jcranmer: http://en.wikipedia.org/wiki/Spasticity
17:54
<TabAtkins>
gsnedders: Of course! Which is yet another layer of idiocy on the mindshower thing.
17:54
<TabAtkins>
I can use "chuwero" in an offensive manner, despite it being a nonsense racial epithet.
17:55
<jcranmer>
bullplop
17:58
<MikeSmith>
about http://html5.org/r/6008 -
17:58
<MikeSmith>
should <table border> be valid?
17:59
<MikeSmith>
that is, <table border> instead of <table border="">
18:00
<TabAtkins>
Unless something went crazy with the decision (given that it was built from Leif's text, not impossible), the two are equivalent in every way.
18:00
<MikeSmith>
ok
18:02
<micheil>
hmm.. the guys behind the netinfo api should really talk with the sysinfo guys: http://dev.w3.org/2009/dap/system-info/Overview.html#network
18:28
<TabAtkins>
gsnedders: Quit abusing the spec feedback system http://www.w3.org/Bugs/Public/show_bug.cgi?id=12523
18:28
<gsnedders>
Meow?
18:28
<gsnedders>
Meow.
18:28
<jgraham>
gsnedders: You are not shoelaces
18:29
<gsnedders>
TabAtkins: Just be glad you haven't seen me with friends here. We have whole conversations just meowing at each other. (And yes, we can tell what we mean.) ^_^
18:30
<TabAtkins>
Well, sure, you can tunnel information through almost any communication medium.
18:31
<jgraham>
gsnedders actually does http over ssh over meow
18:31
<jgraham>
Whenever he wants to tell anyone something he has to phrase it as a POST
18:32
<jgraham>
Doing the decryption is a bitch though
18:32
<gsnedders>
Meow?
19:05
<Hixie>
benschwarz: when did you send the e-mail that you haven't gotten a reply to?
19:06
<Hixie>
benschwarz: with all the htmlwg stuff i haven't been able to respond to feedback at all for a few months now
19:06
<Hixie>
except for specific things like multitrack
19:42
<TabAtkins>
MikeSmith: I dunno who I should talk to, but the permissions on http://dev.w3.org/csswg/css3-content/Overview.html are suddenly borked.
19:42
<TabAtkins>
http://dev.w3.org/csswg/css3-content/Overview.src.html is still okay.
19:46
<MikeSmith>
TabAtkins: checking now
19:46
<MikeSmith>
weird
19:46
<MikeSmith>
all dev.w3.org content is public
19:47
<MikeSmith>
in my experience
19:47
<TabAtkins>
Indeed.
19:47
<TabAtkins>
Dunno how it got messed up.
19:48
<TabAtkins>
Last CVS-based change was over 6 months ago, and I know it was working normally a month or two ago.
19:49
<MikeSmith>
fantasai checked in that error page
19:49
<MikeSmith>
overwrote the actual content
19:49
<MikeSmith>
as far as I can see
19:49
<TabAtkins>
...
19:49
<TabAtkins>
awesome
19:49
<MikeSmith>
http://dev.w3.org/cvsweb/csswg/css3-content/Overview.html
19:50
<TabAtkins>
Maybe last thing I checked was the TR?
19:50
<TabAtkins>
I'll fix it, then.
19:50
<MikeSmith>
http://dev.w3.org/cvsweb/csswg/css3-content/Overview.html.diff?r1=1.2;r2=1.3;f=h
19:50
<MikeSmith>
OK
19:50
<TabAtkins>
Ooh, I'll bet she used Chrome or something that makes another GET request to the resource when you do a Save.
19:51
<MikeSmith>
yup
19:51
<TabAtkins>
SO DUMB
19:51
<MikeSmith>
well, not dumb
19:51
<MikeSmith>
fantasai ain't dumb…
19:51
TabAtkins
keeps a Firefox up for the sole purpose of saving generated specs.
19:51
<TabAtkins>
No, Chrome is dumb.
19:51
<MikeSmith>
ah
19:51
<TabAtkins>
Fantasai made an easy mistake. Pretty sure I've done that before.
19:52
<MikeSmith>
me too
19:52
<MikeSmith>
browsers is dum
19:52
MikeSmith
kicks browsers
19:54
<TabAtkins>
Actually, she would have gotten a nearly-blank page with "unknown request" or whatever on it if she'd done that.
19:54
tw2113
read that with the intro to Beastie Boys' song "You Gotta Fight"
19:54
<TabAtkins>
I suspect she used one of the wget scripts without supplying proper auth.
19:55
<gsnedders>
If I wanted to be condesending and annoying, I'd call her a silly little girl at this point.
19:55
<TabAtkins>
What's the point in that? It was a simply mistake.
19:56
<gsnedders>
to be condesending and annoying
19:56
<TabAtkins>
The tools for generating our specs are annoying.
20:01
<MikeSmith>
respec is better than most
20:02
<MikeSmith>
OK, I just implemented support for the decision about table border
20:02
<MikeSmith>
http://html5.org/r/6008
20:03
<MikeSmith>
value of border must be either 1 or empty string
20:03
<bga_>
i want 0, 2*Math.PI as default arguments in Canvas2D#arc
20:03
<MikeSmith>
if anybody cares to test it at http://www.w3.org/html/check
20:04
<bga_>
writing it each time so annoying
20:04
<MikeSmith>
and let me know if you find bugs
20:04
<MikeSmith>
and/or add comments at http://bugzilla.validator.nu/show_bug.cgi?id=825 (and reopen)
20:06
<jgraham>
gsnedders: If I wanted to be annoying I would laugh at you because they are using respec and not anolis
20:06
<bga_>
but can wrap .arc in Canvas.prototype
20:06
<bga_>
yeah
20:06
<gsnedders>
jgraham: I don't care about Anolis :P
20:09
<wilhelm>
Hixie: I would absolutely be more comfortable with a whitelist for registerProtocolHandler() – at least until we see how the feature will be used in the wild.
20:09
<MikeSmith>
I weep for Anolis, he is dead!
20:16
<wilhelm>
Hixie: The same applies to registerContentHandler(), really. Opera's default blacklist would have to be about 100 entries long – only including MIME-types the browser has native support for. We should probably blacklist some MIME-types covered by plugins too. |c:
20:20
<MikeSmith>
gsnedders: have you read James Kelman?
20:21
<gsnedders>
MikeSmith: no
20:21
<MikeSmith>
gsnedders: I'm reading "How late it was, how late"
20:22
<MikeSmith>
and this is just about the greatest book I have read in a gazillion years
20:29
<TabAtkins>
CSSWG doesn't use respec, though. We use a collection of perl scripts that Bert wrote, conveniently packaged into a cgi.
20:30
<MikeSmith>
TabAtkins: sadly, those ain't even perl scripts
20:30
<MikeSmith>
the source for those this a thing of wonder
20:31
<MikeSmith>
*is a thing of wonder
20:31
<Hixie>
wilhelm: yeah; harder to know what to do with the mime type case, realistically, since there are far more types that make sense to whitelist
20:31
<gsnedders>
TabAtkins: It's mainly C stuff
20:31
<TabAtkins>
Awesome.
20:31
<MikeSmith>
gsnedders: no it's not
20:31
<jgraham>
Oh, I thought it was a complex system of ants and tunnels
20:31
<MikeSmith>
it is from an era that predates perl and C
20:31
<MikeSmith>
jgraham: yah, more like that
20:32
<MikeSmith>
reading the source of it is an educational experience
20:33
<jgraham>
It educates you that you have better - or at least less mindbending - things to do with your life?
20:34
<MikeSmith>
it's cheaper than other mind-altering substances
20:34
<MikeSmith>
and less un-legal
20:34
<jgraham>
Ah, is that also why W3C strictly controls access?
20:35
<MikeSmith>
yes
20:35
<MikeSmith>
we cannot unleash the hallucinogenic power of boscode on the unwashed masses
20:36
jgraham
presumes "boscode" is an ant-powered analog of bytecode or machine code
20:38
<MikeSmith>
"boss" code (extra(neous) "s" removed for extra efficiency…)
20:39
<MikeSmith>
http://dev.w3.org/csswg/?C=M;O=D
20:39
<MikeSmith>
good god almighty
20:39
<MikeSmith>
and they claim that the HTML spec is too big and complicated
20:39
<MikeSmith>
modularization wtf
20:40
<MikeSmith>
solve the complexity problem by spreading it as widely as possible
20:42
<TabAtkins>
Basically, yeah.
20:42
<TabAtkins>
The ideal is a bunch of loosely-interacting modules, so you can read one without having to know too much about the others.
20:43
<TabAtkins>
This doesn't always happen.
20:43
<hober>
witness the N grid/layout drafts of late
20:43
<TabAtkins>
More than that, though, it's a hack around the W3C process. CSS found a way to get a Living Standard within the Rec process.
20:44
<MikeSmith>
+1 to living standards
20:44
<MikeSmith>
as opposed to dead ones
20:44
<TabAtkins>
The layout drafts are a good example of the "loosely-interacting modules", actually. The interaction surface is still somewhat badly defined, but I'm working on that within Flexbox, and what I learn should spread to Grid.
20:45
<TabAtkins>
And then to Table, when somebody writes that some day.
20:45
<jgraham>
TabAtkins: The hack being that you can stop taking anything to Rec and always have N-1 things left to work on?
20:45
<TabAtkins>
jgraham: I don't understand what you're trying to make fun of, unfortunately.
20:47
<jgraham>
Nothing really. I think The Process is pretty silly. But I am not sure the CSS approach is good either
20:48
<jgraham>
One effect seems to be that it is easy to ignore the conceptual bits and hope that someone fixes them later
20:48
<TabAtkins>
Well, it's already paying dividends with a few specs moving higher in the Rec track well before anything else.
20:48
<TabAtkins>
Yes, that's a side-effect we've discovered.
20:50
<wilhelm>
Hixie: Indeed. We could make a low-friction process for the whitelist, though. If we maintain a canonical whitelist accompanying the spec, deploying updated lists to at least Opera installations worldwide is trivial. Opera already phones home once per week, asking for an updated IDN whitelist, browser.js, UA string spoof list, etc. A MIME-type whitelist wouldn't add much overhead. (I don't know if other UAs do something similar, though. If they don't, disregar
20:51
<TabAtkins>
Chrome obviously does something similar.
20:51
<wilhelm>
That makes two… (c;
20:51
<TabAtkins>
And I'm pretty sure FF phones home for some lists. IE does for their compat lists.
20:52
<gsnedders>
wilhelm: " If they don't, disregar"
20:52
<jgraham>
Having to maintain a weekly list for such a little-used feature seems like a drag though
20:52
<wilhelm>
gsnedders: … disregard this suggestion. :)
20:53
<wilhelm>
21:58 -!- Irssi: Loaded script splitlong
20:53
<wilhelm>
:P
20:53
<gsnedders>
wilhelm: Also, go and have fun today. :P
20:53
<jgraham>
wilhelm: I was about to say, it was you instructing on the use of that :p
20:53
<Hixie>
ooh how do we get splitlong!
20:53
<Hixie>
and why is it not a default
20:53
<jgraham>
gsnedders: Maybe this is his idea of fun
20:53
<wilhelm>
/load splitlong.pl
20:53
<TabAtkins>
Aw yus.
20:54
<wilhelm>
gsnedders: I am! I'm playing Dragon Age II.
20:54
<Hixie>
awesome
20:54
<wilhelm>
gsnedders: And eating cake. An as good birthday as any. (c;
20:54
<jgraham>
wilhelm: irc with one hand, games with the other and a cocktail balanced on your lap?
20:54
<jgraham>
Oh cake is better
20:55
<tw2113>
cake rocks
20:55
<wilhelm>
jgraham: Pretty much. (c:
20:55
gsnedders
is going bowling tomorrow… 9, 19… what's the difference? :)
20:58
<jgraham>
wikipedia claims that rock cakes are a common feature in Harry Potter
20:58
<jgraham>
Is that true?
20:59
jgraham
doesn't remember them appearing
21:00
<TabAtkins>
I recall seeing them at least once.
21:00
<TabAtkins>
Don't know where, but it definitely pings my memory.
21:00
<TabAtkins>
...why?
21:01
<jgraham>
It just seems wrong. I mean they might pop up once or so
21:01
<TabAtkins>
I wouldn't call them a "common feature", no.
21:03
<MikeSmith>
Harry Potter books are a painful read
21:03
<MikeSmith>
but the movies are pretty good
21:04
<MikeSmith>
which seems to support the notion that bad books make good movies
21:04
<MikeSmith>
and good books don't
21:04
<tw2113>
i haven't read the books, just listened to someone else read them to me
21:05
<MikeSmith>
hard to imagine a movie version of "How late it was, how late"
21:05
<TabAtkins>
They're okay as books. Definitely pretty good for YA fiction.
21:05
<gsnedders>
Definitely far better than, e.g., Twilight.
21:06
<MikeSmith>
well
21:06
<MikeSmith>
lacking in humor, all
21:06
<MikeSmith>
nowhere like the Series of Unfortunate Events books
21:06
<TabAtkins>
Well, yeah, that's explicitly a humorous series.
21:06
<MikeSmith>
as far as young-adult fiction
21:07
<MikeSmith>
and that movie sucked
21:07
<MikeSmith>
because of that ass Jim Carrey
21:07
<MikeSmith>
who can ruin singlehandedly anything he's in
21:07
<tw2113>
i need to get myself re-listening to the 7th HP book
21:08
<tw2113>
now now, Eternal Sunshine = good
21:09
<TabAtkins>
http://en.wikipedia.org/wiki/Lemony_Snicket:_The_Unauthorized_Autobiography was a *really* confusing book to read when I hadn't yet heard of the SoUE series.
21:09
<TabAtkins>
(My aunt and uncle are friends of the author, so they gave me a free copy.)
21:15
jgraham
will have to agree to disagree with MikeSmith on this
21:16
<jgraham>
(not the Jim Carrey thing you understand, he really is an ass)
21:20
<MikeSmith>
well, there are certainly better books
21:20
<MikeSmith>
such as "How late it was, how late" by James Kelman
21:20
<MikeSmith>
which every young adult should read
21:21
<MikeSmith>
anyways, time for me to sleep
21:22
<karlcow>
おやすみなさい