Skip to content
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

What happens when an implementation-defined limit is reached? #523

Open
annevk opened this issue Jan 16, 2023 · 0 comments
Open

What happens when an implementation-defined limit is reached? #523

annevk opened this issue Jan 16, 2023 · 0 comments

Comments

@annevk
Copy link
Member

annevk commented Jan 16, 2023

Typically this is not defined, in part because editors are not always aware limits might be in play and in part because they do not want to constrain implementation choices. But there is something to be said that if implementations choose the same strategy, they should behave in the same way.

E.g., if implementations decide to throw an exception if an input is larger than X bytes, perhaps the exception should at least be the same, even if X is not.

There is some precedent for this: RangeError exception for ArrayBuffer object allocation. But at the same time JavaScript doesn't deal with any of the other out-of-memory situations, thereby allowing for exceptions, crashing the process, no-opping, or some other behavior.

I'm not sure what is best here. For out-of-memory a process crash seems quite clean, but we're not at a process-per-origin yet so it's not that clean.

annevk added a commit that referenced this issue Jan 16, 2023
Part of the wording is adopted from the HTML Standard.

Follow-up: #523.

Co-authored-by: Domenic Denicola <d@domenic.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant