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

Address limits on unconstrained inputs #520

Merged
merged 7 commits into from
Jan 16, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Address limits on unconstrained inputs
The second half of this paragraph is from the HTML Standard.
annevk committed Jan 9, 2023

Verified

This commit was signed with the committer’s verified signature.
Nothing4You Richard Schwab
commit 5c28a2d94fcaadcd22d7c9ab852398d737f6695d
8 changes: 8 additions & 0 deletions infra.bs
Original file line number Diff line number Diff line change
@@ -239,6 +239,13 @@ paths would be an insurmountable task and not productive as they would not stand
as well as the single algorithm would. Therefore performance is best left as a field to compete
over.

<p>A document using the Infra Standard should not enforce specific limits on unconstrained inputs to
allow for competition among user agents and foster ever greater data structures over time. I.e.,
avoid constraining the computing needs of the future. Nevertheless, user agents may impose
<a>implementation-defined</a> limits on otherwise unconstrained inputs. E.g., to prevent denial of
service attacks, to guard against running out of memory, or to work around platform-specific
limitations.


<h3 id=algorithm-declaration>Declaration</h3>

@@ -1995,6 +2002,7 @@ Chris Rebert,
Daniel Ehrenberg,
Dominic Farolino,
Gabriel Pivovarov,
Ian Hickson,
Jake Archibald,
Jeff Hodges,
Jungkee Song,