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

Use "entry" and "entry list" defined in XHR #3676

Closed
tkent-google opened this issue May 9, 2018 · 4 comments
Closed

Use "entry" and "entry list" defined in XHR #3676

tkent-google opened this issue May 9, 2018 · 4 comments
Labels
clarification Standard could be clearer topic: forms

Comments

@tkent-google
Copy link
Contributor

HTML specification should use entry and entry list instead of "name-value tuple" and "form data set"

@annevk annevk added clarification Standard could be clearer topic: forms labels May 9, 2018
@tkent-google
Copy link
Contributor Author

The benefit is to consolidate multiple concepts representing same thing into one.

@annevk
Copy link
Member

annevk commented May 9, 2018

It should probably define its own "entry list" concept as that one is effectively the internal slot of a FormData object. Unless you want to associate a FormData object with each form element?

@tkent-google
Copy link
Contributor Author

@annevk I think it's safe to use the same "entry list" because a form element doesn't need to keep a reference to an "entry list", and an "entry list" has no references to a form element.

@annevk
Copy link
Member

annevk commented May 14, 2018

I just don't understand how you can use it, since "entry list" as defined is an internal slot of FormData objects.

tkent-google added a commit to tkent-google/html that referenced this issue May 15, 2018
- Replace "form data set" with "entry list"
- Use "File" interface for entry values

Fixes whatwg#3676
annevk pushed a commit to tkent-google/html that referenced this issue May 18, 2018
- Replace "form data set" with "entry list"
- Use "File" interface for entry values

Fixes whatwg#3676
annevk pushed a commit to tkent-google/html that referenced this issue May 18, 2018
- Replace "form data set" with "entry list"
- Use "File" interface for entry values

Fixes whatwg#3676
annevk pushed a commit to tkent-google/html that referenced this issue May 25, 2018
- Replace "form data set" with "entry list"
- Use "File" interface for entry values

Fixes whatwg#3676
annevk pushed a commit to tkent-google/html that referenced this issue May 25, 2018
- Replace "form data set" with "entry list"
- Use "File" interface for entry values

Fixes whatwg#3676
annevk pushed a commit that referenced this issue May 25, 2018
Also use File objects for entry values rather than an abstraction.

Corresponding XMLHttpRequest Standard change: whatwg/xhr#210.

Fixes part of #3676.
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
Also use File objects for entry values rather than an abstraction.

Corresponding XMLHttpRequest Standard change: whatwg/xhr#210.

Fixes part of whatwg#3676.
Bishwarupjee pushed a commit to Bishwarupjee/xhr that referenced this issue Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: forms
Development

No branches or pull requests

2 participants