Closed Bug 1576293 Opened 3 months ago Closed 3 months ago

[wpt-sync] Sync PR 17419 - Add tests for cases where a <base target> shouldn't apply

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 17419 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/17419
Details from upstream follow.

Nate Chapin <japhet@chromium.org> wrote:

Add tests for cases where a <base target> shouldn't apply

A base target attribute should only be considered when navigating via a, area, or form elements: https://html.spec.whatwg.org/multipage/semantics.html#get-an-element's-target

Chrome recently hit a couple of bugs where a base target attribute was incorrectly being applied to other navigations. There don't appear to be any tests for cases where the base target attribute should be ignored. This adds tests for navigation via iframe src and location assignment.

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 2 tests and 2 subtests
OK     : 2
PASS   : 2
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1614ca504f61
[wpt PR 17419] - Add tests for cases where a <base target> shouldn't apply, a=testonly
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.