Editorial: Clarify multipart/form-data field name escaping ambiguity#12459
Open
yezhizhen wants to merge 1 commit into
Open
Editorial: Clarify multipart/form-data field name escaping ambiguity#12459yezhizhen wants to merge 1 commit into
multipart/form-data field name escaping ambiguity#12459yezhizhen wants to merge 1 commit into
Conversation
Signed-off-by: Euclid Ye <yezhizhenjiakang@gmail.com>
Author
|
cc @xiaochengh |
yezhizhen
changed the title
multipart/form-data field name escaping ambiguity
yezhizhen
changed the title
multipart/form-data field name escaping ambiguitymultipart/form-data field name escaping ambiguity
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While implementing this in Servo servo/servo#44943, the sentence looks ambiguous to me. I have to test and figure out whether non-file fields should also be escaped.
At least two implementers are interested (and none opposed):
Gecko, Chromium, Webkit already doing this
Tests are written and can be reviewed and commented upon at:
Covered by existing tests: see wpt.fyi for FileAPI.
Some of these should probably be moved to
html/semantics/formtest suites, but that is another story.The top of this comment includes a clear commit message to use.
(See WHATWG Working Mode: Changes for more details.)
/form-control-infrastructure.html ( diff )