[wpt-sync] Sync PR 15711 - Eliminated remaining uses of [LegacyInterfaceTypeChecking]

RESOLVED FIXED in Firefox 68

Status

()

enhancement
P4
normal
RESOLVED FIXED
5 months ago
4 months ago

People

(Reporter: wptsync, Unassigned)

Tracking

unspecified
mozilla68
Points:
---

Firefox Tracking Flags

(firefox68 fixed)

Details

(Whiteboard: [wptsync downstream], )

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

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

Allison Pastewka <alpastew@microsoft.com> wrote:

Eliminated remaining uses of [LegacyInterfaceTypeChecking]

Removed [LegacyInterfaceTypeChecking] from the two remaining idls,
RTCPeerConnection-getStats and FormData. Updated the relevant tests to
match the new behavior.

Seeing as how [LegacyInterfaceTypeChecking] is no longer being used,
I removed the extended attribute from IDLExtendedAttributes.md and
IDLExtendedAttributes.txt.

Bug: 561338
Change-Id: I4783348f485932f08c86ddb58efb6cb713fd5fe4
Reviewed-on: https://chromium-review.googlesource.com/1507237
WPT-Export-Revision: 9d9a6aea3711cbf081a6fd4187a3643aeb60c0eb

Component: web-platform-tests → DOM
Product: Testing → Core
Component: DOM → DOM: Core & HTML
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/187083290779
[wpt PR 15711] - Eliminated remaining uses of [LegacyInterfaceTypeChecking], a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5de1d58de3d2
[wpt PR 15711] - Eliminated remaining uses of [LegacyInterfaceTypeChecking], a=testonly
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.