-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec bug: What happens with a g,C
mapping?
#181
Comments
Chrome DevTools will throw an error nowadays: https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/core/sdk/SourceMap.ts;l=816;drc=6ca4ad9f4aac1de91c8b5095b8fdb558ad9e7c5e Before 2024 it would silently ignore it and treat This would effectively treat |
Nitpicking, but it's impossible to hit We can encounter an incomplete |
If it's at the end of the mappings, it'll turn into I don't specifically handle it at all 😬. Sourcemaps are machine generated, and I don't wanna slow down everyone for handwritten validation. |
Even including #179, I think our spec is just broken in this case. In https://tc39.es/ecma426/#sec-DecodeBase64VLQ we consume
g
, then the loop continues and it callsConsumeBase64ValueAt
, which tries to decode,
as a base64 value.#180 fixes it by making it an error explicitly, but I'm opening this issue to make sure it's tested.
What do realm implementations do? Do they error, or do they recover by just assuming that the user meant
A
instead ofg
(which is the same bit pattern but without the continuation bit)?The text was updated successfully, but these errors were encountered: