-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Use "entry" and "entry list" defined in XHR #3676
Comments
The benefit is to consolidate multiple concepts representing same thing into one. |
It should probably define its own "entry list" concept as that one is effectively the internal slot of a |
@annevk I think it's safe to use the same "entry list" because a |
I just don't understand how you can use it, since "entry list" as defined is an internal slot of |
- Replace "form data set" with "entry list" - Use "File" interface for entry values Fixes whatwg#3676
- Replace "form data set" with "entry list" - Use "File" interface for entry values Fixes whatwg#3676
- Replace "form data set" with "entry list" - Use "File" interface for entry values Fixes whatwg#3676
- Replace "form data set" with "entry list" - Use "File" interface for entry values Fixes whatwg#3676
- Replace "form data set" with "entry list" - Use "File" interface for entry values Fixes whatwg#3676
Also use File objects for entry values rather than an abstraction. Corresponding XMLHttpRequest Standard change: whatwg/xhr#210. Fixes part of #3676.
Also use File objects for entry values rather than an abstraction. Corresponding XMLHttpRequest Standard change: whatwg/xhr#210. Fixes part of whatwg#3676.
HTML specification should use entry and entry list instead of "name-value tuple" and "form data set"
The text was updated successfully, but these errors were encountered: