Closed Bug 1509346 Opened 6 years ago Closed 1 year ago

Add support for <form rel>

Categories

(Core :: DOM: Forms, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
relnote-firefox --- 111+
firefox111 --- fixed

People

(Reporter: ehsan.akhgari, Assigned: avandolder)

References

(Blocks 2 open bugs)

Details

(4 keywords)

Attachments

(1 file)

In a similar fashion to bug 1503681, we would like to experiment with breaking opener references for pages opened via form navigations.

On the related dev-platform thread, I said this about the spec side of things:
...it's impossible to block opener reference creation upon form submission right now as far as I can tell.  This is actually a bug in the spec.  <https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-submission-algorithm:the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name> calls into "rules for choosing a browsing context" passing only two arguments, omitting the third one (noopener) <https://html.spec.whatwg.org/multipage/browsers.html#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>.

The web compat risk here is unknown so it may make sense to land a pref that we can turn on first on Nightly and take things from there.
Flags: needinfo?(amarchesini)
Might require some docs updates somewhere along the line.
Keywords: dev-doc-needed
Keywords: site-compat

https://github.com/whatwg/html/pull/4332 details changes to the HTML Standard for this. Note that it also adds the rel content/IDL attribute and the relList IDL attribute, as well as support for noopener, noreferrer, and opener, for full parity with <a> and <area>.

Summary: Make <form target="_blank"> imply noopener behaviour → Add support for <form rel>
Component: HTML: Form Submission → DOM: Core & HTML
Priority: -- → P2
Severity: normal → --
Component: DOM: Core & HTML → DOM: Forms
Flags: needinfo?(amarchesini)
Keywords: parity-safari
Webcompat Priority: --- → ?

There is no signal on real websites.

Webcompat Priority: ? → ---
Assignee: nobody → avandolder
Status: NEW → ASSIGNED

Ah, I missed that test. Hopefully I have them all now.

Flags: needinfo?(avandolder)
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch

Release Note Request (optional, but appreciated)
[Why is this notable]: Allows use of previously unsupported standard attribute.
[Affects Firefox for Android]: n/a
[Suggested wording]:
[Links (documentation, blog post, etc)]:

relnote-firefox: --- → ?

Please provide some suggested wording you would like for this note.
I'll add it to the 111 nightly notes and it will follow through to 111 beta and 111 release.

Flags: needinfo?(avandolder)

[Suggested wording]: Use of the rel attribute is now supported on form elements, allowing the specification of the relationship between the current document and the form target in a simpler, cross-browser way.

Flags: needinfo?(avandolder)

Thanks, added to Nightly release notes.
Keeping the relnote? flag open to keep it on the radar for inclusion in our final release notes.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: