| 00:20 | <TabAtkins> | annevk: Bikeshed has an "error" definition type. WebIDL doesn't use it, but I have a "patches welcome" from heycam to mark up all of WebIDL's definitions in a Bikeshed-friendly way. ^_^ |
| 03:59 | <Domenic> | caitp-: of the top of my head I can't think of anything that it could break just by shipping in browsers. what might break is interactions between new libraries using it and old code that doesn't expect nonstandard tags, but that would be a developer-level problem, not a browser-level problem. |
| 04:14 | <caitp-> | hmm |
| 17:09 | <zewt> | ... why is the whatwg.org certificate working? heh |
| 17:09 | <zewt> | it's a wildcard for *.whatwg.org, but it's applied to hostnames like url.spec.whatwg.org, and last I knew wildcard certificates were only valid for one level of nesting |
| 17:10 | <zewt> | did that change recently? it was a braindamaged restriction |
| 17:12 | <zewt> | can't find any browsers rejecting it, maybe it was just one browser that started doing that and they backed out of it |
| 22:02 | <boogyman> | is anyone else getting a 406 (not accepted) for stylesheet requests to w3c.org ? |
| 22:04 | <boogyman> | btw, this only occurs with Chrome 38.0.2125.104m on Windows 8 |
| 23:45 | <MikeSmith> | boogyman: sounds like you may have hit the rate limiter |
| 23:45 | <Hixie> | zewt: it's a wildcard for *.spec.whatwg.org |
| 23:46 | <boogyman> | for single requests? interesting. |
| 23:49 | <MikeSmith> | ah wait no if that were the case you'd be getting 503s |
| 23:49 | <MikeSmith> | what is a 406? |
| 23:49 | <boogyman> | not accepted |
| 23:50 | <MikeSmith> | actually "not acceptable" it seems |
| 23:51 | <boogyman> | So, should I be filing a bug with Chrome? because I was just attempting to load the w3c.org site, not doing anything fancy. |
| 23:51 | <MikeSmith> | which is something different that I guess indicates a problem with the Accept header in the requests your ua is sending |
| 23:52 | <MikeSmith> | boogyman: yah sounds to me like a bug in th UA |
| 23:52 | <boogyman> | D'oh User-Fail. I had an Accept header extension loaded. |
| 23:53 | <MikeSmith> | ah |
| 23:53 | <MikeSmith> | why |
| 23:54 | <boogyman> | The addon will send the configs to any request, it appears w3c is actually parsing them. I was testing an API I've been developing |