77882 2012-02-06 10:16:52 -0800 IETC compareDocumentPosition2 test case fails in WebKit 2022-09-02 14:32:22 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 76198 1 eric webkit-unassigned abarth ahmad.saleem792 ap cdumez loic.yhuel olivier.blin rniwa oldest_to_newest 550082 0 eric 2012-02-06 10:16:52 -0800 IETC compareDocumentPosition2 test case fails in WebKit http://samples.msdn.microsoft.com/ietestcenter/domcore/showdomcoretest.htm?Node_compareDocumentPosition2 According to the spreadsheet, I think abarth had planned to take a look. 550251 1 eric 2012-02-06 13:37:27 -0800 http://samples.msdn.microsoft.com/ietestcenter/domcore/Node_compareDocumentPosition2.htm is a better URL. 820395 2 ap 2013-01-30 12:08:14 -0800 See also: bug 108274. 957262 3 olivier.blin 2013-12-06 09:28:20 -0800 This has been fixed by r153660. See bug 119316 - compareDocumentPosition() should report PRECEDING or FOLLOWING information even if nodes are disconnected 985883 4 ap 2014-02-28 22:42:59 -0800 That change is about to be reverted though. 1502932 5 lforschler 2019-02-06 09:03:14 -0800 Mass moving XML DOM bugs to the "DOM" Component. 1895869 6 ahmad.saleem792 2022-09-02 14:32:22 -0700 Safari Technology Preview 152 pass all of these cases as per WPT: https://wpt.fyi/results/dom/nodes/Node-compareDocumentPosition.html?label=experimental&label=master&aligned Marking this as "RESOLVED CONFIGURATION CHANGED". Thanks!