08:20
<Ms2ger>
Yay for Google fucking over Google: http://code.google.com/p/chromium/issues/detail?id=43394#c44
08:55
<MikeSmith>
Ms2ger: wonderful
08:55
<MikeSmith>
"Gmail and other Google Apps are relying on the fact that Chrome defines DOM attributes on DOM instances."
08:56
<MikeSmith>
"It's strange that these Google Apps are working fine in Firefox and IE where DOM attributes are defined on prototype chains. Probably Google Apps are using different JavaScript code depending on browsers."
08:57
<MikeSmith>
so you'd think they'd be happy if they could move to just one code path instead of needing to maintain two
08:58
<MikeSmith>
Ms2ger: oh, but see the next comment
09:00
<Ms2ger>
Yeah, indeed
09:04
<jochen__>
as I noted on the bug, I think that statement is false
09:04
<Ms2ger>
I'll try to look at your javascript: urls later, haven't had time yet
09:04
<jochen__>
it's just that the new codepath for the attributes in v8 was not tested very well and likely broken
09:05
<Ms2ger>
Anyway, we'll see :)
09:05
Ms2ger
heads off for a while
09:07
<MikeSmith>
jochen__: yeah your comment is the one I meant by "oh, but see the next comment"
09:08
<MikeSmith>
so, I'll got back to remaining optimistic
09:10
<MikeSmith>
hsivonen: if it's OK with you, I'd like to add "Access-Control-Allow-Headers: content-type" to the validator response headers
09:10
<MikeSmith>
for context see http://lists.whatwg.org/pipermail/implementors-whatwg.org/2013-December/000338.html
09:14
<jochen__>
:)
09:16
<MikeSmith>
hsivonen: otherwise, if somebody wants to use the validator REST interface with XHR, they have to send the "laxtype" parameter and even then they'll get back a "Being lax about non-HTML Content-Type: text/plain" warning
09:18
<MikeSmith>
jochen__: it will be nice to see the interface tests in the web-platform-tests testsuite working in Chrome (since for most of those we rely on a test harness that in turn relies on conformant WebIDL support)
09:21
<jochen__>
yes
09:22
<jochen__>
however, the patch Kentaro uploaded only moved "popular" attributes
09:22
<MikeSmith>
jochen__: oh really?
09:22
<MikeSmith>
didn't know
09:22
<jochen__>
i guess the idea is that if the popular ones work, we can mass-move the rest
09:23
<MikeSmith>
that sounds like a sane way to do it I guess
09:28
<MikeSmith>
hsivonen: to be clear, ideally a Web app should be able to do .setRequestHeader("Content-type", "text/html") for an XHR to the validator. But if it does then the request gets preflighted and rejected because the validator doesn't send "Access-Control-Allow-Headers: content-type" in the options response
09:31
<MikeSmith>
hsivonen: so if we add "Access-Control-Allow-Headers: content-type" it will eliminate the need for apps to send the laxtype parameter, and eliminate the warning message the gets reported bacause of that
09:33
<hsivonen>
MikeSmith: oops. I missed that aspect of CORS. Yeah, sure, it makes sense to add that.
09:34
<hsivonen>
I wonder if there are other headers that should be allowed
09:34
<MikeSmith>
yeah I wondering the same thing
09:34
hsivonen
tries to see if Content-Length and such are permitted by default by the spec
09:35
<hsivonen>
"To be clear, the method and header fields are mutually exclusive. When one of them is empty the other is non-empty." what's that about?
09:36
<annevk-cloud>
That is about caching
09:37
<hsivonen>
annevk-cloud: yeah, but does it mean that allowing methods GET and POST would remove the need to care about particular headers?
09:37
<annevk-cloud>
Content-Length is set by the UA iirc
09:37
<annevk-cloud>
No it does not
09:37
<annevk-cloud>
It just means that the cache entry is either for a header or a method
09:38
<hsivonen>
oh
09:38
<annevk-cloud>
Is hopefully clearer in Fetch
09:38
<annevk-cloud>
If not, bug reports appreciated
09:38
<hsivonen>
does validator.nu need to add Access-Control-Allow-Methods, too?
09:39
<hsivonen>
or maybe it already does in OPTIONS responses
09:39
hsivonen
should look at the source
09:39
<annevk-cloud>
If you allow more than GET and POST
09:39
MikeSmith
is looking right now also
09:40
<MikeSmith>
my tests with POST already work fine
09:40
<annevk-cloud>
If you feel your setup is secure you could allow any header
09:40
<annevk-cloud>
Just echo the requested headers
09:41
<MikeSmith>
I think that might be overkill but maybe not
09:41
<hsivonen>
it already does Access-Control-Allow-Methods", "GET, HEAD, POST, OPTIONS
09:41
<hsivonen>
which is why POST works
09:42
<annevk-cloud>
POST works by default though iirc
09:42
<annevk-cloud>
HEAD is also whitelisted
09:42
<annevk-cloud>
And OPTIONS is part of the protocol
09:43
<JakeA>
annevk-cloud: What's going on with promises at the moment, which spec is "the spec"?
09:44
<JakeA>
Just saw https://code.google.com/p/v8/source/browse/branches/bleeding_edge/src/promise.js?spec=svn18113&r=18113 - and there's things like Promise.resolved and Promise.one, which aren't in https://github.com/domenic/promises-unwrapping/blob/master/README.md
09:45
<MikeSmith>
hsivonen: btw I see Access-Control-Policy-Path in there. in VerifierServlet.java. I guess we should get rid of that
09:45
<hsivonen>
MikeSmith: I can't remember what that is about
09:45
<hsivonen>
MikeSmith: something that has been removed from the spec?
09:46
<MikeSmith>
hsivonen: yeah, long gone now
09:55
<MikeSmith>
hsivonen: btw while we're on the subject of headers, I'd like to also propose we change the Accept header that the validator's sending, so that it's something closer to what browsers send
09:56
<MikeSmith>
right now it's sending "/*; q=0.1, application/docbook+xml, application/xhtml+xml, application/xml; q=0.5, image/svg+xml, text/html; q=0.9, text/xml; q=0.3"
09:56
<MikeSmith>
oops
09:57
<MikeSmith>
make that */* at the beginning
09:58
<MikeSmith>
anyway I think it might be better to send just, e.g., "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"
10:00
<MikeSmith>
one reason I suggest it is that currently tit can cause the validator to get sent an application/xhtml+xml version of document while browsers get sent a text/html version of that same document
10:11
<dekiss>
I have weird problem, I made emai lnewsletter, the newsletter has too much scrolling on mobiles, why?
10:11
<dekiss>
I have viewprot meta tags, the email newsletter looks too much zoomed in iphone why?
10:12
<dekiss>
I have this <meta content='width=device-width, target-densitydpi=device-dpi, initial-scale=1.0, maximum-scale=1.0, user-scalable=0' name='viewport' />
10:15
<MikeSmith>
hsivonen: looking at the code it seems like the order the Accept header is being built in is good but it doesn't get preserved because it's going into a TreeSet. So I think I could keep the rest of that code as-is but just change it to use a LinkedHashSet
10:16
<MikeSmith>
dekiss: I don't think you can expect much help here with that question. Not sure where to suggest instead though
10:21
<dekiss>
ok
10:27
<darobin>
who said that public-html saw no useful discussion? I have proof to the contrary: http://lists.w3.org/Archives/Public/public-html/2013Dec/0003.html
10:27
<hsivonen>
MikeSmith: OK
10:28
<hsivonen>
MikeSmith: especailly the html5 facet of the validator should use the same Accept header as browsers
10:29
<hsivonen>
even the new validator is now old enough to be legacy code like this :-(
10:34
<MikeSmith>
heh
10:34
<Ms2ger>
My eyes glazed over, but right before that I saw "Deprecating tags such as <center> is a mistake."
10:36
<MikeSmith>
hsivonen: so I'll change Accept and also add Access-Control-Allow-Headers for content-type for now
10:36
<hsivonen>
MikeSmith: ok
10:36
<MikeSmith>
Ms2ger: you're clearly not reading with the proper mindset
10:37
<Ms2ger>
MikeSmith, quite likely
10:37
<Ms2ger>
MikeSmith, I did click on a link to a public-html email, so that already says a lot about the proper mindset
10:37
<MikeSmith>
heh
10:38
<MikeSmith>
Ms2ger: you got public-html-rolled by darobin
10:38
<MikeSmith>
or maybe it should be public-html-goatse'd
10:39
<darobin>
hahaha
10:44
<annevk-cloud>
JakeA: Domenic's repo is the spec, Google is not following it afaict
10:54
<MikeSmith>
annevk-cloud: "Based on prototype at https://github.com/rossberg-chromium/js-promise which informed the latest spec draft version at https://github.com/domenic/promises-unwrapping/blob/master/README.md"; in his commit message
10:55
<annevk-cloud>
Andreas disagrees with some stuff so he implemented it differently
10:56
<annevk-cloud>
Not sure whether that's a good thing yet
10:57
<MikeSmith>
explicitly basing the browser implementation on his own speculative JS prolyfill instead of a spec seems a bit odd
10:59
<annevk-cloud>
Yeah is odd, just not sure if it is wrong
11:39
<JakeA>
Promise.race vs Promise.one I don't care about. Not convinced it's useful. An opposite to Promise.all would be useful.
11:40
<JakeA>
Promise.resolved is only a better name if you don't pass in an arg. For most cases Promise.resolve is better
11:56
<annevk-cloud>
Yeah, the bikeshedding seems wrong
11:56
<annevk-cloud>
More thinking about deferreds
13:35
<zcorpan>
hmm, it seems presto/blink/gecko actually use utf-8 query encoding when resolving <base href>
13:40
<zcorpan>
...or not, bogus test
13:44
<zcorpan>
data:text/html;charset=windows-1252,<!DOCTYPE%20html><script>document.write('<base%20href%3Dhttp%3A%2F%2Fexample.invalid%2F%3F%5Cu00e5><a%20href><%2Fa>')%3Balert(document.links%5B0%5D.href)%3B<%2Fscript> is a correct test
13:46
<zcorpan>
note to self: about:blank uses utf-8
13:52
<zcorpan>
IE seems to drop the query
14:10
<darobin>
what's the expected way to run html5lib-python tests against a different source of tests than the submodule?
14:11
<darobin>
jgraham: ^^
14:13
<darobin>
also, is there a way of running the tests against just a subset of the data?
14:13
<jgraham>
darobin: You aren't really expected to do that :)
14:13
<darobin>
jgraham: bah!
14:13
<jgraham>
What's the use case?
14:13
<darobin>
how can you try out something new then?
14:14
<jgraham>
Add it to the existing tests?
14:14
<darobin>
well, yeah, but I want to run my tests before pushing it to the repo
14:15
<darobin>
jgraham: the situation is: I have new tests in my own fork of html5lib-tests and I'd like to run them before making a PR
14:15
<jgraham>
darobin: That sould JustWork, no?
14:15
<jgraham>
*should
14:15
<darobin>
mmmm, I guess there's something I'm not understanding
14:16
<darobin>
should I just nuke the submodule in html5lib-python that brings in the tests and replace it with my own?
14:16
<darobin>
I mean I can easily do that and ln -s instead — it just seems more brutal than what I'd expect :)
14:17
<jgraham>
Why wouldn't you jsut add your own tests to the submodule?
14:18
<darobin>
the submodule is 1) not my repo so I can't initiate a PR from it; 2) normally submodules are stuck at a given revision
14:20
<darobin>
but clearly that's not a problem you've had, I presume all the tests have been written by html5lib maintainers anyway :)
14:20
<darobin>
I'll resort to ln and leave you get back to whatever
14:20
<jgraham>
Well the submodule thing is new
14:20
<darobin>
what I was thinking of is some option to pass to nosetests so that it'd pick up the tests data from elsewhere; or some such
14:21
<jgraham>
So I think that won't work because it will try to read the data files from the original location in any case. But I might be wrong
14:23
<darobin>
I'm removing the original location and replacing it with a symbolic link
14:23
<darobin>
let's see
14:24
<darobin>
seems happy enough
14:24
<jgraham>
OK
14:24
<annevk>
zcorpan++ if you're writing tests for that
14:24
<annevk>
zcorpan: my URL tests don't cover those aspects
14:25
<darobin>
jgraham: and I'm guessing the answer to "can I just run on a subset of the tests?" is "mmm, why would you want to do that?" :)
14:25
<darobin>
whoa, lots of broken tests
14:26
<SimonSapin>
darobin: you can commit and push from a submodule
14:26
<darobin>
SimonSapin: yeah, but it's hardcoded to be https://github.com/html5lib/html5lib-tests.git whereas I'm using my own fork
14:27
<SimonSapin>
you can still add a remote
14:27
<SimonSapin>
I typically have two remotes for github stuff: upstream and fork
14:28
<jgraham>
Yeah, it's just a normal repo except that the metadata is kept somewhere strange
14:35
<zcorpan>
annevk: https://critic.hoppipolla.co.uk/r/437
15:10
<annevk>
So http://online.wsj.com/news/articles/SB10001424052702304355104579236261045331876 is published in opinion, but who wrote it?
15:10
<annevk>
If there's no name, does it mean the WSJ team is behind it?
15:11
<jgraham>
YEs, I think that's how it works
15:19
<zcorpan>
image/svg+xml in an iframe shouldn't inherit the encoding, right? it should just use xml's encoding rules
15:23
<darobin>
annevk: "Editorial board member Joe Rago"
15:24
<darobin>
(for the related video — which points to the same conclusion)
15:27
<darobin>
jgraham: is there some reason for what tests are in what files?
15:28
<jgraham>
darobin: It is a philosopical treatise on existential disorder
15:29
<jgraham>
Either that or material for Dan Brown to use in his next "novel"
15:29
<darobin>
jgraham: thanks, that's the impression it left me with
15:29
<darobin>
I preferred the first one
15:29
<jgraham>
Well done
15:29
<jgraham>
You win a French citizenship
15:30
<jgraham>
(at least I imagine that's how it works)
15:31
<Ms2ger>
And an induction into Opus Dei
15:31
<darobin>
may I win anything I don't already have?
15:31
<Ms2ger>
A sense of humour?
15:32
<darobin>
also, I presume that html5lib failing several tests currently in the suite is normal?
15:32
<jgraham>
I don't think so
15:32
<jgraham>
But ask gsnedders
15:32
<jgraham>
Which tests are they?
15:32
<darobin>
Ms2ger: don't worry, becoming more proficient with python is definitely giving me one
15:33
<darobin>
jgraham: if I use the tests from the submodule (so at a given revision) all pass, but with the latest from the repo they don't
15:33
<darobin>
28 fail
15:33
<jgraham>
Oh
15:33
<darobin>
most seem to do with <command>
15:33
<jgraham>
Sounds plausile
15:33
<darobin>
and weird characters in doctype
15:33
<jgraham>
*plausible
15:33
<jgraham>
Especially if the spec also changed
15:34
<darobin>
okay, thanks!
15:41
<annevk>
darobin: that he wrote the piece?
15:42
<darobin>
annevk: that it comes from the WSJ as an entity — it's a practice that's not uncommon in certain parts of the press
15:43
<darobin>
editorial opinions are the opinion of the journal, not just some guy
15:43
<annevk>
darobin: ta
15:44
<darobin>
annevk: I don't know how the WSJ operates, but e.g. in the Economist all the articles are unsigned (except the columns which are pseudonymous)
15:46
<annevk>
darobin: when I read the Economist there was no "opinion" thingie, but I guess a column counts as a similar thing
15:47
<darobin>
annevk: it's the Economist, they are cocksure enough to any of their opinions facts ;-)
15:48
<annevk>
uhuh, whenever they wrote about the web though...
15:53
<darobin>
annevk: if you know of a single newspaper that writes smart stuff when they're writing about a topic you really know, I'd be happy to hear about it
15:54
<annevk>
Daring Fireball is pretty good, but not a newspaper
15:54
<annevk>
also have to read the bits about Google with care
15:55
<darobin>
and anything related to Apple being awesome
15:59
<jgraham>
I would really not cite Daring Fireball as a source of good journalism
16:02
darobin
is wondering if update_html5lib_tests.py really makes sense
16:04
<darobin>
whoa, and it looks like we haven't updated WPT from it in a while
16:06
<jgraham>
darobin: Makes sense in what way?
16:06
<arunranga>
annevk, are you ok with the current handling of blob: URLs, query, etc.? Not sure if your bug update to 23946 means you think more needs to be done, or if it can be closed.
16:08
<darobin>
jgraham: well, reading the source, there are two modes
16:08
<darobin>
jgraham: the basic one is that you give no arguments and it uses the tests from inside the html5lib source — that part is okay
16:08
<darobin>
jgraham: the other is that it checks if sys.argv is > 2 but then it only looks at sys.argv[2]
16:09
<darobin>
and only takes one directory
16:09
<darobin>
so I'm calling it as python update_html5lib_tests.py xxx /path/to/tests
16:09
<darobin>
seems to work
16:09
<darobin>
but nonsensical :)
16:11
<jgraham>
I think it used to take another argument. Probably got lost somewhere when I updated it :)
16:12
<darobin>
heh
16:12
<jgraham>
Anyway, fixes welcome I guess
16:13
<darobin>
is anyone relying on this?
16:13
<darobin>
(that we know of)
16:13
<annevk>
Cyrillic is a real mess
16:13
<jgraham>
darobin: No, I think it's just used to import the tests
16:13
<annevk>
Only encoding group with five entries in Firefox Nightly's new menu
16:13
<darobin>
jgraham: I wonder if it would be possible to use a more readable format in the generated JS tests
16:13
<darobin>
I mean, good luck reviewing that
16:14
<annevk>
arunranga: there's a lot of text currently and it's not clear to me when it applies
16:14
<jgraham>
darobin: You review the source and trust the generated output
16:15
<annevk>
arunranga: e.g. in the section "A definition of blob URL Scheme" (casing?) it says "A query must be ignored." which does not seem very applicable
16:15
<jgraham>
But sure, other methods of importing these tests are possible
16:15
<jgraham>
The primary one being to use XHR and parse the raw files in js
16:16
<darobin>
that might actually be a viable solution — tbh I'm not even sure what you're doing in there :)
16:16
<jgraham>
It depends how much you trust XHR to deliver unchanged bytes
16:16
<jgraham>
I decided at the time that I didn't very much
16:16
<Domenic_>
annevk: any resources on why WebIDL/etc. switched from stupid int constants to nice string constants for enums? Helping a coworker convince other coworkers that string enums are fine.
16:16
<darobin>
fair enough
16:17
<jgraham>
It might be worth revisting that assumption now
16:17
<darobin>
jgraham: I'm not annoyed enough to change it at this point, it's great that we have what we have
16:17
<darobin>
but I might look into it at some point, it's a bit of a long ride to get something all the way in
16:17
<jgraham>
darobin: Yep
16:17
darobin
hopes no one comes back with a "that's what she said" joke here
16:17
<Ms2ger>
twss
16:17
<Ms2ger>
Damn you!
16:17
<darobin>
heh
16:19
<arunranga>
annevk, ok, that makes sense.
16:19
annevk
looks
16:19
<annevk>
Domenic_: hmm http://lists.w3.org/Archives/Public/public-script-coord/2010OctDec/0098.html and then https://www.w3.org/Bugs/Public/show_bug.cgi?id=11451
16:20
<Domenic_>
annevk: perfect, thanks!
16:23
<annevk>
arunranga: I think I'd prefer moving to a place where we have createObjectURL() defined as creating the URL and then a separate place that does the lookup
16:23
<annevk>
arunranga: it's not clear we need anything else
16:23
<annevk>
arunranga: the lookup being the bit that gets passed a URL object whose scheme is "blob" and then uses the scheme data to find an entry in the table to locate the relevant resource
16:25
<arunranga>
annevk, I think I agree, actually.
16:25
arunranga
wanders off to reorganize the spec a bit
17:23
<gsnedders>
<b><b><b><b>x</b></b></b></b>y — when </b> is passed to the AAA, what's on the list of active formatting elements?
17:25
gsnedders
is pretty sure html5lib is wrong here
17:26
<jgraham>
[b,b,b]
17:27
<gsnedders>
Why?
17:27
<gsnedders>
Why only three?
17:27
<jgraham>
http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#push-onto-the-list-of-active-formatting-elements
17:28
<gsnedders>
Oh.
17:28
<gsnedders>
I should, like, follow xrefs and not assume simplicity.
17:28
<gsnedders>
jgraham: This is needed solely to help avoid the O(n^2) case without breaking content, right?
17:29
<jgraham>
Yeah, something like that
17:30
<gsnedders>
Thanks for pointing out my obvious wrongness. :)
17:30
<jgraham>
No problem
17:30
<jgraham>
I'm sure you would do the same for me
17:31
<gsnedders>
But of course. :)
17:39
<gsnedders>
<b><table><tr><td>a<foo>b</b>c — is "c" in foo?
17:40
<gsnedders>
Yes, it is, obviously.
17:41
<gsnedders>
That was me just being totally stupid.
17:48
<Hixie>
gsnedders: the noah's ark clause isn't to avoid O(N^2) complexity, it's to avoid O(N^2) memory usage
17:51
<gsnedders>
I should stop asking questions and just send the damned email before more people say even more of what I wrote is wrong :)
17:52
<gsnedders>
Hixie: But it works in tandem with the AAA loop limits, right?
17:55
<gsnedders>
jgraham, darobin (if you see this): yes, it's known html5lib-python doesn't pass tests at the top of master of html5lib-tests, thus why the submodule isn't at that revision.
17:55
<gsnedders>
(Because html5lib-python isn't up to date with the spec, but html5lib-tests is.)
18:24
<Hixie>
gsnedders: something like that
18:25
<Hixie>
gsnedders: it's not necessary about the AAA
18:25
<Hixie>
gsnedders: the AAA is more about how to handle misclosed tags
18:25
<Hixie>
gsnedders: noah's ark is more about how to handle deep pointless trees or trees that just never close
18:29
<Hixie>
heycam|away: ping https://www.w3.org/Bugs/Public/show_bug.cgi?id=22646
18:57
<gsnedders>
The new W3C ruby stuff, are people implementing this?
18:59
<Ms2ger>
I hope not
18:59
<gsnedders>
Then we reject darobin's pull requests?
19:00
<Ms2ger>
No, we accept the test cases and fix the expectations :)
19:00
<gsnedders>
:)
21:01
<Hixie>
MikeSmith: if you have any idea for https://www.w3.org/Bugs/Public/show_bug.cgi?id=23659 please do bounce them around :-)
21:56
<Hixie>
sweet kittens the web's focus model is complicated when you get right down to it
21:57
<Hixie>
and <dialog> is not going to help make it simpler
22:11
<Hixie>
i need a word for "object that manages clusters of focusable objects"
22:11
<Hixie>
the best i've come up with so far is "focusable liege", so please feel free to bikeshed...
22:17
<Hixie>
oh lordy
22:18
<Hixie>
i know where this is headed
22:18
<Hixie>
i'm going to accidentally end up defining the web's key event routing algorithm
22:36
<zcorpan>
Hixie: define hit testing while at it :-)
22:55
<Hixie>
zcorpan: that's an entirely separate problem, luckily
23:08
<jgraham>
Luckily for whom?
23:10
<Hixie>
me
23:10
<Hixie>
man, i had no idea keyboard focus was this complicated as it is
23:11
<jgraham>
That's not very community-spirited of you :p
23:12
<Hixie>
:-P
23:13
<Hixie>
seriously, nobody has a better word than "liege" for the object that manages focusables?
23:15
<jgraham>
Isn't an object that manages usually called a "manager"?
23:16
<Hixie>
hm, i thought we already used that term
23:16
<Hixie>
but i guess not!
23:16
<Hixie>
manager it is
23:18
<Hixie>
i wish english had a term for "ancestor-or-self"
23:20
<jgraham>
Well there's something you have in common with the xpath folks
23:20
<Hixie>
and dom, yeah
23:20
<Hixie>
unlike both of those, however, i prefer to contort my english prose with redundancy rather than contort it with an invented term "ancestor-or-self" :-P
23:25
<Hixie>
what do you think of tabindex="group 1" as being a way to declare a tabindex scope? it wouldn't do anything except scope the tabindex of descendants
23:25
<Hixie>
context is https://www.w3.org/Bugs/Public/show_bug.cgi?id=23960