-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
<form method="dialog">
should probably not check for noopener
#8499
Comments
cc @whatwg/forms too |
Edit: this analysis was incorrect. The problem is that we end up creating a top-level navigable we don't need. |
Seems good to me. So this would consist of moving what is currently steps 16 and 23 up to after step 9, I think? That is, we still want to:
But we do not want to:
Would you be up for writing a spec PR and tests PR covering these? |
Presumably we just have to move
up? Makes sense to ignore action parsing as well. (Ideally we'd not have "jump", but that's a bit more effort.) |
Right, that's step 23; step 16 is establishing the value of method. |
Sounds good to me. Based on what I'm reading in chromium it seems like this is what we are already doing. |
Looks reasonable. @avandolder |
Yeah, this should also line up with how Gecko already handles submissions - we check for dialog before handling rel values. |
Also refactor "submit dialog", "close the dialog", and their callers. Note that removing the open attribute check is safe as "close the dialog" also handles that. Tests: ... Fixes #8499.
FYI, I ended up finding a "bug" in Gecko. It takes the form's action into account. Bug linked from the PR. |
Also refactor "submit dialog", "close the dialog", and their callers. Note that removing the open attribute check is safe as "close the dialog" also handles that. Tests: web-platform-tests/wpt#38819. Fixes #8499.
According to the spec, we should be checking for the
noopener
, and then skip to the dialog steps.https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-submission-algorithm:get-an-element's-noopener
I think it probably makes sense to skip to the dialog steps earlier, before we even do any navigation checks, given
form[method=dialog]
does not involve any navigation.cc @domenic @annevk
The text was updated successfully, but these errors were encountered: