08:05
<annevk>
Who else would be good to cc on https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 ?
08:05
<annevk>
Maybe maciej?
08:06
<annevk>
Who from Google?
08:11
<heycam>
arv?
08:11
<MikeSmith>
annevk: maybe post a message to webkit-dev, with a link to the bug? That way anybody could just Cc themselves.
08:55
<darobin>
manu-db: you there?
09:02
<Ms2ger>
Good morning, darobin :)
09:04
<darobin>
hi Ms2ger!
09:36
<MikeSmith>
darobin: if you pinging manu-db about those bugs with the public-rdfa-wg⊙wo address, please see my comments over on #html-wg :)
09:38
<darobin>
MikeSmith: yup saw them thanks!
09:57
<hsivonen>
this sums up the disconnect: https://twitter.com/svgeesus/status/294075320691204097
10:44
<MikeSmith>
hsivonen: https://twitter.com/svgeesus/status/294060529780137984 surprised me more
10:44
<MikeSmith>
"if SAX1 had it, ppl used and depended on it and SAX2 dropped it, that would be a great analogy."
10:45
<MikeSmith>
I would think the normal conclusion would be that people probably did not depend on it
10:45
<MikeSmith>
and everybody gets things done fine in SAX2 without it
10:46
<MikeSmith>
hsivonen: but anyway, LexicalHandler does actually expose it, right?
10:46
<MikeSmith>
I realize of course that ContentHandler doesn't
10:47
<hsivonen>
MikeSmith: not in LexicalHandler. Guess again. :-)
10:47
<hsivonen>
MikeSmith: it’s well buried
10:47
<hsivonen>
MikeSmith: not in core
10:47
<hsivonen>
not in extra set 1.0
10:47
<hsivonen>
it’s in extras 1.1 alpha
10:47
<MikeSmith>
ah OK
10:47
<hsivonen>
MikeSmith: do you want to guess again or shall I give the name of the interface?
10:48
<MikeSmith>
well given that, it's even more clear there's not wide need for it by people programming in SAX
10:48
<MikeSmith>
hsivonen: lemme make one more guess
10:50
<MikeSmith>
hsivonen: well I was going to "guess" by finding it in the docs but I just now did that and I still can't find it!
10:50
<hsivonen>
Designed by XML haters, clearly. :-)
10:51
<hsivonen>
The interface is Locator2. I bet you didn’t see that coming.
10:51
<MikeSmith>
eh?
10:51
<MikeSmith>
nuts
10:52
<hsivonen>
well, it’s not completely nuts to bundle the character encoding info with line and column info
10:52
<MikeSmith>
ah yeah that makes sense
10:52
<hsivonen>
but it shows how the designers of the API treated that stuff as that kind of IO artifact
10:52
<MikeSmith>
yeah
10:54
<MikeSmith>
hsivonen: about Chris's comments, funny thing is, I don't think Chris feels very strongly about polyglot. So I'm not sure why he cares whether the XML declaration is exposed in the DOM API
10:56
<MikeSmith>
and so far the polyglot case that Glazman brought up is the only case that I recall anybody in the discussion saying they actually needed it for
10:58
<MikeSmith>
I guess maybe what Chris was reacting to is that he thought the removals were motivated just by kneejerk XML hate
11:04
<JibberJim>
Anyone know off hand if the video element can go 0 volume distinct from MUTE (ie change volume to 0, call unmute, what happens?) It seems from reading that mute and volume are distinct, so you can have an "unmute" which does nothing if the volume is set to 0. And a volume setting to 1 which doesn't produce any sound because it's muted.
11:09
<MikeSmith>
JibberJim: what method do you call to "unmute"?
11:09
<MikeSmith>
oh
11:09
<MikeSmith>
nm
11:11
<MikeSmith>
JibberJim: after looking at the spec, your reading seems correct
11:12
<MikeSmith>
you want other behavior?
11:13
<MikeSmith>
like, if volume is 0 and you unmute, then something should happen to the volume?
11:13
<darobin>
that strikes me as entirely sane and correct behaviour
11:13
<MikeSmith>
yeah
11:17
<darobin>
but JibberJim isn't usually a huge fan of sane and correct
11:18
<Ms2ger>
And a good morning to you too
11:20
<karlcow>
well with unmuting and listening to the volume at 0. You can at least listen the noise of silence.
11:23
<Ms2ger>
I didn't need to see your name to know who said that :)
11:33
<matijsb>
there's a Terry Pratchett joke in there somewhere
11:34
<Ms2ger>
You're welcome to make it :)
11:35
<matijsb>
I'll leave it to the pros ;)
14:08
<manu-db>
darobin, MikeSmith: Hey - was in meetings all day yesterday - what's up?
14:20
<darobin>
manu-db: don't worry, I pinged you by mistake
14:21
<darobin>
MikeSmith: was pretending to be you in Bugzilla, which confused me
14:21
<manu-db>
darobin: Is this exchange going to result in no new work being piled on top of me?
14:23
<Ms2ger>
manu-db, if you want work...
14:23
<manu-db>
noooo!
14:23
<manu-db>
no
14:24
<Ms2ger>
Yes you do! ;)
14:24
<manu-db>
no more, I can't take it.
14:24
manu-db
hides under darobin.
14:24
Ms2ger
gives work to darobin instead
14:25
<manu-db>
good man. :) - he loves extra work.
14:30
<darobin>
you can try giving work to me, but what with my brain being smothered in snot it's not going to do you any good :)
14:31
<manu-db>
it just slides off... that's a good defense, never thought about it that way.
14:31
<manu-db>
darobin: on a more serious note - is there anything I need to do as a result of whatever happened yesterday?
14:31
<Ms2ger>
I'm snot, you're glue?
14:32
<darobin>
manu-db: no, but thanks for offering ;)
14:32
<darobin>
Ms2ger: huwah?
14:39
<Workshiva>
I haven't been keeping up with the filesystem APIs, is there a way to offer the user to save a data: URI with a recommended filename?
14:52
<darobin>
Workshiva: <a href='data:...' download='xxx.foo'>,...
14:54
<Workshiva>
That seems almost too easy to be true
14:57
<Workshiva>
Also, thanks
15:01
<darobin>
Workshiva: well, it's not implemented all that broadly
15:03
<Workshiva>
Luckily I only need it for a chrome extension
16:45
<Velmont>
Hmmm. darobin, what do you think about the name? If everything is supposed to be in html-testsuite, it's not exactly a very ... obvious name, is it?
16:56
<darobin>
mmm, Velmont is Odin in disguise!
16:56
<darobin>
Velmont: I don't think that the name is a huge problem to be honest
16:57
<darobin>
99% of people think that all of what we do is "HTML5"
16:57
<Velmont>
Okay. :]
16:57
<Ms2ger>
Those people aren't the ones I want to write tests :)
16:57
<Velmont>
We want the 1%!!
16:57
<darobin>
lol
16:57
<darobin>
Ms2ger: that's actually not true, a lot of the good test writers really don't give a shit about the whole naming thing
16:58
<darobin>
and we want them on board
16:58
<Ms2ger>
The ones that can tell a spec from a hole in the ground ;)
16:58
<darobin>
(and I don't think they should give a shit — I for one don't :)
16:58
<Velmont>
At TestTWF there was a HTML5 "part". Everyone had to put up their hand on what they wanted to work on. Almost noone did put up their hand for HTML5, because they were waiting for "IndexedDB" and similar specs that they cared about. :]
16:58
<darobin>
if you think that a spec is different from a deep, dark, and neverending hole in the ground you clearly don't know what a spec is
16:59
<marcosc>
heh
16:59
<darobin>
Velmont: true, but frankly I don't think the name is an issue
16:59
<darobin>
naming would be an important concern if we went with multiple repos
16:59
<darobin>
because we'd need to make it easy for people to find the right repo
17:00
<darobin>
but if there's only one, everything points there
17:00
<darobin>
we could call it unicorn for all it matters IMHO
17:00
<darobin>
who am I kidding that my opinions are ever humble? I meant IMO
17:00
<Velmont>
I'm a bit at loss about what to write on that wiki page for Art though... I can copy what's in the readme at github, maybe. ( https://github.com/w3c/html-testsuite/blob/master/README.md )
17:01
<darobin>
Velmont: write whatever you think someone who doesn't know us but is clueful would need to get started
17:01
<darobin>
if that means cut and paste, then all the easier for you
17:01
<darobin>
once you've put a first draft up I'll look at it to help
17:06
<Ms2ger>
darobin, pff, let's just put it on github.com/whatwg/tests :)
17:06
<darobin>
haha
17:08
<Velmont>
darobin: The real reason I asked was that I was maybe expecting some resistance on the naming not being generic.
17:09
<darobin>
Velmont: yeah I thought of that too
17:09
<Velmont>
The Webapps WG uses the W3C's ''html-testsuite'' repository on GitHub for its tests.
17:09
<darobin>
if it really is a problem we'll look into changing it
17:09
<darobin>
but I don't think it's a real issue
17:10
<Velmont>
Yeah, don't really have to preemptively do that ;]
17:10
<darobin>
right, I prefer to cross that bridge if it shows up
17:10
<darobin>
no point in solving an issue if no one ends up having it :)
17:10
Ms2ger
throws a bridge at darobin's feet
17:10
Ms2ger
puts a nice stack of tests on top
17:11
darobin
mumbles something about the velocity of an unladen swallow
17:11
<darobin>
Ms2ger: you *really* don't want me reviewing anything today
17:11
<darobin>
I'll get to it as soon as I can look at something more complex than email without my eyes crossing
17:11
<Ms2ger>
I don't want you to review, I want you to approve :)
17:11
<darobin>
lol
17:12
<darobin>
if it really is only about approving, you can approve it yourself you know :)
17:12
<Ms2ger>
Well, technically, yes :)
17:12
<Ms2ger>
But that makes it seem the review process is a failure
17:13
<Ms2ger>
We wouldn't want that, would we? ;)
17:14
<gsnedders>
In reality, nobody reviews anything anyway.
17:58
<Velmont>
Meh darobin disappeared. But anyway -> http://www.w3.org/wiki/Webapps/Submitting_tests
18:21
<tantek>
Velmont - I took a look - looks good. And thanks for using the W3C wiki rather than a WG silo wiki :)
18:23
<Velmont>
tantek: Yeah, I just notified webapps list about it now. Time to do something else :]
18:24
<tantek>
Velmont, cool. Also, your update reminded me the Webapps page itself needed some updating, e.g. dates of the next meeting: http://www.w3.org/wiki/Webapps
18:25
<Velmont>
tantek: Haha, yeah, I didn't even read them :S Should've noticed that.
18:25
<tantek>
It's ok, now we just have to convince whoever maintains the meeting agendas to use the W3C wiki :)
19:28
<matjas>
“If there wasn’t a benefit to coding XHTML then why would it be formally codified into the (x)HTML5 standard then?” — http://mathiasbynens.be/notes/html5-levels#comment-13
19:29
<Hixie>
and y'all complained when i had the spec discouraging xml
19:29
<Hixie>
and look where we are now :-P
19:30
<matjas>
(i didn’t complain :P)
19:31
<matjas>
relevant commit from the other day http://html5.org/tools/web-apps-tracker?from=7645&to=7646
19:33
<Hixie>
btw html4 didn't "not require" the slash; the slash just meant something very different in html4
19:33
<Hixie>
basically almost none of the browsers implemented it, but the validator did
19:35
<matjas>
Hixie: heads up, http://ln.hixie.ch/+ 404s
19:35
<matjas>
Hixie: what did it mean in HTML4? is this about SGML?
19:35
<Ms2ger>
Yep
19:35
<Ms2ger>
<s/foo/
19:36
<matjas>
ah, and <title// etc., I see
19:36
<matjas>
http://mathiasbynens.be/notes/minimal-html all over again
19:41
<Hixie>
hm, oops
19:41
Hixie
fixes his redirects
19:41
<Hixie>
404 fixed
19:42
<Hixie>
yeah, the / in html4 was sgml magic syntax
19:42
<Hixie>
meant various things, but none of it is what html now says it means
19:55
<jgraham>
Velmont: FWIW I think the repo name should be web-platform-testsuite
19:56
<jgraham>
Or failing that no-rdf-allowed-testsuite
19:56
<Ms2ger>
How about rdfa?
19:56
<jgraham>
The second choice name should answer that ;)
19:57
<jgraham>
But seriously, I don't care if RDFa people put tests there
19:57
<jgraham>
I can ignore them without difficulty
20:19
<JibberJim>
MikeSmith / darobin (who's not here...) sorry I got dragged away after my question :( But yes, I don't like the idea of calling UNMUTE and it not resulting in sound coming out - however, that's as a user, and it doesn't necessarily mean the spec is wrong as you can handle the behaviour yourself in your UI layer.
20:20
<JibberJim>
I noted that Chrome's UI handles it by showing the Mute/Unmute button as muted and unresponsive when you click on it if you make the volume 0, and that seems very wrong to me. It means the user has a button which sometimes work.
20:23
<TabAtkins>
JibberJim: Existing televisions seem relatively split on the subject, in my experience. Some treat mute-ness as an independent state from volumn, others act fancy and will push you up to a "reasonable" volumn if you lower the volume to 0 and then press unmute.
20:23
<TabAtkins>
Man, *why* am I typoing it as volumn so much? That third instance, which is spelled correctly, took me two tries to get it right.
20:24
<TabAtkins>
Anyway, the independent-state thing seems nice and simple to understand. Trying to decide on a reasonable volume seems hard.
20:24
<TabAtkins>
(Argh, again with the attempted volumn spelling!)
20:24
<Velmont>
jgraham: "tests"
20:25
<JibberJim>
It actually came up because the test page only lets you take the volume down to 0.01 or something like that...
20:26
<JibberJim>
Yes I agree, the "what is a reasonable volume" is hard - although perhaps less hard on a TV which often these days has a "volume when you turn it on" setting in their menu.
20:47
<jgraham>
Velmont: The name?
20:47
<jgraham>
I specifically don't want EmotionML tests, or RIF tests or anything that you wouldn't implement in a browser
20:48
<jgraham>
"web platform" is the name for things that we implement in web browsers
20:48
<jgraham>
So web-platform-tests[uite]
20:49
<jgraham>
(I think html-testsuite is bad because it's misleading; we want to make it easy for people to find the right things)
20:58
<annevk>
MikeSmith: emailed webkit-dev
20:58
<Hixie>
annevk: did you get a chance to review https://www.w3.org/Bugs/Public/show_bug.cgi?id=17839 ?
20:59
<annevk>
Hixie: to some extent, need to figure out still why you can't use decode
20:59
<Hixie>
it does DOM manipulation
20:59
<Hixie>
er
20:59
<Hixie>
BOM
20:59
<Hixie>
typo
20:59
<annevk>
Hixie: which is what we want, unless the requirements changed somehow
21:00
<Hixie>
yeah but i already do that
21:00
<annevk>
I'll have a look tomorrow, but basically assume I'm on a 16-day vacation or some such
21:01
<annevk>
Hixie: the idea was to centralize the BOM checking
21:02
<Hixie>
i don't see much value in changing how we do bom checking
21:03
<annevk>
if it's a change something went wrong
21:04
<annevk>
the value of CSS / HTML / XML / JavaScript / ... using decode (and new formats using utf-8 decode) is that there's more shared code
21:05
<Hixie>
as far as i can tell it's just pointless editorial tweaking :-)
21:05
<Hixie>
if it ain't broke, i don't want to fix it
21:06
<annevk>
I'll keep that mind when doing a more thorough review
21:36
<JibberJim>
Another VIDEO element question, which I can't find in the spec. Is the loadStarted event required? Or is it possible to call .play() and it go immediately to canPlayThrough ? because it's got a source and it can play etc. ?
21:40
<JibberJim>
I think the event is required from reading.