88006 2012-05-31 13:50:36 -0700 [Win] fast/events/remove-target* tests fail 2019-02-06 09:18:44 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Windows 7 RESOLVED FIXED http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r119132%20(24326)/results.html LayoutTestFailure, Regression P2 Normal --- 1 jberlin webkit-unassigned adele jberlin jhoneycutt webkit-bug-importer oldest_to_newest 638688 0 jberlin 2012-05-31 13:50:36 -0700 Unfortunately, given the state of the Windows testers, I don't know when this started. fast/events/remove-target-in-mouseup-deep.html fast/events/remove-target-in-mouseup-insertback.html fast/events/remove-target-in-mouseup-twice.html fast/events/remove-target-in-mouseup.html fast/events/remove-target-with-shadow-in-drag.html I am going to land Windows-specific expected (failing?) results in order to get the bots green. One example of the failures: --- /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/events/remove-target-in-mouseup-deep-expected.txt 2012-05-31 12:54:00.555862500 -0700 +++ /home/buildbot/slave/win-release-tests/build/layout-test-results/fast/events/remove-target-in-mouseup-deep-actual.txt 2012-05-31 12:54:00.554862500 -0700 @@ -1,3 +1,3 @@ This test ensures WebKit does not fire click event on a node that has been removed in mouseup event. -PASS +click here 638696 1 jberlin 2012-05-31 13:59:19 -0700 Added Windows-specific expected (failing?) results in http://trac.webkit.org/changeset/119144 653038 2 jhoneycutt 2012-06-19 17:35:48 -0700 These tests now pass; removed the failing results in <http://trac.webkit.org/changeset/120766>. 1503234 3 lforschler 2019-02-06 09:18:44 -0800 Mass move bugs into the DOM component.