User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a) Gecko/20040512 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a) Gecko/20040512 Firefox/0.8.0+ Do this with the upcoming testcase. Delete one of the objects in the frame (the body element or the text node). The element/node stays in the tree view although the element itself is deleted. Reproducible: Always Steps to Reproduce: 1. See above 2. 3. Actual Results: The element/node stays in the tree view although it has been removed. Expected Results: The element/node should be removed from the tree view
Yeah. The current setup in inDOMView is kind of wacky. The problem is that the node we get the observer method isn't in our array of visible nodes. Which is just messed up... I'll try and re-write the way our node array works, which should fix a number of other bugs on stuff not disappearing or not appearing, etc. when it should.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Interesting. inDOMView.cpp is getting the wrong tree view (the attributes tree instead of the node view tree) in some scenarios, which is causing this bug.
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
You need to log in before you can comment on or make changes to this bug.