| 06:44 | <annevk> | smaug: because table sorting is cool! |
| 07:33 | <annevk> | Where in http://testthewebforward.org/docs/ is information on how to work with cross-origin tests? |
| 07:35 | annevk | finds http://testthewebforward.org/docs/test-format-guidelines.html#tests-involving-multiple-origins |
| 07:35 | <odinho> | There's someone who always mentions table sorting. Maybe brucel? |
| 07:38 | <annevk> | odinho: also https://twitter.com/sil |
| 07:57 | <MikeSmith> | IMHO it's a failure of the priority of constituencies that we're not prioritizing table sorting higher |
| 07:57 | <MikeSmith> | it's something that normal end users would get a lot of benefit from |
| 07:59 | <annevk> | Hmm, http://天気の良い日.web-platform.test does not work locally? Lame |
| 08:01 | <annevk> | Never mind, port issue |
| 08:01 | <MikeSmith> | annevk: port? |
| 08:01 | <MikeSmith> | yeah |
| 08:01 | <MikeSmith> | http://xn--n8j6ds53lwwkrqhv28a.web-platform.test:8000/ |
| 08:01 | <MikeSmith> | 8000 |
| 08:06 | <annevk> | protip, use window.close() and not close() from an attribute event handler |
| 08:06 | <annevk> | the latter will invoke document.close() and leave you puzzled |
| 08:07 | <annevk> | MikeSmith: also needed to add <meta charset=utf-8> btw, but that was more obvious |
| 08:08 | <MikeSmith> | annevk: why did you need to add it? |
| 08:08 | <MikeSmith> | ah, for a particular test |
| 08:18 | <annevk> | MikeSmith: yeah, to make those non-ASCII code points appear properly |
| 08:32 | <odinho> | annevk: Ah, yes. True, I've seen that. |
| 09:25 | <mkwst> | annevk: Given the validation that Yoav added to DOMTokenList in https://github.com/whatwg/dom/commit/63a030265fc3dac400a99f729fd5874490ae335c, what's the expected feature detection code we'd want developers to use? |
| 09:25 | <mkwst> | Something like `var x = document.createElement('iframe'); if (x.sandbox.add('x')) { ... }`? |
| 09:26 | <annevk> | mkwst: yeah, that's what yoav suggested |
| 09:27 | <annevk> | mkwst: he submitted a patch to HTML too, but hasn't addressed my feedback yet |
| 09:30 | <mkwst> | Got it. |
| 09:30 | <mkwst> | Thanks!@ |
| 09:32 | <annevk> | yw#$ |
| 09:35 | <zcorpan> | annevk: yeah in general avoiding barewords in event handler attributes is a good idea :-) |
| 09:36 | <annevk> | zcorpan: yeah, I guess I shouldn't even try it, but I kinda appreciate the minimalism |
| 09:36 | <annevk> | zcorpan: though of course, the more often you do that, the less extensible everything becomes |
| 09:38 | <zcorpan> | JS/DOM in general is pretty hostile to extensibility |
| 09:46 | <annevk> | In a certain way, yes, but in a lot of ways, also no |
| 10:25 | <tobie> | What's the long term idea with HTML event loop vs EcmaScript job queues? |
| 10:27 | <tobie> | context: ideally the generic sensor api could be implementable both in nodejs and within a browser, trying to understand and list why it's not possible in practice. |
| 10:38 | <annevk> | tobie: I think ideally ECMAScript defers logic to the host, but different folks have different ideas :/ |
| 10:39 | <tobie> | reading JakeA's post on the event loop right now which points to https://esdiscuss.org/topic/the-initialization-steps-for-web-browsers#content-16 |
| 10:41 | <annevk> | tobie: yeah, there's a ton of unresolved issues at the moment |
| 10:42 | <annevk> | tobie: it's not entirely clear how to resolve them and nobody seems super keen on doing the work |
| 10:42 | <tobie> | annevk: right-- |
| 10:43 | <tobie> | it's interesting because nodejs seems to implement a browser-like event loop system with tasks and microtasks (though I should check) |
| 11:31 | <annevk> | MikeSmith: any idea why https://github.com/whatwg/html/search?l=html doesn't list "source" and why there's still a .inc file listed as PHP? |
| 11:52 | <annevk> | jgraham: reviewable still seems enabled? https://github.com/w3c/web-platform-tests/pull/2356 |
| 11:52 | <annevk> | jgraham: https://github.com/w3c/web-platform-tests/pull/2329 currently looks not okay due to reviewable, while I did address all the feedback |
| 11:52 | <annevk> | jgraham: I just don't want to create yet another account |
| 11:54 | <jgraham> | annevk: reviewable uses your GH account |
| 11:54 | <jgraham> | But I will try to disable it |
| 11:55 | <jgraham> | It seems to be disabled for new PRs |
| 11:56 | <annevk> | jgraham: well I just created that PR |
| 11:56 | <annevk> | 8 minutes ago that is |
| 11:57 | <jgraham> | OK I also removed the webhook |
| 11:57 | <jgraham> | Pretty sure that's a bug in reviewable |
| 12:02 | <mkwst> | Reviewable looks great, but it requested write access to my repositories. I'd prefer that not be required to submit tests. :) |
| 12:12 | <nox> | mkwst: I'm not seeing this. |
| 12:12 | <nox> | https://usercontent.irccloud-cdn.com/file/uTe9h3Am/Capture%20d%E2%80%99e%CC%81cran%202015-11-18%20a%CC%80%2013.12.28.png |
| 12:12 | <nox> | mkwst: ^ |
| 12:14 | <mkwst> | nox: Click publish after adding a comment. |
| 12:15 | <mkwst> | That ends up asking me for write permissions to repositories. |
| 12:15 | <mkwst> | See the first answer on https://github.com/Reviewable/Reviewable/wiki/FAQ :) |
| 12:16 | <mkwst> | Totally reasonable explanation (GitHub's permissions aren't granular enough). But still. |
| 12:24 | <nox> | Oh I see. |
| 12:24 | <nox> | GitHub's permissions generally suck, yeah. |
| 12:29 | <roc> | I'm glad I'm not the only one who noticed that |
| 12:30 | <roc> | I wanted to give an application push access to one specific repository under my account with an API key, but that seems to be impossible. You can only create API keys that have write access to *all* repos your account can write to. |
| 13:05 | <philipj> | roc: I think I did that when I maintained the html-mirror repo, using a deploy key |
| 13:06 | <Ms2ger> | roc, there's an easy solution, but it involves creating a new account :) |
| 13:06 | <philipj> | is that what you've tried, or are you all talking about something else? |
| 13:07 | <philipj> | oh, applications..., yeah that's something completely different |
| 13:07 | <MikeSmith> | > annevk: MikeSmith: any idea why https://github.com/whatwg/html/search?l=html doesn't list "source" and why there's still a .inc file listed as PHP? |
| 13:07 | <MikeSmith> | no idea |
| 13:08 | <MikeSmith> | I'm not sure how to control the behavior |
| 13:08 | <MikeSmith> | I don't know if the .gitattributes file affects that |
| 13:09 | <roc> | Ms2ger: yeah. that's horrible :-) |
| 13:12 | <roc> | While you github fans are here: if I want to have HTML-format documentation checked in alongside the code in a project, but I also want to have the latest checkout of that documentation available on the Web, what are my options? |
| 13:13 | <Ms2ger> | You can have travis publish to another git repo and use gh-pages |
| 13:13 | <Ms2ger> | That's how https://servo.github.io/rust-cssparser/cssparser/index.html works |
| 13:14 | <philipj> | roc: If you want to publish it on your own domain or something, a webhook that just pulls the latest into your ~/www or similar works too |
| 13:14 | <Ms2ger> | (Except that it pushes to a branch in the same repo for some reason) |
| 13:14 | <roc> | ick |
| 13:14 | <roc> | ok |
| 14:01 | <annevk> | roc: most WHATWG specifications are published by a commit-hook that just fetches a zip from the GitHub repository and publishes it |
| 17:59 | <smaug____> | annevk: want to do a sanity check? push/replaceState https://html.spec.whatwg.org/multipage/browsers.html#dom-history-pushstate don't seem to care at all whether the current entry is actually for the document for which the history object was created. I mean a case when one takes a reference to a history object and then navigates browser context to some other page, yet uses the old history object |
| 17:59 | <smaug____> | maybe I'm missing something here |
| 18:32 | <gsnedders> | Hixie_: yer site's down |
| 18:40 | <tantek> | gsnedders: I thought he was on G+ now |
| 18:41 | gsnedders | has no idea what the best way to prod him is now :) |
| 18:45 | <Domenic> | So in the spirit of the topic... is there a spec for navigator.javaEnabled? |
| 18:45 | <Domenic> | I guess I should check the html spec instead of just google... it'll be embarassing if it's there |
| 18:46 | <Domenic> | OK it does exist in the spec but is an attribute not a property |
| 18:46 | <Domenic> | s/property/method |
| 18:48 | <Hixie_> | whatwg.org just got updated to a newer distro |
| 18:49 | <Hixie_> | let me know if anything broke |
| 20:30 | <gsnedders> | ergh. feeling like I have to use sync xhr. :( |
| 20:31 | <gsnedders> | tl;dr: need to open a pop-up conditionally, depending on the result from an XHR request |
| 20:31 | <gsnedders> | and I can't use async XHR because then it's not a user-initiated window.open call |
| 20:31 | <gsnedders> | I suppose I could always open an about:blank popup and then close it depending on the XHR response, but that seems like a poor work-around |
| 20:32 | <gsnedders> | or just reimplement popups using an iframe and position absolute… |
| 20:32 | <gsnedders> | suggestions, anyone? |
| 21:30 | <darobin> | gsnedders: can you maybe do the XHR call before the user clicks? get the data in advance |
| 21:31 | <darobin> | otherwise, yeah, go with a modal+iframe |
| 21:33 | <gsnedders> | nah, an iframe is a bad idea actually, given no browser chrome to give URL + security status, bah |
| 21:33 | <gsnedders> | guess just doing a probably pointless XHR call is best |
| 21:46 | <caitp> | is there any reason why an iframe couldn't display security status? |
| 21:46 | <caitp> | like a little overlayed frowny face |
| 21:47 | <roc> | compat |
| 21:50 | <caitp> | if it's a potential phishing attack, the compat issue is probably second to the phishing issue |
| 21:52 | <zcorpan> | if we identify a phishing attack, don't we basically block the page? |
| 21:52 | <caitp> | ideally |
| 21:54 | <caitp> | or, the security advisory could show up outside of the iframe when you tried to interact with it |
| 21:54 | <caitp> | i'm sure there are clever ways around that issue |
| 21:58 | <bblfish> | annevk: is there a way to reduce the number of connections when using CORS? My server connects with a GET to remote resource. I think it 1) makes an OPTIONS request. This 2) returns a GET with a 401 and then 3) one gets the result |
| 21:59 | <gsnedders> | is there anyway to find declarations with a given selector in CSSOM easily? |
| 21:59 | <gsnedders> | like, better than just iterating through the entire Stylesheet? |
| 22:13 | <smaug____> | session history... hopeless |
| 23:06 | <smaug____> | so hopeless |
| 23:07 | <smaug____> | can we remove it from the platform ? :) |
| 23:07 | <zcorpan> | gsnedders: no :-( |
| 23:07 | <zcorpan> | smaug____: no :-( |
| 23:07 | <zcorpan> | we suck |
| 23:08 | <zcorpan> | smaug____: is there a problem with specifying no-op for non-active documents' history? |
| 23:09 | <smaug____> | this time I'm actually looking at the recent scroll restoration mode |
| 23:10 | <smaug____> | which is defined to do something, and that something isn't defined |
| 23:10 | <smaug____> | so actually, it isn't defined to do anything :) |
| 23:11 | <zcorpan> | very well then |
| 23:15 | <zcorpan> | smaug____: i think the spec was equally hand-wavy about scroll restoration before there was an api to turn it off |
| 23:16 | <smaug____> | that is true, but now I need to figure out what to actually turn off |
| 23:18 | <zcorpan> | yeah.. and i suppose if we want interop in this area, we should spec it better |
