Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Ambiguous wording in form submission leads to interop issue #11092

Copy link
Copy link
Closed
@lukewarlow

Description

@lukewarlow
Issue body actions

What is the issue with the HTML Standard?

See step 11.5 of https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#concept-form-submit
this as specced means that a submit button in a dialog form will always override the dialog's returnValue because a button always "has a value" (it's an empty string when missing the value attribute).

However, Chromium and WebKit implement this step as "has a value attribute" which is not the same thing.

I believe Chromium and WebKit implement this as would be expected and the spec should be updated to clarify (with tests added for this case).

Test Case: https://jsfiddle.net/wfhgc9yd/

Metadata

Metadata

Assignees

No one assigned

    Labels

    interopImplementations are not interoperable with each otherImplementations are not interoperable with each othertopic: dialogThe <dialog> elementThe <dialog> elementtopic: forms

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.