10:49
<annevk>
WorkerGlobalScope might have been impacted because JS engines didn't have other types of globals at the time, but not sure
14:10
<GPHemsley>
yall are not having nearly as much fun with this as I had hoped
14:15
<annevk>
GPHemsley: it was hard to come up with a joke-y reply and then someone started to take it seriously
14:16
<annevk>
GPHemsley: whatwg/encoding also somewhat routinely gets serious requests for stuff like this, which takes some of the fun out as well
14:25
<annevk>
GPHemsley: but hey, the page might get fixed, there's that ;-)
14:25
<GPHemsley>
:-P
14:27
<GPHemsley>
annevk: I do have some (more) serious archival-related concerns about changing the encoding of a historical document, though
14:28
<GPHemsley>
(mostly outside the scope of the WHATWG)
14:30
<GPHemsley>
side note, my original thought was to register an encoding with the IETF registry, but it seems that hasn't been updated since 2018
14:30
<annevk>
W3C keeps things in version control I think, but also, any such concerns should extend to the metadata, which likely has changed
14:31
<GPHemsley>
there was a relatively-recent working draft revision of the relevant RFC, but that seems to have been abandoned
14:31
<GPHemsley>
annevk: true
14:34
<annevk>
GPHemsley: pointer?
14:35
<annevk>
GPHemsley: the IANA registry is considered obsolete by the web
16:21
<andreubotella>
annevk: The changes in https://github.com/whatwg/html/pull/3276 related to percent-encoding don't seem to be tested, with Firefox not following them in at least some cases
16:25
<andreubotella>
oh, I missed https://github.com/web-platform-tests/wpt/pull/8618
16:27
<annevk>
andreubotella: it seems these did land in /FileAPI/file/
16:31
<andreubotella>
all I'm seeing in FileAPI/file is about making sure filenames effectively use encode
16:32
<annevk>
Oh okay
17:04
<GPHemsley>
from 2015: https://tools.ietf.org/html/draft-iana-charset-reg-procedure-01
17:04
<GPHemsley>
annevk: ^
17:05
<GPHemsley>
annevk: it appears the intent was to split the registry in categories such that it can continue to register legacy encodings
18:09
<annevk>
GPHemsley: ooh, yeah, I've seen that I think
18:09
<annevk>
GPHemsley: too little, too late