Move the "setRangeText should set dirty value flag" test into standard wpt

RESOLVED FIXED in Firefox 55

Status

()

Core
DOM
RESOLVED FIXED
8 months ago
8 months ago

People

(Reporter: bz, Assigned: bz)

Tracking

Trunk
mozilla55
Points:
---

Firefox Tracking Flags

(firefox55 fixed)

Details

Attachments

(1 attachment)

Spec change at https://github.com/whatwg/html/issues/2425 has come through, so we can upstream this test now.
Created attachment 8848260 [details] [diff] [review]
Move the test for setRangeText setting the dirty value flag into upstream wpt

MozReview-Commit-ID: 6yF42plMkAE
Attachment #8848260 - Flags: review?(bugs)
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED

Updated

8 months ago
Attachment #8848260 - Flags: review?(bugs) → review+

Comment 2

8 months ago
Pushed by bzbarsky@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7b89ee0ae420
Move the test for setRangeText setting the dirty value flag into upstream wpt.  r=smaug
Hey Boris,

it seems this cause merge conflicts when trying to merge mozilla-inbound to mozilla-central so i had to back this out. could you take a look ?
Flags: needinfo?(bzbarsky)

Comment 4

8 months ago
Backout by cbook@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/45fe96225142
Backed out changeset 7b89ee0ae420 for causing merge conflicts
wpt manifest strikes again.  :(  It's basically a landmine for anyone actually properly using the tools we have for updating it.  If someone else also uses those tools, they get automatic merge conflicts if someone else did NOT use those tools.
Flags: needinfo?(bzbarsky)

Comment 6

8 months ago
Pushed by bzbarsky@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1143fd4a40f5
Move the test for setRangeText setting the dirty value flag into upstream wpt.  r=smaug
https://hg.mozilla.org/mozilla-central/rev/1143fd4a40f5
Status: ASSIGNED → RESOLVED
Last Resolved: 8 months ago
status-firefox55: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.