| 00:08 | <TabAtkins> | jsbell: Travis was failing earlier due to a Bikeshed bug, so it just needs a poke (or another commit). |
| 00:09 | <jsbell> | Thx. If a WHATWG-empowered person could poke it I'd appreciate it; I want to link to a new dfn in the commit. |
| 02:53 | <Domenic> | botie: tell jsbell I poked it https://travis-ci.org/whatwg/dom/builds/208150332 |
| 02:53 | <botie> | will do |
| 08:58 | <nox> | annevk: https://github.com/w3c/web-platform-tests/issues/2499#issuecomment-284365616 Months later I'm afraid I don't remember. :P |
| 12:24 | <smaug> | foolip: https://www.chromestatus.com/metrics/feature/timeline/popularity/865 gives me AddEventListenerFourArguments |
| 12:25 | <smaug> | oh, it is just slow to update |
| 12:45 | <foolip> | smaug: sounds like https://github.com/GoogleChrome/chromium-dashboard/issues/220 |
| 12:46 | <smaug> | ah, yes |
| 14:02 | <annevk> | jgraham: here's a case where it's been hard to find a reviewer: https://github.com/w3c/web-platform-tests/pull/4811 |
| 14:04 | <annevk> | jgraham: I actually do find myself sometimes landing certain changes to XMLHttpRequest without review, just because the level of interest is really low |
| 14:13 | <jgraham> | annevk: I'm totally happy with the level of review than Domenic gave in that case |
| 14:15 | <Domenic> | "Please refer to the URL Continually Updated Specification" lol (from https://www.w3.org/TR/url-1/ ) |
| 14:15 | <jgraham> | annevk: I mean, I am sympathetic to your concern :/ |
| 17:10 | <botie> | jsbell, at 2017-03-07 02:53 UTC, Domenic said: I poked it https://travis-ci.org/whatwg/dom/builds/208150332 |
| 17:19 | <alextes> | aaaah this is where you guys hide |
| 17:19 | <alextes> | I'm looking for stevenvachon |
| 17:20 | <alextes> | but maybe someone else can answer this question for me too |
| 17:24 | <alextes> | Steven suggested we add whatwg-url support to a tiny request lib I like to help maintain. Node only. It supports Node v4+ (maybe in a month v6+), that begs the question how to support whatwg-url in earlier node versions. However, after contemplating this a bit I realised it's likely Steven just meant to suggest for the lib to seamlessly support whatwg-url on Node v8+. Currently it does something before passing to Node's http module which breaks this. I'm |
| 17:24 | <alextes> | hoping there are folks from the workgroup here that know about an effort to get libs everywhere to seamlessly start supporting whatwg-url when Node does. |
| 17:25 | <alextes> | Giving stevenvachon a mention would also be hugely appreciated, can't track down his handle :[ |
| 17:37 | <annevk> | alextes: I think steven is sometimes here under that handle, some folks here help maintain whatwg-url and then separately Node.js added a native URL library recently that conforms to the same standard |
| 17:40 | <Domenic> | alextes: I maintain the jsdom/whatwg-url npm package, but I can't quite understand your problem. |
| 17:44 | <Sebmaster> | alextes: Node has an implementation of the URL standard natively nowadays. The whatwg-url package independently implements the whole spec and could be used to shim that capability for older versions which do not support it. |
| 20:11 | <JoWie> | instances of HTMLObjectElement are typeof "function" in firefox and chrome. where can i find this in the html spec? or has this never been specced? |
| 20:47 | <jsbell> | JoWie: That'd be in https://heycam.github.io/webidl/#es-interfaces |
| 20:50 | <smaug> | how do people review spec changes when specs tend to use so overlong lines |
| 20:50 | <smaug> | and github has the worst tooling for reviewing |
| 20:51 | <jsbell> | Oh, instances, hrm... |
| 20:52 | <TabAtkins> | smaug: Yell at those specs for using shitty line-breaking, and recommend they use semantic linefeeds http://rhodesmill.org/brandon/2012/one-sentence-per-line/ like a civilized person. |
| 20:52 | <jsbell> | JoWie: sorry, ignore my previous comment. Looking... |
| 20:53 | <smaug> | JoWie: FWIW, I get "object" in FF |
| 20:53 | <smaug> | Chrome for some reason gives function |
| 21:16 | <jsbell> | joWie: HTMLObjectElement and HTMLEmbedElement used to have legacycaller applied. Defined https://heycam.github.io/webidl/#idl-legacy-callers and removed https://github.com/whatwg/html/pull/1979/files - Gecko (FF) removed recently https://bugzilla.mozilla.org/show_bug.cgi?id=909656 but Blink (Chrome) has not yet https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/MuxvaXiyBxU/GRICeJm0hHkJ |
| 21:18 | <jsbell> | Oh, blink removed too, just hasn't hit stable yet (landed Feb 13) |
| 21:18 | <jsbell> | https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/AiDZ7ru9mGg/_D_9Fcc2AwAJ |
| 21:18 | <jsbell> | So that should go away soon |
| 21:20 | <JoWie> | jsbell: ah thanks |
| 21:53 | <alextes> | thank you for the replies annevk Domenic Sebmaster |
| 21:54 | <alextes> | So to Domenic and Sebmaster a shim for older versions is nice, but what I'm unclear on is how you would then expect people to use the node modules that expect their own 'options' object for older versions. |
| 21:54 | <Domenic> | alextes: what options object are you talking about? |
| 21:54 | <alextes> | https://nodejs.org/api/http.html#http_http_request_options_callback |
| 21:55 | <Domenic> | alextes: oh, I don't know, whatwg-url wasn't meant to be used with that |
| 21:55 | <alextes> | Alright. |
| 21:57 | <alextes> | I guess I should ask node folks how they feel about throwing a whatwg-url href into the node url parser. |
| 22:00 | <Sebmaster> | alextes: Why not just serialize out the fully resolved url to a string? |
| 22:00 | <Sebmaster> | Before you provide it to the options object |
| 22:00 | <alextes> | I thought this is what href was from looking at: https://nodejs.org/api/url.html#url_url_href |
| 22:01 | <alextes> | I guess 'toString' is more appropriate :] |
| 22:01 | <alextes> | is that what you meant? |
| 22:04 | <alextes> | Sebmaster ^ |
| 22:04 | <Sebmaster> | No I mean why are you not calling this yourself before sticking it into the request object? |
| 22:18 | <alextes> | Sebmaster because node v4 doesn't have it. |
| 22:19 | <alextes> | If I use the shim I still don't have something I can pass to node's http modules. |
| 22:20 | <alextes> | But I'd say perhaps serialising at that point is acceptable. I don't know in which scenarios whatwg-url might serialise to something node v4 does not support. |
| 22:22 | <Sebmaster> | alextes: if you use the shim, you can just serialize with .href and can pass it in |
| 22:22 | <alextes> | Alright, good to know, thanks! |