| 00:05 | <gsnedders> | <meta http-equiv="Refresh" content="20; URL=page4.html"> when loaded at page1.html#foobar doesn't preserve the fragment, does it? (c.f. behaviour of the Location header on HTTP 3xx) |
| 00:08 | <gsnedders> | MikeSmith: WHY IS THAT IN MO SPACE?! |
| 00:10 | <MikeSmith> | 😕 |
| 00:10 | <MikeSmith> | oh MO = member only |
| 00:10 | <MikeSmith> | damn |
| 00:10 | <MikeSmith> | they should no even be using that list |
| 00:11 | <gsnedders> | like I can just about deal with sending an email saying "here's the connection details for the next telecon" in MO space, but everything else :grimmace: |
| 00:11 | <MikeSmith> | even weirder, there isn’t even a working group for the GPU work yet |
| 00:11 | <gsnedders> | I mean it's a CG right? |
| 00:11 | <MikeSmith> | yeah |
| 00:12 | <MikeSmith> | so that list should not even exist to begin with |
| 00:12 | <gsnedders> | a few CGs have group-only lists which are implemented as Member+group |
| 00:12 | <MikeSmith> | ah |
| 00:12 | <MikeSmith> | well that doesn’t seem so great |
| 00:12 | <gsnedders> | it may even be part of the default setup? |
| 00:12 | <MikeSmith> | yeah it would have to be I guess |
| 00:12 | <gsnedders> | https://lists.w3.org/Archives/Member/ looks like every CG does? |
| 00:12 | MikeSmith | looks |
| 00:12 | <MikeSmith> | sigh |
| 00:13 | <MikeSmith> | not good |
| 00:13 | <MikeSmith> | まずい |
| 00:13 | <gsnedders> | what guidelines do we give CG contributors? do we give any indiciation as to when which ML shoudl be used? |
| 00:13 | <MikeSmith> | I would hope so |
| 00:13 | <MikeSmith> | I will look |
| 00:14 | <gsnedders> | sorry if I seem snarky |
| 00:14 | <gsnedders> | but you know I always am about anything technical in MO space, and soemwhat snarky about admin stuff in MO space |
| 00:15 | <MikeSmith> | yeah as you should be |
| 00:15 | <MikeSmith> | as everybody should be |
| 00:15 | <MikeSmith> | https://www.w3.org/community/about/tool/#lists |
| 00:15 | <MikeSmith> | > Each group has three mailing lists by default |
| 00:15 | <MikeSmith> | problem number 1... |
| 00:15 | <MikeSmith> | > Community Groups must only use this list for administrative matters. |
| 00:16 | <MikeSmith> | I think maybe the internal-mygroup⊙wo list was originally intended only for discussions about patent-related stuff for CG’s specs |
| 00:17 | <MikeSmith> | ah well |
| 00:18 | <MikeSmith> | gsnedders: I hope you or somebody other than many has the psychic energy free to start a discussion somewhere asking for this to be fixed |
| 00:18 | <MikeSmith> | *you or somebody other than *me* |
| 00:19 | <MikeSmith> | (I sometimes like to refer to myself in the third person as “many” |
| 00:21 | <gsnedders> | I really don't have the energy to fight it when I'm not even paid to do anything outside of the CSS WG |
| 00:26 | MikeSmith | hands gsnedders some https://www.youtube.com/watch?v=mi1DUsfSH5Y to listen to |
| 17:03 | <annevk> | Domenic: Canary? |
| 17:05 | <annevk> | Domenic: seems really weird that macOS has hosts and Windows does not, but what do I know |
| 17:05 | <Domenic> | annevk: yep. Looks like sleevi's looking at it too... in general it's a known issue that Chromium has divergent URL parsing on different OSes. |
| 17:56 | <annevk> | Sounds like I need to get a BrowserStack account again |
| 17:57 | <annevk> | I'm a little worried Live URL Viewer might break down in IE6 though |
| 17:57 | <Domenic> | It breaks down in IE11 |
| 17:57 | <annevk> | good times |
| 17:57 | <Domenic> | Back to <base> and <a> tests I guess |
| 17:58 | <Domenic> | I guess thankfully <base> isn't necessary for the case in question |
| 18:01 | <Bakkot> | > Chromium has divergent URL parsing on different OSes |
| 18:01 | <Bakkot> | wait what |
| 18:01 | <Bakkot> | is there an issue for that somewhere? |
| 18:05 | <Domenic> | I could swear there was, but I'm not finding it |
| 18:05 | <Domenic> | https://source.chromium.org/chromium/chromium/src/+/master:url/url_parse_file.cc;l=68;drc=0e223687cb484dd52c99a56813eaa2e142e9263a?originalUrl=https:%2F%2Fcs.chromium.org%2F anyway |
| 18:07 | <Bakkot> | neat, thanks |
| 18:09 | <annevk> | There are more general bugs on aligning Chromium with the URL parser though they mostly get activity from silly bots |
| 18:10 | annevk | takes a peek at registerProtocolHandler() |
| 18:16 | <Domenic> | As I search for this bug I'm adding more blocking bugs to https://bugs.chromium.org/p/chromium/issues/detail?id=660384 |
| 18:29 | <annevk> | Thanks! |
| 18:30 | <annevk> | So registerProtocolHandler() is messy and https://github.com/whatwg/html/issues/481 is very much a thing in Firefox at least. |
| 18:30 | <annevk> | It seems to block navigating to a registered scheme for a fair number of code points, even if they end up percent-encoded. |
| 18:32 | <Domenic> | I was hoping you'd finish up your registerProtocolHandler() cleanup PR at some point |
| 18:33 | <Domenic> | But I guess you're gesturing at deeper problems. https://github.com/whatwg/html/issues/3377 is informative. |
| 18:34 | <annevk> | Yeah, I was looking at that and then found out what I thought was a non-issue is an issue too. |
| 18:34 | <annevk> | Well, or Firefox has a bug. Will look a bit more tomorrow. |
| 21:35 | <saber1> | Domenic: ping |