07:04
<zcorpan>
i don't see how <b><i><a><s><tt><div></b>abc</b></div></tt></s></a>xyz</i> invokes the loop limit
07:04
<zcorpan>
i wonder how old ie renders it
07:07
<zcorpan>
has an unnecessary </b>
08:11
<krijn>
Somebody in here who knows something about the WHATWG wiki?
08:12
<krijn>
Actually, never mind
08:45
<Ms2ger>
Whoa, whoa
08:46
<Ms2ger>
Microsoft is looking at http://dom.spec.whatwg.org ?
10:10
<hsivonen>
I don't see an email about polyglot by Lachy on public-html? what happened?
10:16
<othermaciej>
hsivonen: I see one by you, were you expecting one from him too?
10:23
<asmodai>
Good morning!
10:25
<asmodai>
hsivonen: talk of the devil ;)
13:35
<annevk>
I wonder at what point I should start filing bugs on browsers to fix certain bugs...
13:36
<boogyman>
annevk: you'd have a betterchance and convincing them to up the priority
13:36
<annevk>
that sentence missed "URLs"
14:13
<GPHemsley>
krijn: Anything I can help you with (re wiki)?
14:14
<krijn>
GPHemsley: nope, sorry, I misread a question somebody sent me via the logs, thought it was about the wiki
14:15
<krijn>
But I didn't understand the question itself, so I kind of stopped after that
14:15
<krijn>
It mentioned wiki somewhere in the sentence, but that's about it
14:19
<GPHemsley>
ah, ok
15:00
<annevk>
anyone from Chromium around? zcorpan found out that http://™%/ parses badly (in particular the bytes ™ is represented as in utf-8 get decoded using iso-8859-1 somehow)
15:00
<annevk>
abarth: ^^
15:18
<GPHemsley>
annevk: Is there any way you can prevent /^[a-z]+:[:\s]/i from being parsed as a URL?
15:31
<annevk>
what does [:\s] do?
15:42
<annevk>
odinho: maybe fix that CORS graphic tomorrow? ;)
15:43
<GPHemsley>
annevk: Well, a lot of error messages tend to have <term>: <error message>
15:44
<GPHemsley>
annevk: So when I copy and paste them into the location bar to search, Firefox interprets it as a URL and fails.
15:44
<annevk>
"http: test" wfm
15:45
<annevk>
but the address bar does not have much to do with URL parsing
15:46
<boogyman>
GPHemsley: that shouldn't be interpreted as a url anyway, because it's missing the slashes
15:46
<GPHemsley>
annevk: Try "warning: text"
15:47
<zewt>
annevk: well, address bar parsing should probably be a superset of url parsing (but if they decide not to do that it's not really the spec's problem)
15:47
<zewt>
eg. pasting a URL from a link should always work, but what it does with things like ^ is up to it
15:47
<GPHemsley>
boogyman: I'm not sure what you mean. There are URLs that don't have slashes (e.g. mailto:)
15:47
<annevk>
GPHemsley: seems like Gecko should not do dispatching to external handlers from the address bar but instead use Google
15:48
<annevk>
GPHemsley: doesn't make much sense to me to handle external schemes there
15:48
<zewt>
firefox even screws up "site:foo.com bar" if i try to search in the address bar, heh
15:48
<annevk>
opera does too
15:48
<GPHemsley>
annevk: Try "irc: test"
15:48
<zewt>
(chrome gets that right, at least)
15:48
<zewt>
(site:, i mean)
15:49
<annevk>
GPHemsley: yeah sure, same thing imo
15:49
<annevk>
GPHemsley: file/http/https are the only scheme-things that should probably work there
15:49
<GPHemsley>
annevk: What are you suggesting they do for known protocols that they don't support (e.g. IRC)? Nothing?
15:49
<zewt>
anything that can fetch a file should, eg. ftp
15:49
<zewt>
anything that can launch a ui (if you have an irc handler registered, irc: should work)
15:50
<annevk>
GPHemsley: use Google?
15:50
<zewt>
(if someone gives an IRC URL in here, and i copy and paste it into the address bar, it should work if clicking a link would have worked)
15:50
<annevk>
I'd rather not have it launch UI from the address bar
15:50
<GPHemsley>
I think they'd disagree with you on that point (as do I)
15:50
<zewt>
that doesn't make sense, http is launching ui (an html document)
15:50
<zewt>
(well, if it points to html, you know what i mean)
15:51
<GPHemsley>
I agree with zewt: If I paste an IRC URL into the location bar, it should not go to search
15:51
<annevk>
no, http loads in the top-level browsing context
15:51
<annevk>
in any event, not my problem :)
15:51
<zewt>
yes, creating ui :)
15:52
<zewt>
gp: i suspect "web compatibility for URLs" and "user compatibility for people typing random noise in the address bar" is its own complicated problem; no idea what the overlap looks like
15:52
<zewt>
but the URL spec should only concern itself with the former
15:53
<zewt>
a hard enough problem by itself, heh
15:54
<zewt>
(i'm wondering if there are any cases of URLs that have to parse for web compatibility, but which conflict with address bars really wanting to parse user input differently, that might cause address bars to not accept every possible URL)
15:57
<zewt>
i suppose things like google metatags (site) could be in danger of that, where they might have to treat it differently if they end up with a scheme of "site", etc
15:58
<zewt>
(not an actual problem as long as there's no overlap between them and real schemes)
16:05
<SimonSapin>
TabAtkins: ping
16:08
<GPHemsley>
zewt, annevk: FTR, Firefox allows you to prefix something with '?' in order to force it to do a search.
16:08
<GPHemsley>
so "?site:test" will work
16:49
<annevk>
"I reserve this level of anger for when I'm flying Ryanair!" :-)
17:10
<Hixie>
annevk: not set on the top-level browsing context of a popup from an iframe that's sandboxed
17:10
<annevk>
Hixie: ah yeah, dunno either
17:11
<annevk>
Hixie: how about having cdn.whatwg.org or resources.whatwg.org or giving us access to images.whatwg.org?
17:11
<Hixie>
(that's the confusion that delayed me last time i tried to spec it, but i think it's clear now)
17:11
<Hixie>
sure
17:11
<Hixie>
you just want to stick images there, or other stuff too?
17:11
<annevk>
other stuff too
17:11
<Hixie>
k
17:11
<Hixie>
how about "anne.cdn.whatwg.org" :[D[D-)
17:11
<Hixie>
although "cdn" is a bit of a misnomer
17:12
<annevk>
yeah, agreed, Ms2ger suggested that
17:12
<annevk>
this is not just for me, fwiw
17:12
<Hixie>
yeah but i can only give one of you access at a time
17:12
<annevk>
it's for shared resources of *.spec.whatwg.org
17:12
<annevk>
Hixie: we're gonna manage access via GitHub
17:12
<Hixie>
ah right
17:12
<SimonSapin>
annevk: are you still in Lyon?
17:12
<annevk>
SimonSapin: back home
17:12
<SimonSapin>
ok
17:13
<Ms2ger>
You guys aren't taking the cdn thing seriously, are you? :)
17:13
<Hixie>
resources.whatwg.org done
17:13
<Hixie>
bbl
17:17
<annevk>
Ms2ger: well, I was, as I don't care about this bikeshed
17:29
<annevk>
I wonder if the CSS WG is open to defining "whatwggreen" as color value
17:38
<annevk>
data:text/html,<style>body{margin:.5em;font:20em sans-serif}b{color:%233c790a}</style>?&%23x2009;<b>&%23x20dd;</b>
17:38
<annevk>
so cool
17:39
<annevk>
(the thin space is arguably a hack)
17:44
<annevk>
hmm actually, ? needs to be green too
18:19
<GPHemsley>
annevk: And you gotta get the font right.
18:55
<GPHemsley>
I filled up the wiki sidebar with a bunch of linky goodness. Let me know if there's any links you want me to add.
20:28
<GPHemsley>
Can we move the spec stylesheets to resources.whatwg.org?
20:29
<Hixie>
feel free to make a copy, but i'm keeping mine :-P
20:30
<Hixie>
(i just have a spec-specific one for the HTML spec)
20:33
GPHemsley
imagines Hixie's house without any spoons or knives.
20:40
<abarth>
annevk: please file a bug: http://code.google.com/p/google-url/issues/entry
21:51
<GPHemsley>
Reviews welcome on my most recent mimesniff commit.
22:34
<smaug____>
jgraham: what was the name of the reviewing tool you talked about
22:37
<jgraham>
smaug____: critic
22:37
<jgraham>
Well technically "opera critic" (good pun, eh), but everyone calls it critic
22:38
<jgraham>
https://github.com/jensl/critic
22:38
<smaug____>
no no, obviously the page for it is http://www.theoperacritic.com/
22:40
<jgraham>
heh
22:40
jgraham
-> sleep
23:25
<gsnedders>
jgraham: It's called "opera critic"? I thought it was just "critic"?