| 00:51 | <MikeSmith> | is “Content-Type:text/html; name="canvas-dashed-line.html"; charset=” valid syntax? |
| 00:52 | <scshunt> | MikeSmith: no |
| 00:52 | <scshunt> | MikeSmith: you need to have a value for charset= |
| 00:52 | <MikeSmith> | scshunt: ok, didn’t think so |
| 00:52 | <MikeSmith> | yeah |
| 00:52 | <scshunt> | although you shouldn't have a charset on text/html anyway |
| 00:53 | <MikeSmith> | eh? |
| 00:53 | <scshunt> | and "name" is an invalid parameter |
| 00:53 | <MikeSmith> | OK |
| 00:54 | <scshunt> | it's now considered bad form to use a charset parameter for types that provide ways to determine the charset from the body |
| 00:55 | <scshunt> | text/html does still permit this though |
| 00:56 | <MikeSmith> | interesting |
| 00:56 | <MikeSmith> | didn’t know that |
| 00:56 | <scshunt> | https://tools.ietf.org/html/rfc6657 |
| 00:56 | <MikeSmith> | text/html needs it for parsing with the right charset, and I would think other types would need it as well |
| 00:57 | <MikeSmith> | btw, that header seems to be getting set automatically by bugzilla.mozilla.org |
| 00:57 | MikeSmith | looks at https://tools.ietf.org/html/rfc6657 |
| 00:57 | <scshunt> | if you need a charset parameter, then use it |
| 00:57 | <scshunt> | :) |
| 00:57 | <scshunt> | but yeah, charset= is definitely not correct |
| 00:58 | <MikeSmith> | ok |
| 00:58 | <scshunt> | http://www.iana.org/assignments/media-types/text/html does not allow "name" as a parameter |
| 00:58 | <scshunt> | (but it should be ignored rather than treated as an error) |
| 00:59 | <MikeSmith> | yeah that header is causing the content-type parser in the HTML checker to fail in an unexpected with (java.lang.StringIndexOutOfBoundsException: String index out of range) |
| 00:59 | <MikeSmith> | ok |
| 02:16 | <MikeSmith> | wow a rare Dmitry Turin reference https://mailarchive.ietf.org/arch/msg/webpush/Al5xy2qQOBxXMrnE-SCKjUt-SJU |
| 02:51 | <MikeSmith> | http://stackoverflow.com/questions/37528006/detecting-that-a-web-worker-has-been-loaded-without-sending-an-explicit-message |
| 06:20 | <annevk> | MikeSmith: answered |
| 06:36 | <MikeSmith> | annevk: thanks |
| 06:42 | <mathiasbynens> | is https://encoding.spec.whatwg.org/ down/flaky for anyone else? |
| 06:50 | <annevk> | mathiasbynens: yeah, but others are too... |
| 06:58 | <annevk> | mathiasbynens: seems things are back up again |
| 06:59 | <mathiasbynens> | hmm, not for me, at least not consistently |
| 07:01 | <annevk> | mathiasbynens: hmm, maybe some kind of DDOS? |
| 07:02 | <annevk> | Or just DOS, I think Hixie_ pays for computing power, so if there's a spike that might just cause things to grind to a halt |
| 10:10 | <daleharvey> | Anyone on the spec side want to talk about the implementation of Notifications actions? |
| 10:12 | <daleharvey> | mostly looking around for examples, code or other right now, I am guessing this is trying to do something like what spotify or okta / oauth does with notifications, ie let you play / pause, approve / reject from within the notification? |
| 10:49 | <Ms2ger> | annevk, does a Location have an associated Document or Window? (Or WindowProxy?) |
| 10:53 | <annevk> | Ms2ger: that is defined, no? |
| 10:55 | <annevk> | daleharvey: that's the idea, yes |
| 10:55 | <annevk> | daleharvey: basically a notification with a set of buttons |
| 10:55 | <annevk> | daleharvey: the buttons representing the actions, which can be activated somehow |
| 10:56 | <annevk> | daleharvey: if you'd like an example in the specification I'm afraid you'll have to PR it or file an issue |
| 11:04 | <annevk> | Ms2ger: "Each Window object is associated with a unique instance of a Location object, allocated when the Window object is created." |
| 11:05 | <annevk> | Ms2ger: "A Location object has an associated relevant Document, which is this Location object's associated Document object's browsing context's active document." |
| 11:10 | <Ms2ger> | annevk, hrm, I vaguely remembered that location was hanging off the WindowProxy, but I guess that was wrong, then |
| 11:12 | <annevk> | Ms2ger: yeah, that'd make it very hairy |
| 11:44 | <Ms2ger> | Anyone who could check http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4244 in any of Edge/IE/Safari? |
| 11:49 | <rodneyre_> | Ms2ger anything particular to check for? |
| 11:49 | <Ms2ger> | Tell me what's logged :) |
| 11:49 | <rodneyre_> | copy to here or a gist? |
| 11:51 | <Ms2ger> | Just paste the three first lines here |
| 11:51 | <rodneyre_> | https://gist.github.com/rodneyrehm/f64c8de6d2f47c26fc6c129242012afc |
| 11:51 | <Ms2ger> | Or that :) |
| 11:51 | <Ms2ger> | Three browsers, three results |
| 11:51 | <rodneyre_> | I can check edge and ie in a few… |
| 11:52 | <Ms2ger> | That would be nice too |
| 11:52 | <rodneyre_> | no access to browserstack? |
| 11:52 | <Ms2ger> | Nope |
| 11:52 | <Ms2ger> | Asking here has worked well enough in the past :) |
| 11:56 | <annevk> | Ms2ger: you can ask jst, but I guess the #whatwg proxy works too |
| 12:02 | <rodneyre_> | bah, I can't copy from edge in browserstack, hmpf |
| 12:09 | <rodneyre_> | Ms2ger updated the gist with IE11 and Edge14 |
| 12:09 | <annevk> | Ah okay, so that's not just me |
| 12:09 | <annevk> | It gives the impression copy & paste works |
| 12:10 | <Ms2ger> | Yay, they agree with Fx |
| 12:12 | <Ms2ger> | rodneyre_, thanks |
| 14:53 | <nox> | Is the interface 'Elements' dead? |
| 15:00 | <annevk> | nox: for now |
| 15:00 | <nox> | Ah. |
| 15:00 | <nox> | annevk: Is it a live collection btw? |
| 15:01 | <annevk> | nox: no, Array subclass |
| 15:01 | <nox> | annevk: Woooo. |
| 15:17 | <nox> | annevk: When can that be integrated back? |
| 15:17 | <nox> | annevk: I was wondering with another Servo developer what React uses to build list of elements, |
| 15:17 | <nox> | and if it could avoid live collections, |
| 15:17 | <nox> | then I remembered about Elements. |
| 15:18 | <annevk> | nox: IDL-subclassing support |
| 15:18 | <nox> | Couldn't it just be [ArrayClass] or something? |
| 15:18 | <annevk> | No |
| 15:18 | <nox> | What's the difference? |
| 15:19 | <annevk> | Hmm, later/tomorrow |
| 15:19 | <nox> | (TIL ArrayClass became LegacyArrayClass.) |
| 15:19 | <nox> | annevk: Sure! |
| 16:45 | <annevk> | nox: ArrayClass puts Array on the prototype chain, but doesn't make the object an actual Array |
| 16:46 | <nox> | Oh ok. |
| 16:46 | <annevk> | wanderview: structured cloning the JSON and passing it back and forth sounds a lot slower |
| 16:46 | <annevk> | wanderview: since it needs to be serialized and deserialized |
| 16:47 | <wanderview> | annevk: we wouldn't actually do this in a real worker... we would make the parse go to an AST representation that gets rehydrated on js thread when done |
| 16:47 | <wanderview> | so just deserialize overhead |
| 16:47 | <annevk> | wanderview: but deserialize isn't that different from parsing in the first place I'd think |
| 16:48 | <wanderview> | annevk: it really depends where the costs come from... parsing the string? or js object allocation? |
| 16:48 | <annevk> | wanderview: in any event, has someone made a convincing case this is important? It seems like we should just wait for async-JSON to be a thing and ride the coattails |
| 16:49 | <wanderview> | annevk: did I say we were doing something about it today? |
| 16:49 | <annevk> | wanderview: I don't think you did |
| 16:50 | <wanderview> | annevk: I think waiting for async json spec would be good as well: https://twitter.com/wanderview/status/737684000613879808 |
| 16:51 | <annevk> | I wonder why that thread blew up a bit though, maybe just because the real reason it's async wasn't mentioned |
| 16:55 | <wanderview> | annevk: yea, I don't know... its not like any browser implements an optimization here |
| 16:55 | <annevk> | spec is sync too, though of course blackbox optimizations allowed |
| 16:56 | <annevk> | but there's all kinds of rather absurd optimizations possible here |
| 16:57 | <annevk> | e.g., you could go from bytes straight to an object structure, decoding the strings in parallel |
| 16:58 | <wanderview> | annevk: I'm more excited to learn today that edge has implemented ReadableStream already |
| 16:58 | <annevk> | wanderview: nice, hopefully there's tests |
| 17:37 | <Domenic> | It seems like a lot of the spam we get on HTML is probably via the "File an issue about the selected text" link. Given that it always contains a random multipage URL with a fragment. |
| 17:37 | <Domenic> | I can't understand how this would work though. Some kind of web crawler bot that has a GitHub account and also pushes the submit button? |
| 17:42 | <MikeSmith> | Domenic: dunno but yeah I am confused by that as well |
| 17:44 | <tantek> | the bots are getting smarter |
| 21:54 | <smaug____> | hmm, why BlobPart uses USVString |
| 21:57 | <smaug____> | oh, it doesn't work at all how I expected |
| 21:58 | <jsbell> | Expecting ByteString behavior perhaps? |
| 22:01 | <smaug____> | yeah, something closer to that. I was expecting it to take DOMString |
| 22:21 | <Garbee> | Domenic: Sadly the unit testers we have like PhantomJS that run on engine cores also make more capable spam bots all too easy to build as well. |
| 22:21 | <Garbee> | And Selenium, et. all. |