Closed
Bug 73552
Opened 24 years ago
Closed 4 years ago
compare methods not working on Attr nodes
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: pbwiz, Assigned: kinmoz)
References
Details
(Keywords: dom2, Whiteboard: [C],[selection][range][embed][correctness])
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
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
|
Reporter | |
Comment 1•24 years ago
|
||
thanks for the testcase!
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
|
Reporter | |
Comment 3•24 years ago
|
||
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.
|
||
Updated•24 years ago
|
Whiteboard: [select]
Target Milestone: --- → Future
|
|
||
Comment 4•24 years ago
|
||
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
Keywords: correctness,
dom2
|
|
||
Updated•24 years ago
|
Whiteboard: [select] → [select][range]
|
|
||
Updated•24 years ago
|
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
|
|
||
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla1.0
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]
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
|
||
Updated•15 years ago
|
QA Contact: lchiang → traversal-range
|
||
Comment 10•14 years ago
|
||
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.
Keywords: qawanted
|
||
Updated•14 years ago
|
Depends on: AttrExodus
|
||
Updated•12 years ago
|
Component: DOM: Traversal-Range → DOM: Core & HTML
|
||
Comment 11•11 years ago
|
||
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.
|
|
||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
|
||
Comment 12•11 years ago
|
||
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 → ---
|
|
||
Comment 13•11 years ago
|
||
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?
Keywords: qawanted
|
||
Comment 15•4 years ago
|
||
As per bug 73681 (and the DOM Standard) Attr nodes cannot contain child nodes so the test is (now) invalid.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•