I have found that ALL of the compare methods of the range object fail if the range commonAncestorContainer is an Attr Node. The methods effected are: compareBoundaryPoints intersectsNode comparePoint isPointInRange compareNode - This is the only one that throws an exception I have wrote up a test case and am attaching it. Jeff Yates
thanks for the testcase!
Status: UNCONFIRMED → NEW
Ever confirmed: true
I believe that I have found the cause of this bug. All child nodes of an Attr node have there parentNode property set to null. See bug #73681. If someone could confirm that this is what is causing this problem I will mark it as a dependancy/blocker. Jeff Yates.
17 years ago
Depends on: 73681
I would suspect that this cannot get resolved at all until 73681 is resolved
setting to 0.9.2 anthonyd
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.2
Summary: Range compare methods not working on Attr nodes → RANGE: compare methods not working on Attr nodes
Whiteboard: [select][range] → [select][range][embed]
Target Milestone: mozilla0.9.2 → mozilla1.0
Summary: RANGE: compare methods not working on Attr nodes → compare methods not working on Attr nodes
Whiteboard: [select][range][embed] → [selection][range][embed][correctness]
getting range spec up to snuff. setting to 0.9.3 anthonyd
Target Milestone: mozilla1.0 → mozilla0.9.3
range stuff will at somepoint have to be corrected. i can see how people who wish to embed our product will need some of the range functionality to manipulate nodes (specifically text nodes). anthonyd
Whiteboard: [selection][range][embed][correctness] → [C],[selection][range][embed][correctness]
Assignee: anthonyd → kin
Status: ASSIGNED → NEW
Bulk move of mozilla1.0 bugs to mozilla.1.0.1. I will try to pull some of these back in if I can.
Target Milestone: mozilla1.0 → mozilla1.0.1
Testcase as posted fails to execute due to Range.intersectsNode not being implemented - this is bug 579638. qawanted: We should convert this into a mochitest.
Component: DOM: Traversal-Range → DOM: Core & HTML
Product: Core → Core
Windows 2000 support has been dropped a while ago. Please only reopen this bug if you can reproduce it on Windows XP or older with current Firefox builds.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
Ioana, there appears to be nothing win2k-specific about this bug. Please don't resolve bugs as wontfix based on their (bogus, automatically set by Bugzilla) OS field without actually trying to reproduce them.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
I tried to reproduce this issue with the attached test case on Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20100101 Firefox/25.0 and got the following: * range.compareNote throws an exception (no errors, more details displayed in the Browser console). * for range.intersectsNode, range.comparePoint, range.isPointInRange and range2.selectNodeContents, I get that "Argument 1 is not an object". The first argument for them is range.startContainer.firstChild. I don't get any other errors. Any ideas about how I could fix this test case?
Bulk priority change, per :mdaly
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.