| 08:00 | <raintrap_> | hey guys. I wanted to test my site in a different version of Safari. Is there like a platform or tool which I could use without installing multiple versions of Safari in my machine? Thanks! |
| 09:46 | <mkwst> | annevk: I've started spelling out the fetch implications of priming in a bit more detail: https://mikewest.github.io/hsts-priming/#modifications-fetch-main Suggestions welcome. |
| 09:46 | <mkwst> | annevk: agl didn't seem to hate it. |
| 14:08 | <annevk> | mkwst: great success |
| 14:11 | <annevk> | mkwst: that looks pretty good |
| 14:11 | <annevk> | mkwst: thank you |
| 14:12 | <mkwst> | annevk: I figure we throw this to the wolves, and once there's some agreement, you or Richard or I can turn it into a set of patches against Fetch. |
| 14:12 | <mkwst> | annevk: And I guess I'll try to get Jeff interested in updating the RFC to give Fetch some hooks. |
| 14:25 | <annevk> | mkwst: that sounds good |
| 14:26 | <annevk> | mkwst: might do some bikeshedding at that point, but for a discussion this seems good |
| 14:27 | <mkwst> | Yeah, I don't plan on nailing everything down. This is a quick first pass to have something concrete to argue about. |
| 14:56 | <zcorpan> | https://github.com/w3c/webvtt/pull/246 |
| 15:07 | <annevk> | I like how zcorpan employs the IRC equivalent of "drops mic" |
| 15:43 | <annevk> | JakeA: any opinions on https://github.com/whatwg/fetch/issues/40? |
| 15:45 | <wanderview> | annevk: that means "from http cache", right? or also Cache API? |
| 15:45 | <annevk> | wanderview: just HTTP |
| 15:46 | <annevk> | wanderview: perhaps we should rename the RequestOptions cache httpCache? |
| 15:46 | <annevk> | wanderview: and this fromHTTPCache? |
| 15:46 | <annevk> | hmm |
| 15:46 | <annevk> | I guess it's clear enough |
| 15:46 | <wanderview> | annevk: not sure... I don't like those |
| 15:47 | <wanderview> | annevk: I guess Response is standalone and Cache API is another layer... makes sense they are unrelated... but I could see it confusing people |
| 15:47 | <annevk> | yeah me neither, and we don't prefix lots of other HTTP stuff with HTTP either |
| 15:47 | <JakeA> | annevk: I'm not sure what I'd use it for |
| 15:47 | <wanderview> | annevk: lets rename Cache API to FetchStore again :-) |
| 15:48 | <JakeA> | Boooo |
| 15:48 | <annevk> | That would have been a lot better name given that it's not actually a cache |
| 15:51 | <annevk> | JakeA: https://github.com/slightlyoff/ServiceWorker/issues/412#issuecomment-57635369 is the argument for this addition, but I haven't really hard anyone ask for it so maybe we should not do it |
| 16:00 | <annevk> | So confusing how code.google.com redirects to you to the issues overview after adding a comment to an issue |
| 16:01 | <wanderview> | annevk: bugzilla does the same, no? |
| 16:01 | <caitp> | there's a setting |
| 16:01 | <annevk> | wanderview: yeah, Bugzilla often shows the same bug for me, sometimes the next one in a listing |
| 16:02 | <annevk> | s/yeah, // |
| 16:03 | <caitp> | there used to be a setting, huh |
| 16:03 | <caitp> | i guess there still is, it just doesn't get saved to your profile? weird |
| 16:04 | <caitp> | https://www.dropbox.com/s/0hata33lawvez1c/Screen%20Shot%202015-11-06%20at%2011.04.04%20AM.png?dl=0 << that thing, unless you don't get that option normally |
| 16:08 | <annevk> | interesting |
| 16:48 | <mkwst> | annevk: you'll be thrilled to know that code.google.com is dying, and we're building a whole new bug tracker for crbug.com! |
| 16:48 | <mkwst> | annevk: I'm sure that will be a wonderful experience for everyone. |
| 17:06 | <annevk> | mkwst: hmm so maybe change noopener link attribute to 'noopener' <link rel> keyword? |
| 17:06 | <annevk> | mkwst: in the commit message |
| 17:07 | <mkwst> | annevk: Sure. Pushed. |
| 17:08 | <annevk> | mkwst: also, the link syntax looks wrong per https://daringfireball.net/projects/markdown/syntax#link though maybe GitHub does something else |
| 17:08 | <annevk> | oooh cool |
| 17:08 | <annevk> | he switched to HTTPS |
| 17:09 | <mkwst> | Ha, yeah. I don't actually use the inline syntax. I'll fix it. |
| 17:09 | <annevk> | no HSTS yet |
| 17:10 | <mkwst> | annevk: I'm not getting redirected. I suspect you're using HTTPS Everywhere? |
| 17:10 | <mkwst> | (which is good) |
| 17:10 | <annevk> | I don't think so |
| 17:11 | <mkwst> | (pushed a fix to the markdown) |
| 17:11 | <annevk> | ooh |
| 17:11 | <annevk> | I think I found that link on Google |
| 17:11 | <annevk> | So Google might do some HTTPS Everywhere of sorts or just index both and rank this one higher |
| 17:12 | <annevk> | interesting |
| 17:12 | <mkwst> | That crazy Google. Who knows what it'll do next? |
| 17:12 | <annevk> | mkwst: you didn't confirm my question btw |
| 17:13 | <annevk> | mkwst: but I guess that means it's a yes, we still need to fix #313 |
| 17:15 | annevk | is gonna assume he got all that correct |
| 17:16 | <mkwst> | annevk: Yes. Sorry, there's probably some work to do there. |
| 17:16 | <mkwst> | At least we'll need to make "disowned its owner" actually clear out the owner browsing context. |
| 17:16 | <mkwst> | And probably other things that bz knows about that I don't. |
| 17:16 | <annevk> | mkwst: yeah, I think that's all there is to it |
| 17:17 | <annevk> | mkwst: plus perhaps a note that this turns it from an auxiliary browsing context into a top-level one |
| 17:18 | annevk | goes to file a bug against Gecko |
| 17:18 | <mkwst> | I think we may need to do more than that. "familiar with" seems a bit too loose, for example. |
| 17:19 | <mkwst> | but I'm kinda hoping that bz will spell out the things he'd like to see changed? :) |
| 17:20 | <annevk> | mkwst: my suggestion for the commit message was silly, should've been rel=noopener of course, <link> has nothing to do with it |
| 17:20 | annevk | blames the time |
| 17:20 | <annevk> | mkwst: familiar with just builds on it being auxiliary |
| 17:21 | <annevk> | mkwst: at least last time I probed bz that seemed to be it, but willing to be surprised |
| 17:21 | <mkwst> | Same origin as well. |
| 17:22 | <mkwst> | That is, if https://a.com nested in http://b.com opens https://a.com in a new window with 'noopener', I'd like it to be unfamiliar. |
| 17:22 | <mkwst> | (pushed another new commit message :) ) |
| 17:23 | <annevk> | mkwst: too late, already merged |
| 17:24 | <annevk> | mkwst: just noticed we need to change the IDL for window.open() too |
| 17:24 | <annevk> | mkwst: but I can do that |
| 17:24 | <mkwst> | CC me on the patch, just so I know what to do next time? |
| 17:27 | <annevk> | mkwst: https://github.com/whatwg/html/commit/1cf14758fda3d7c157c0a89334bd3bc0cad7686e |
| 17:28 | <mkwst> | annevk: Got it, thanks. |
