Closed Bug 1457047 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 10645 - Update webidl2.js to v10.2.1

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox61 fixed)

RESOLVED FIXED
mozilla61
Tracking Status
firefox61 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 10645 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/10645 Details from upstream follow. Chris Nardi <christopherncarmel@hotmail.com> wrote: > Update webidl2.js to v10.2.1 > > This was created by: > > ``` > git revert 280005efe04503f14891d73c6ceab1077a59a735 > git subtree pull --prefix=resources/webidl2 https://github.com/w3c/webidl2.js.git v10.2.1 --squash > ``` > > and then making the merge commit have a reasonable commit message. @gsnedders does this look right? > > Main motivation for this update is pulling in https://github.com/w3c/webidl2.js/pull/139, which has the potential to result in performance improvements for IDL tests. > > Note that 280005efe04503f14891d73c6ceab1077a59a735 was reverted as upstream changes in https://github.com/w3c/webidl2.js/pull/139 should have made effectively the same change (and created a merge conflict); the fix was reported to work in Servo. > > This **should not be merged** as of yet -- I think I did this right per https://github.com/w3c/web-platform-tests/pull/8063#issuecomment-341887244, but I need someone to sanity check me first so it doesn't mess anything up. This also cannot be squashed & rebased, it needs a pure merge.
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/21a5a8d11df3 [wpt PR 10645] - Update webidl2.js to v10.2.1, a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in before you can comment on or make changes to this bug.