00:00
<gsnedders>
(I know the harness is a horrible hack, but it was done as such to get it working somewhat in all browsers, inc. Firefox just after the HTML5 Parser merge which had some odd, fun bug)
00:01
<roc>
it's great
00:03
<gsnedders>
roc: Try running a single test case in it :)
00:04
gsnedders
can't remember half his gripes with it, but he has plenty
01:42
<nessy>
foolip: does Opera fire the progress event on video elements?
04:07
<foolip>
nessy: yes, as per spec about the timing
04:07
<foolip>
last I checked anyway :)
04:08
<nessy>
yeah - about to write you a bug report :)
04:08
<nessy>
I think onprogress works, but not addEventListener
04:08
<nessy>
but then, it's really hard to test because after every test I have to change the file name, because Opera has buffered it and a shift-reload doesn't reload the video resource
04:09
<nessy>
I have the same problem with Chrome, incidentally
04:09
<nessy>
that's at least one bug ;)
04:10
<nessy>
actually - ditch that - it's only the reloading that doesn't work
04:10
<nessy>
progress events work
04:13
<foolip>
nessy: use a HTTP server and set the source to URL+'?'+something random
04:14
<nessy>
good idea
04:14
<foolip>
is it Math.random() perhaps?
04:14
<nessy>
still, it would be nice if shift-reload on the page ditched the buffered media resource
04:14
<foolip>
anyway, that's what zcorpan does
04:14
<nessy>
Firefox does that
04:14
<foolip>
Opera doesn't have a special reload I think
04:14
<foolip>
at least I never found one
04:15
<nessy>
well, I can reload the resource with shift-click on the reload button
04:15
<nessy>
also, I can remove all other elements from cache in "Tools"->"Delete private data…"
04:15
<nessy>
except for media resources
04:20
<foolip>
oh, that *is* a bug
04:20
<foolip>
can you file one at http://bugs.opera.com ?
04:21
<nessy>
ok
04:22
<nessy>
and webkit is next …. :(
04:24
<nessy>
gah, seems impossible for me to get an account there :(
04:24
<nessy>
will try the wizard ...
04:27
<jwm>
hehe
04:28
<jwm>
amazing how many opera people are in whatwg
04:32
<nessy>
jwm: I am using all browsers :)
04:39
<MikeSmithX>
jwm: it's not amazing if you consider how much market capital Opera has
04:40
<foolip>
we like standards, etc etc :)
04:45
<jwm>
MikeSmith: less than all other browsers?
04:45
<jwm>
hehe
04:54
<MikeSmith>
jwm: inversely proportional
04:54
<MikeSmith>
little-known axiom
05:17
<MikeSmith>
what are some synonyms for the word "encode"?
05:17
<MikeSmith>
in the general sense
05:19
<MikeSmith>
ok, encrypt is close I guess
08:02
<zcorpan_>
foolip: when are you moving?
08:02
<hsivonen>
how up-to-date is html5lib these days?
08:26
<jgraham>
hsivonen: According to the existing testcases it's not that bad
08:26
<jgraham>
A couple of patches haven't been pushed to google code
08:31
<hsivonen>
jgraham: OK. I'm going to advertise it to the SVG WG then
08:32
<hsivonen>
jgraham: it has SVG support, right?
08:32
<jgraham>
hsivonen: Right
08:33
<jgraham>
From memory the missing things is the recent change to <button> or something
08:33
<jgraham>
s/things/thing/
08:34
<hsivonen>
ok
08:35
<annevk>
the SVG minutes didn't consider html5lib to be a real implementation
08:36
<annevk>
if you're talking about that
08:49
jgraham
wonders what was being discussed
08:50
<annevk>
read it and weep: http://www.w3.org/2010/05/31-svg-minutes.html
08:53
<jgraham>
Sigh
08:54
<jgraham>
No one noticed that webkit are implementing then?
09:02
<annevk>
dunno, roc pointed that out on the list this morning
09:03
<annevk>
btw, I don't think anything will actually happen
09:06
hsivonen
just followed up to roc's email
09:08
<hsivonen>
the "spec X is not done" mentality *within* the W3C is so bizarre
09:26
<foolip>
zcorpan_: as soon as I'm back in sweden, tillträde is July 5 I think
09:31
<zcorpan_>
foolip: ok. fun :)
09:32
<zcorpan_>
foolip: if i go back to video work, i still have a reason to go to göteborg then :P
09:33
<jgraham>
foolip: You are moving? That's sad :(
09:33
<jgraham>
Well I mean it is hopefully nice for you
09:34
<foolip>
I'm quite thrilled
09:35
<foolip>
zcorpan_: you're always welcome to work on video
09:35
<jgraham>
To be leaving Linköping?
09:37
<foolip>
jgraham: Honestly, yes. Outside of work there's nothing I enjoy about Linköping.
09:38
<jgraham>
Well yeah I would hardly recommend it as a holiday destination
09:40
<foolip>
Most importantly, I think my wife will like Göteborg better.
09:40
<foolip>
More people. People are rare in Sweden...
09:41
<jgraham>
Not stockholm then?
09:42
<foolip>
No, Stockholm is the capital and thus clearly sucks, as I am not from the capital.
09:42
<foolip>
That's the theory anyway :)
09:42
<foolip>
Also, they talk funny.
09:43
<jgraham>
That makes no sense
09:43
<annevk>
foolip, that goes for all of Sweden, I have to say
09:43
<foolip>
Haha
09:43
<zcorpan_>
they talk funny in göteborg too
09:43
<hsivonen>
Is there an Opera office in Stockholm?
09:43
<jgraham>
But sure Göteborg is nice
09:43
<jgraham>
hsivonen: A tiny one. Two engineers and some sales guys
09:43
<zcorpan_>
hsivonen: yes
09:44
<hsivonen>
ok
09:44
<zcorpan_>
there's an office in örebro also
09:44
<zcorpan_>
a tinier one
09:44
<jgraham>
zcorpan_: You don't count as "an office"
09:44
<zcorpan_>
jgraham: :(
09:44
<jgraham>
One person is "working from home" You need two people to make an office
09:45
<jgraham>
Unless you are actually not working from home I guess
09:46
<annevk>
if Rijk is actually in wijk bij duurstede maybe we should petition for a Dutch office here in Utrecht
10:02
<hsivonen>
I wonder what version number I should give to the next release of the V.nu parser...
10:02
<hsivonen>
It should be 1.3 at minimum and I don't want to go all the way to 2.0 yet
10:03
<hsivonen>
possible choices: 1.3, 1.5 and 1.9
10:07
<annevk>
just do 1.3 then
10:07
<annevk>
you're not in competition (yet) so there's no reason to inflate your numbers
10:11
<hsivonen>
annevk: ok. makes sense
10:11
<hsivonen>
I'm thinking of going to 2.0 when I add a sanitizer
10:16
<jgraham>
Make it converge on the golden ratio
10:17
<annevk>
http://www.youtube.com/watch?v=zaT7thTxyq8 is really funny
10:18
<annevk>
for sure our marketing department has their highlights
10:18
<hsivonen>
New thing I learned today: Nautilus caches the file listings on samba mounts for days and doesn't show new files without clicking the reload button
10:18
<hsivonen>
FAIL
10:24
<annevk>
what happened to publishing new drafts?
10:24
<annevk>
did someone object in private or so or are all the chairs on holiday break?
10:31
<annevk>
http://lists.w3.org/Archives/Member/w3c-ac-forum/2010AprJun/0101.html (W3C Member-only) (doesn't provide an answer to the above question but is interesting)
10:35
<Dashiva>
annevk, you tease
10:40
<MikeSmith>
"Potato slow. Opera fast." is great
10:40
<MikeSmith>
who are the dudes in the video, I wonder?
10:40
<zcorpan_>
Odd & Even
10:41
<MikeSmith>
annevk: nobody privately objected to publishing new drafts, btw
10:41
<MikeSmith>
zcorpan_: hey!
10:41
<MikeSmith>
I wanted to bug you about something
10:41
<MikeSmith>
IRI checking
10:41
<zcorpan_>
MikeSmith: i know
10:41
<MikeSmith>
ah, OK
10:42
<zcorpan_>
MikeSmith: the messages look nice, but i don't have time right now to write tests
10:43
zcorpan_
is eating websocket cookies
10:43
<MikeSmith>
ok, no oproblem
10:43
<MikeSmith>
*problem (no o)
10:43
<MikeSmith>
zcorpan_: yeah, I figured you were still in Websocket Wonderland for a while
10:43
annevk
is sort of curious what Hixie is up to
10:44
jgraham
is sort of curious what the chairs are up to
10:45
hsivonen
wonders if the chairs noticed that Gecko, WebKit and Dreamweaver made progress on implementing elements proposed for removal since the start of the survey
10:46
<annevk>
at least one of them should have noticed stuff landing in WebKit :)
10:46
<hsivonen>
not to suggest that that's in any way relevant to Decisions, of course. ;-)
10:47
<annevk>
depending on the outcome of the decision, we may have came up with a few more <embed>-like elements
10:48
<annevk>
with as difference that these have a proper specification
10:48
<hsivonen>
annevk: do you mean elements supported by browsers and Adobe's authoring tools but not the spec?
10:49
<zcorpan_>
damned browsers making up their own tags
10:49
<annevk>
hsivonen, yeah
10:49
<annevk>
with "the spec" being the "the spec the W3C publishes"
10:49
<jgraham>
If these decisions don't keep the elements then the HTMLWG deserves to become a laughing stock
10:52
<Dashiva>
You can't really blame the WG for chair decisions, can you? Well, and the people who create the issues.
10:55
<Philip`>
You can blame the WG for putting up with it
10:55
<jgraham>
We could have a revolution
10:55
<Philip`>
The W3C and the chairs only have authority because people choose to give it to them
10:56
<jgraham>
With pitchforks and torches and things
10:56
<annevk>
Revolution is XHTML2
10:56
<jgraham>
Although those typically end with the revolutionary leader dyning in an unpleasant way, so if anyone asks it was Philip`'s idea
10:56
<annevk>
Though from a W3C perspective maybe HTML5 is indeed revolution... Strange world.
10:56
<jgraham>
*dying
10:56
<Dashiva>
annevk: That depends on what you revolt _against_
10:57
<Dashiva>
You could say XHTML2 was a revolution against HTML, and HTML5 is a revolution against XHTML2
10:57
<annevk>
What if you just wanna evolve?
10:58
<Philip`>
The WG members could form a new working group that's entirely independent of the W3C with its own non-consensus model for making decisions and that develops its own specification called HTML5
10:58
<Dashiva>
That's a question of authority, I suppose
10:58
<Philip`>
and so it's their fault if they choose to work within the existing system instead
10:58
<Dashiva>
From the W3C viewpoint, I'm sure XHTML2 _was_ evolution
10:59
<annevk>
From miles high it may indeed seem that way
11:00
<aho>
i liked xhtml2's "hx"
11:00
<aho>
using h1 (etc) in conjunction with nested sections is sorta weird
11:00
<annevk>
AlexD keeps it up: "HTML5 is vapourware _until_ the spec. reaches recommendation status."
11:01
<jgraham>
aho: Yeah but it is kinda broken because you can still use <h> and <h1> in the same document
11:01
<annevk>
vapourware: "New software that has been announced or marketed but has not been produced."
11:01
<jgraham>
This is like the opposite of vapourware
11:01
<jgraham>
We haven't announce it is done but it is still beiong produced
11:01
<aho>
jgraham, still... i'd like to point out that this is a section-nesting heading and not a regular one
11:01
<Dashiva>
solidware?
11:02
<jgraham>
aho: They are all just headings
11:02
<aho>
using a weight-free heading would do the trick
11:02
<annevk>
Guess I should stop... http://xkcd.com/386/
11:02
<aho>
jgraham, yea... they are all just tags (?) :>
11:04
<aho>
i just liked that there was some heading which indicated that its intended weight depends on the section nesting
11:04
<Dashiva>
aho: Isn't that obvious, though? Since h1 would only be at the very top of the document normally
11:04
<aho>
and tables are normally only used for tabular data? :D
11:06
<annevk>
aho, by that argument we should have <table2> which will be only used correctly, which of course is nonsense
11:06
<jgraham>
Dashiva: I think something like LiquidCrystalWare would be better since it appears all over the place but the theory is still not complete
11:06
<aho>
bad analogy :>
11:07
<jgraham>
(of course the theory of any state of matter is not complete but...)
11:07
<annevk>
aho, works for me :)
11:09
<Hixie>
you know, if the svgwg thinks html5 is vapourware, maybe we should just use the same process as svg 1.2 did
11:10
<Hixie>
and just stamp html5 as a REC and ignore 10% of the feedback we've gotten, just like they did
11:10
<Hixie>
http://ln.hixie.ch/?start=1155235213&count=1
11:10
<Dashiva>
Hixie: The rules don't apply to XML languages, you should know that by now
11:11
<Hixie>
html5 has an xml serialisation!
11:11
<Dashiva>
A fig leaf, nothing more
11:11
<aho>
annevk, "Sections may contain headings of any rank, but authors are strongly encouraged to either use only h1 elements, or to use elements of the appropriate rank for the section's nesting level."
11:12
<aho>
if there were an element for headings without any weight, it would be clear which route you picked
11:12
<Dashiva>
It would be clear, but for what purpose?
11:13
<aho>
say there is a doc... and 5 years later some different person writes a new stylesheet
11:14
<Dashiva>
No problem at all
11:15
<aho>
there is also no problem with using single letter variables exclusively
11:15
<aho>
it just takes a bit longer to understand than necessary
11:15
<Dashiva>
There's a rather significant backwards compatibility problem, for no actual benefit
11:15
<annevk>
aho, just use <h1>
11:16
<annevk>
<h2-6> is only if you care about backwards compatibility
11:16
<aho>
if you use canvas and all those new apis... why would you care about such a small detail?
11:16
<annevk>
indeed
11:16
<annevk>
why do you?
11:17
<aho>
breaking backward copatibility of weight-free headings, that is
11:17
<Dashiva>
Because not every page uses canvas?
11:18
<aho>
article, aside, section, nav... they "break" backwards compatibility the same way
11:18
<aho>
not really much harm done there
11:18
<Dashiva>
Those are different. They _add_ semantics to what is considered meaningless by older browsers
11:18
<aho>
well, i did like h/hx. that's all :P
11:19
<aho>
being able to differenciate between weighted headings and weight-free/section-nesting headings doesn't add anything?
11:20
<annevk>
nope
11:20
<aho>
wouldn't that make the structure clearer?
11:20
<Dashiva>
You're the one claiming it does, shouldn't you answer?
11:20
<Dashiva>
<Dashiva> aho: Isn't that obvious, though? Since h1 would only be at the very top of the document normally
11:24
<Dashiva>
Hixie: Last link in that blog post is dead, by the way
11:25
<aho>
well, imo h/hx:h1-h6 is sorta like span:em/b/strong/i
11:25
<aho>
i really liked that
11:25
<aho>
but it's not like this will be added to any spec any time soon
11:25
<Hixie>
Dashiva: that's even better
11:25
<Hixie>
Dashiva: so much for stable links at the w3c!
11:25
<aho>
so, i don't really see why you think it's necessary to discuss this in depth
11:25
<Dashiva>
Maybe it wasn't cool enough to not change
11:28
<Dashiva>
aho: Span has no semantics, the proposed hx does.
11:28
<aho>
yes
11:28
<aho>
h/hx on its own doesn't have specific weight
11:28
<aho>
sorta like a td on its own doesn't have much use :>
11:32
<Dashiva>
I guess you're just an aho, after all...
11:32
<aho>
*clap* *clap*
11:34
<annevk>
Dashiva, Hixie, I guess it is http://www.w3.org/TR/2006/CR-SVGMobile12-20060810/lc3-replies-public.html
11:38
<aho>
Dashiva, if you see some hx somewhere, you know it's a heading which relies on section-wrapping. if you see h1, it's either the old kind of heading *or* one which relies on section-wrapping. the hx element doesn't have this kind of ambiguity - and that's something i generally like
11:39
<aho>
e.g. i like code conventions, because they help getting rid of that stuff
11:39
<aho>
saves time
11:40
<jgraham>
aho: I have no idea how you envison that working
11:41
<jgraham>
What happens with <body><hx><section><hx><section<h1>
11:41
<jgraham>
(ignore the typo)
11:41
<jgraham>
Is the <h1> a top level heading or a third level heading
11:43
<jgraham>
(exactly this use case happens any time a mashup embeds content that uses <h1> in a container that uses <section>)
11:45
<aho>
what happens in a mashup that embeds content that uses <h2-6> in a container that uses section? ;>
11:47
<annevk>
it would just work
11:47
<aho>
so, that section h4 thing you just embedded will look like what exactly?
11:48
<jgraham>
aho: The logical outline is well defined
11:49
<jgraham>
aho: The style will (by default) just depend on the tag name, but that is a CSS limitation taht would be worse if we also had <hx>
11:49
<jgraham>
Hopefully we will get ::section(n) and so on
11:49
<aho>
-moz-any() is nice for this stuff .)
11:50
<aho>
e.g. section any(h1,h2,h3,h4,h5,h6,hx) { first level heading}
11:51
<aho>
if it all were hx you wouldn't have to do that though
11:51
<jgraham>
Right, but make the section a pseudo class that matches all level one sections
11:51
<jgraham>
aho: It can't all be <hx>
11:52
<aho>
why not? (if we ignore mashups)
11:52
<jgraham>
We don't ignore mashups
11:52
<jgraham>
If we make invalid assumptions we can prove anything
11:52
<aho>
i never used any mashup, i never made one, i never will make one
11:52
<aho>
i don't even know one popular mashup
11:53
<Dashiva>
If you aren't making mashups, it's pretty much a non-issue
11:53
<jgraham>
You never used an online feed reader, for example?
11:53
<Dashiva>
Mashups are the important case, not something to ignore
11:55
<aho>
aggregators typically process the feeds quite a bit, but they generally don't really work all that well
11:58
<jgraham>
"process the feeds quite a bit" typically means "do some sanitization". Having to rewrite the heading tags to fit in with the output template is rather different
11:59
<aho>
well, currently you just have random headings there
11:59
<aho>
i don't really see how that's super awesome
11:59
<aho>
<:
12:09
<aho>
in retrospect i think it would have been better if i hadn't mentioned xhtml2's hx. i hadn't expected this kind of annoying discussion... giving that it's a dead spec n all... oh well :>
12:09
<aho>
it's nice that html5 picked up section tho (there! i said it) :>
13:11
hsivonen
notes "WebM will be supported by all three major browsers: Google Chrome, Mozilla Firefox and Opera" on OMG! UBUNTU!
13:11
<Peter`>
I'm still wondering what Apple will do with WebM
13:12
<Peter`>
no word on that I'm assuming?
13:12
<Peter`>
(Next to Steve Jobs saying he doesn't like it)
13:17
<Dashiva>
Of course he doesn't like it, it wasn't invited by him :)
13:53
<Lachy>
Peter`, Apple won't support WebM while there is still a percieved risk of patent trolls
13:54
<Peter`>
Clearity on the legal patent subjects might take months, if not years
13:54
<Lachy>
they will at least be waiting to see what comes out of the FUD from the MPEG LA, if anything at all. But, they'll likely just maintain the threat for ages, like they have with Theora.
13:55
<Lachy>
right, so I wouldn't recommend holding your breath for Apple to support it.
13:55
<hsivonen>
Lachy: citation needed
13:55
<Peter`>
I'm quite curious about the future and implementation of WebM, specifically now Microsoft is more or less supporting it as well
13:56
<Lachy>
but I believe there will at least be 3rd party quick time components made available one day, which will enable support in Safari.
13:57
<daedb>
Apple doesn't even support Vorbis yet, so any official support for VP8 seems incredibly unlikely.
13:57
<Peter`>
But following Theora and the lack of a formal stance of the company on WebM, different from Steve Jobs' own thoughts, it's still somewhat undefined right now. As hsivonen already said, while it's unlikely, nothing is clear
13:57
<hsivonen>
It's so frustrating that XiphQT still doesn't have Thusnelda. it would be nice to have WebM support rolled into XiphQT
13:58
<hsivonen>
Peter`: what have I said?
13:58
<Peter`>
"citation needed"
13:58
<Lachy>
hsivonen, http://www.theregister.co.uk/2010/05/20/jobs_on_vp8/
13:59
<Lachy>
http://www.theregister.co.uk/2010/05/21/mpegla_mulls_patent_license_for_webm/
13:59
<hsivonen>
Peter`: I meant I wanted to see Lachy's source
13:59
<hsivonen>
Lachy: thanks
14:00
<hsivonen>
Lachy: I think the Register is extrapolating quite a bit from Steve dropping one URL without commentary
14:01
<Lachy>
yes, that's true. But it's not too much of a stretch given what Jobs previously said about forming a patent pool around open video codecs
14:02
<Lachy>
There was another article I read that was a set of email exchanges between a reporter, Larry Horn from the MPEG LA and, I believe, someone from Xiph, which talked about the FUD that the MPEG LA have maintained for years over theora
14:02
<Peter`>
hsivonen: alright, sorry :)
14:04
<hsivonen>
Lachy: well, yeah, anyone can be "looking into" whatever
14:05
<hsivonen>
(As I understand it, the FUD Monty was referring to wasn't MPEG-LA FUD per se but FUD from the MPEG camp. IIRC, MP3 licenses haven't been managed by MPEG-LA.)
14:06
<Peter`>
I'm assuming Google knows what they're doing though, also considering the list of companies who already committed to VP8, there has to be a certain degree of certainty. A chance of submarine patents arising always remains, with any product that's entering an already-existing market
14:08
<hsivonen>
when creating a Ubuntu USB installation stick with a large (over 1 GB) persistence file, is the creation of the persistence file supposed to be insanely slow?
14:08
<hsivonen>
I'm wondering if I have bought a bad USB stick
14:09
<hsivonen>
also, it seem the progress meter was programmed by the person who came up with the Windows file copy progress meter
14:14
<Lachy>
Peter`, IANAL, but I think the number of other companies supporting WebM, many of whom I assume hold numerous patents of their own, give some level of protection because they may hold patents that they can use defensively against others who aggressively attack VP8
14:17
<zcorpan_>
http://twitter.com/microft/statuses/15176790401
14:26
<Peter`>
Lachy: That's a good point, specifically given that the license states that you cannot file patent claims against Google if you're using the specification. Widely interpreted, one could say that they're using open-source to minimize the chance of patent claims
14:26
<Peter`>
Then again, IANAL either
14:30
<MikeSmith>
can anybody remind me what happened the the "Copy and paste" section of the HTML5 spec?
14:31
<MikeSmith>
it seems to be commented out in the source now
14:34
<hsivonen>
MikeSmith: it used to define copy and paste in terms of drag and drop
14:34
<MikeSmith>
ok
14:34
<hsivonen>
MikeSmith: then it was pointed out to Hixie that some browser(s?) exposed copy and paste in a distinct way already
14:35
<MikeSmith>
ah
14:35
<MikeSmith>
I wonder if there is open bug on it
14:36
<hsivonen>
What kind of write speed (MB/s) should one expect from a USB stick?
14:36
<gsnedders>
hsivonen: Varies massively
14:38
<hsivonen>
OK, I bought USB sticks that suck
14:38
<hsivonen>
sigh
14:40
<hsivonen>
lesson learned: shop at a computer store. don't rely on office supply stores
14:41
<hsivonen>
aaargh. now after spending over 2 hours creating the persistence file, it's just starting to create a file system inside the persistence file
14:42
<MikeSmith>
hsivonen: found http://www.w3.org/Bugs/Public/show_bug.cgi?id=8800
16:24
<Peter`>
MikeSmith (?)/W3C: The link in the latest Twitter message gives a 404 error http://twitter.com/w3c/status/15185050915
16:41
<boblet>
anyone into diff and on a Mac should check out www.kaleidoscopeapp.com
16:42
boblet
is sad that he prolly fits this category
17:18
jwalden
is surprised he can't find an Opera bug-reporting menu item or UI in Opera itself (not for site bugs, but for Opera bugs)
17:19
<Philip`>
jwalden: Help -> Support -> Report a bug?
17:19
<jwalden>
Philip`: more indirect than I'd expected
17:19
jwalden
should note this is a beta version
17:20
<jwalden>
I guess Firefox doesn't have a similar item, so I guess it's not too odd
17:22
jwalden
finally got annoyed enough to report http://krijnhoetmer.nl/irc-logs/whatwg/20100405#l-486 now that it's breaking his site's intended rendering
17:23
<jwalden>
although, big blue background is probably a better rendering than the non-scaled background you get in a browser that doesn't support background-size, if your screen resolution/browser window are large enough
17:23
<jwalden>
or at least less failtastic
19:35
<variable>
.
19:35
<TabAtkins>
.?
19:37
<jgraham>
.*
19:38
<TabAtkins>
.{0,5}
19:38
<TabAtkins>
Hello
19:38
<jgraham>
True
20:18
<TabAtkins>
Today's surprising spellcheck list omission: "combinations".
20:18
<variable>
TabAtkins: which speller checker?
20:19
<TabAtkins>
Firefox on ubuntu.
20:21
<nielsle>
Are webgl and notifications likely to become official html?
20:21
<TabAtkins>
I know that Chrome either has them or is implementing them. Can't speak for other browsers.
20:23
<gsnedders>
WebGL will remain a separate spec, and so will notifications
20:23
<gsnedders>
It makes little sense to make them part of the HTML spec, IMO
20:23
<gsnedders>
But I guess it's a question of what you mean by "official HTML"
20:25
<nielsle>
I meant html as defined by w3c, but I think that I got my answer.
21:00
<jgraham>
nielsle: WebGL is not being done at W3C. Noifications I'm not so sure about but only Google seem really interested at the moment
21:01
<jgraham>
(WebGL is nevertheless becoming a standard; other standards organisations are avaliable, as they would say on the BBC)
21:05
<nielsle>
Thank you for the answers. (I am not an expert on all this, but I am not fully convinced that non-standard html is good thing.)
21:08
gsnedders
gets caught out by the fact that null does not equal anything in SQL
21:09
<TabAtkins>
NULL IS NULL
21:09
<ment>
badam bam tssss...
21:10
<gsnedders>
TabAtkins: Yeah, found that now
21:10
<Dashiva>
Just like NaN isNaN()
21:12
<gsnedders>
How do GROUP BY and joins interact?
21:12
<TabAtkins>
GROUP BY applies to the joined table.
21:12
<TabAtkins>
(Unless you've grouped in a subquery, of course.)
21:13
<gsnedders>
Okay, so it is logical
21:37
<AryehGregor>
Does Steve Jobs actually respond to a large fraction of the random mail he receives from the public?
21:38
<AryehGregor>
Maybe it's just a press corps, but everyone seems to assume that the responses are actually from him.
21:40
<Philip`>
AryehGregor: If Santa can reply to all the messages I send him, I'm sure Steve Jobs can
21:40
<TabAtkins>
You think Santa doesn't have an elven press corps?
21:41
<Philip`>
Of course not
21:41
<Philip`>
Elves don't even exist
21:41
<TabAtkins>
Oh ye of little Christmas faith...
21:41
<Philip`>
It's just him and Rudolph
21:42
<TabAtkins>
I have a folk song that clearly contradicts your assertion.