| 08:08 | <mkwst> | annevk: https://chromium-review.googlesource.com/c/chromium/src/+/2003311. |
| 08:19 | <annevk> | mkwst: thanks, makes sense it was something like that |
| 08:21 | <annevk> | Still gotta write some javascript: URL tests to confirm how inheritance works I guess |
| 08:22 | <mkwst> | Yeah, sorry for the mixup. We try to be good about maintaining tests, but this was clearly our fault. |
| 08:23 | <mkwst> | Hopefully `javascript:` will be the same as `about:srcdoc`, which is tested. |
| 08:37 | <annevk> | mkwst: javascript: has a source and a target, so there are different scenarios there |
| 08:37 | <annevk> | and I thought the hope is that it reuses target's stuff somehow? |
| 08:38 | <annevk> | anyway, gotta test |
| 10:03 | <yhirano> | annevk: is the client for a top-level navigation request set? Is it set to the previous document? |
| 10:08 | <annevk> | yhirano: I don't think it should be set if the user enters the address |
| 10:08 | <annevk> | yhirano: but none of that is well defined at the moment |
| 10:09 | <yhirano> | how about the case where the user clicks a link? |
| 10:31 | <annevk> | yhirano: in that case you need a client for referrer computation |
| 10:46 | <yhirano> | annevk: thank you |
| 13:15 | <annevk> | TabAtkins: https://github.com/tabatkins/bikeshed/pull/1587 |
| 14:36 | <mathiasbynens> | in which hsivonen beautifully describes 3 distinct scenarios in which Firefox reloads due to late or missing <meta charset>: https://github.com/GoogleChrome/lighthouse/issues/10023#issuecomment-575129051 |
| 16:21 | <botie> | bkardell, at 2019-06-19 04:15 UTC, MikeSmith said: congrats on joining Igalia |
| 18:52 | <Bakkot> | is there a way to ping people re: https://github.com/whatwg/html/issues/5102 short of just bumping the issue? @mkwst maybe? I'm trying to update Salvation (a library for working with CSPs) and stuff like this issue is making it hard to know what the right behavior to implement is. |
| 18:55 | <Bakkot> | (also is there a good channel for discussion of CSPs in general?) |
| 19:33 | <Domenic> | Bakkot: I think you've done all the pinging I could think of, except maybe emailing public-webappsec⊙wo? |
| 19:33 | <Domenic> | What we ideally would get here is Safari/Chrome/Firefox's opinion how strongly each feels about their current behavior. Absent any such signals, we should update the spec to match the majority. |
| 19:50 | <Bakkot> | neat, thanks Domenic. |
| 20:17 | <bathos> | Regarding "Other specifications can also define body-ok keywords." in https://html.spec.whatwg.org/multipage/links.html#linkTypes, is there an authoritative list of these externally defined tokens or a way to search for them? One I know of is "manifest" (https://w3c.github.io/manifest/#linking) but I’m unsure if there are others. |
| 20:25 | <annevk> | bathos: no, and these days I suspect we’d favor inlining it all, if any are defined externally |
| 20:30 | <bathos> | yeah, extension points are tricky unless they involve a very search-friendly term (e.g. imo that’s why stuff like "HostEnsureCanCompileStrings" works okay — it’s unambiguous what you’re looking for). I was able to find this at least: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/tests/html/semantics/rellist-feature-detection.html#9-15 |
| 20:31 | <bathos> | so at least in moz, the only acknowledged tokens not appearing in HTML appear to be "manifest", "apple-touch-icon", and "apple-touch-icon-precomposed" |
| 20:31 | <bathos> | oh and "bookmark", which is in HTML but disallowed on <link> |
| 20:35 | <TabAtkins> | annevk: Thanks, I'd missed your comment that deps had landed. |
| 21:16 | <MikeSmith> | Bakkot: yeah I’d also like to see that issue get resolved |