Closed Bug 524292 Opened 15 years ago Closed 15 years ago

Search > Find Nodes does not work in DOM inspector

Categories

(Other Applications :: DOM Inspector, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 522844

People

(Reporter: alice0775, Unassigned)

References

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2b2pre) Gecko/20091023 Firefox/3.5.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091024 Minefield/3.7a1pre ID:20091024042521 Search > Find Nodes does not work. Reproducible: Always Steps to Reproduce: 1.Start Minefield with DOM Inspector 2.0.3 (https://addons.mozilla.org/en-US/firefox/addon/6622) 2.Tools > Dom Inspector 3.File > Inspect aURL..., 4.Enter "chrome://browser/content/browser.xul"(without quotation) and Click OK button. 5.Search > Find Nodes 6.Input "sidebar"(without quotation) into an Id field and Click Find button. Actual Results: DOM tree does not expand. Object pane is empty. Expected Results: DOM tree should expand. Tree should be selected. Object pane should be displayed. Regression window: Works: http://hg.mozilla.org/mozilla-central/rev/ba9c06d83b3e Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091020 Minefield/3.7a1pre ID:20091020115018 Broken: http://hg.mozilla.org/mozilla-central/rev/ebe24de601e5 Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091020 Minefield/3.7a1pre ID:20091020114156 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ba9c06d83b3e&tochange=ebe24de601e5 Candidate regress bug: Bug 522601. Make inDeepTreeWalker closer to spec behavior and implement various unimplemented methods
Blocks: 522601
Keywords: regression
Version: unspecified → Trunk
Summary: Search > Find Nodes does not work → Search > Find Nodes does not work in DOM inspector
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.