939012 - Inspector can get stuck after element is destroyed.

Status: RESOLVED WORKSFORME

(DevTools :: Inspector, defect, P2)

Description

[Luke]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131028112446

Steps to reproduce:

After a jQuery dialog is destoryed, if you were inspecting something on it, the inspector panel breaks. For example:
http://jsfiddle.net/TCAgb/

After running this script, close the orange jQuery-dialog when the p tag in its contents is being inspected. With this element no longer existent, you can inspect the "log in" and other elements in the outer tab, but they will not highlight anything in the inspector panel - the inspector is now very broken.


Actual results:

Trying to move the inspector off a now-nonexistent element fails, and subsequent inspects also fail to highlight the element in the inspector DOM view. In the worst cases, the inspector panel can be completely blank where it should have the DOM nodes.


Expected results:

You should be able to always inspect elements in the inspector.

Comment 1

[[:Aleksej]]

Confirmed with firefox-25.0.ru.linux64.
Works for me with 2013-11-14-03-02-04-mozilla-central-firefox-28.0a1.en-US.linux-x86_64.

Comment 2

[Luke]

Thanks, can you mark this as "confirmed" please?

Comment 3

[buddhieash]

Checked on Nightly version 37.0a1 (2014-12-19) with Windows 7-64bit environment.Worked without get stuck.

Comment 4

[Dave Camp (:dcamp)]

Aleksej on irc just confirmed something like this happening on nightly:

If I understand correctly, this went away after: "I probably either or both: scrolled the page and shrunk the devtools."

Jeff, can you prioritize this against the devedition-40 list?

Comment 5

[Dave Camp (:dcamp)]

OK, maybe not the same bug - but we did see a stuck element in nightly, under different circumstances.

Comment 6

[Jeff Griffiths (:canuckistani) (:⚡︎)]

P2 for now - would really like to see a repro case and I don't understand the newer situation enough. If it was easy to repro, I would go P1.

Comment 7

[Brian Grinstead [:bgrins]]

I'm unable to reproduce via the steps in the description.  We will definitely need STR or at least the page that it happened on before someone can work on it.

Comment 8

[Brian Grinstead [:bgrins]]

I have a feeling this was either Bug 1121528 or Bug 1036324.  Going to mark as worksforme since both of these were resolved since that bug report.  Please reopen if someone is able to reproduce.