00:13
<GPHemsley>
Hixie_: ¿Qué es esto? https://www.w3.org/Bugs/Public/show_bug.cgi?id=26787
00:18
<GPHemsley>
List archive is broken? http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-February/030179.html
00:41
<Hixie_>
GPHemsley: load it in a browser that you haven't visited www.whatwg.org in recently and you should be fine
00:42
<GPHemsley>
Hixie_: Why's that?
00:43
<GPHemsley>
"Firefox can't establish a connection to the server at lists.whatwg.org."
00:43
<Hixie_>
because if you've visited whatwg.org recently you'll have received the STS header
00:43
<Hixie_>
which tells your browser to never open an http:// connection to a whatwg.org subdomain
00:43
<Hixie_>
yet dreamhost haven't yet made lists.* subdomains support https
00:44
<GPHemsley>
oh, interesting
00:47
<GPHemsley>
oh, so, being broken is the expected state at the moment?
00:47
<Hixie_>
we're pretending lists.whatwg.org never existed
00:48
<Hixie_>
see how all mention of it has been scrubbed from whatwg.org/mailing-list, for instance
00:48
<GPHemsley>
ah
00:48
<GPHemsley>
are all the archives at w3.org now?
00:48
<Hixie_>
archives for whatwg@ have been available on w3.org for some time
00:49
<Hixie_>
and are much nicer than the lists.whatwg.org ones
00:49
<GPHemsley>
yeah, sorry, I didn't phrase that clearly: I meant, this has an equivalent page on w3.org somewhere?
00:49
<Hixie_>
what does "this" in that sentence refer to?
00:50
<GPHemsley>
the particular link I gave
00:50
<Hixie_>
oh
00:50
<Hixie_>
yes
00:50
<Hixie_>
no idea what it is though :-)
00:50
<Hixie_>
http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Feb/0025.html
00:51
<GPHemsley>
that was a quick turnaround :P
00:51
<Hixie_>
open the page, copy the first sentence into google...
00:51
<GPHemsley>
ah, you and your other browser
00:53
<GPHemsley>
(this is probably a naive question, I'm realizing now...) is there really a usecase for forcing a URL to HTTPS that doesn't actually connect?
00:53
<Hixie_>
preventing someone from DOSing the secure site and MITMing the insecure one
00:54
<GPHemsley>
yeah, that was basically what I expected the answer to be
00:55
<GPHemsley>
but aryeh's site is dead anyway?
00:58
<Hixie_>
GPHemsley: http://web.archive.org/web/20121127212525/http://aryeh.name/spec/innertext/innertext.html
00:59
<GPHemsley>
you and your lack of laziness :P
00:59
<Hixie_>
yeah, copying and pasting urls into text fields, such hard work
00:59
<GPHemsley>
I should probably work on my existing spec before I worry about other ones...
00:59
<Hixie_>
:-P
01:03
<GPHemsley>
Incidentally, I am soliciting suggestions for a good computer desk. Feel free to send them my way (publicly or privately), as I am currently stationed on the floor.
01:20
<Domenic>
terinjokes: don't listen to the haters; GitHub issues are 1000x better than mailing lists.
01:21
<Hixie_>
github issues are terrible
01:21
<Hixie_>
bugzilla bugs are pretty awesome though
01:25
<caitp->
flexible and powerful but not well designed
01:41
<terinjokes>
i already have haters
01:41
<terinjokes>
awesome
08:22
<annevk>
terinjokes: haters?
08:27
<annevk>
Domenic: asynchronously is now something else, might want to update guides: https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel
08:41
<annevk>
I did not realize that if you're not using Nightly you don't get mixed content warnings in the UI for images
08:43
<annevk>
Can anyone tell me if https://codereview.chromium.org/265973003 is in Chrome stable?
08:48
<annevk>
Alternatively, run http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3191 and tell me what it says
09:37
<annevk>
hsivonen: observation: the messaging that crypto is too hard for people to try themselves discourages people from playing around in that area; it might makes sense if you deploy sites, but not in the general sense
13:20
<GPHemsley>
Bugzilla > GitHub
15:31
<JonathanNeal>
Am I reading kangax wrong or does this suggest Chrome 35+ has String.prototype.contains? http://kangax.github.io/compat-table/es6/#String.prototype.contains
15:43
<JakeA>
annevk: going to binge on tickets next week, sorry for not really giving it the attention it deserves of late
15:44
<JakeA>
*conferences*
15:47
<annevk>
JakeA: getting input on the cache stuff would be good
15:48
<annevk>
JakeA: if you run into some networking people, point them to it :-)
15:49
<JakeA>
annevk: yeah, cache API consensus will be a priority. Will likely organise a call once I've gone through the issues
15:50
<JakeA>
annevk: will also take another serious look at the jenga thread
15:50
<annevk>
JakeA: sorry, this was fetch() cache setttings
15:50
<annevk>
JakeA: see tweet
15:53
<JakeA>
annevk: ahh yes, will look at that too. Also people have requested some way to set expiry on SW cache items... I think that's the point you just use the browser cache, but I want to give that more thought too
15:53
<annevk>
that doesn't make sense
15:54
<annevk>
as the whole interaction with the cache API is through script, so you can't really help not inspecting it
15:54
<JakeA>
That's my gut reaction too
15:59
<annevk>
JakeA: I could imagine setting an expiry for a URL
21:14
<GPHemsley>
Hixie_: Is everything whatwg.org now (instead of www.whatwg.org)?
21:21
<tantek>
yay for no-www.org :D
21:27
<GPHemsley>
Their wall of shame is for domains that forward no-www to www. But there are more deserving websites for which no-www flat out doesn't work.
21:30
<GPHemsley>
Oh, html.spec.whatwg.org is finally canonical? \o/
21:41
<tantek>
speaking of shaming domains, http://httpshaming.tumblr.com/
21:46
GPHemsley
wonders why <code> is no longer orange
21:55
<tantek>
anybody else watching the live video stream at edgeconf.com/2014-sf ?
21:58
<GPHemsley>
Look at me, closing mimesniff bugs and stuff...
21:59
<tantek>
GPHemsley++
21:59
<GPHemsley>
:)