Closed Bug 1098380 Opened 10 years ago Closed 10 years ago

Developer edition: inspector tool doesn't reach the dom elements on right click

Categories

(DevTools :: Inspector, defect)

35 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1091706

People

(Reporter: neovea, Unassigned)

Details

Attachments

(1 file)

Attached image Sans-titre-1.jpg
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20141112004001

Steps to reproduce:

Right click on element page
select "inspect the element"


Actual results:

the inspector open up
but the selected element dom is not selected


Expected results:

the selected element should be selected and hilightened
I can't reproduce this. Can you reproduce if you restart with add-ons disabled (see the options in the help menu) or on a clean profile? ( https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles )
Component: Untriaged → Developer Tools: Inspector
Flags: needinfo?(neovea)
Summary: Developper inspector tool doesn't reach the dom elements on right click → Developer edition: inspector tool doesn't reach the dom elements on right click
Oh, and when it's broken, are there errors in the browser console?
I have the same problem with the default profile installed; it works however with a clean profile. When it is broken and started via Terminal (on Mac), I get this error in stdout:

A coding exception was thrown in a Promise resolution callback.
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise

Full message: TypeError: source is not an object
Full stack: merge@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/util/object.js:43:10
NodeFront<.form@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/inspector.js:727:18
types.addActorType/type<.read@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/protocol.js:282:7
exports.WalkerFront<.frontForRawNode@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/inspector.js:2854:22
Selection.prototype.setNode@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/framework/selection.js:136:1
CM_inspectNode/<@chrome://browser/content/nsContextMenu.js:512:9
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:865:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:7 

With a clean profile there is no such error.
So I actually deactivated ADB (Adblock), now it works.
Flags: needinfo?(neovea)
(In reply to neovea@gmail.com from comment #4)
> So I actually deactivated ADB (Adblock), now it works.

Erratum : This is not addblock, this ADB Helper from https://github.com/mozilla/adbhelper
I don't know what this is.
-> jryans per adb helper stuff (github says last commit is yours! :-) )
Flags: needinfo?(jryans)
(In reply to neovea@gmail.com from comment #5)
> (In reply to neovea@gmail.com from comment #4)
> > So I actually deactivated ADB (Adblock), now it works.
> 
> Erratum : This is not addblock, this ADB Helper from
> https://github.com/mozilla/adbhelper
> I don't know what this is.

ADB Helper enables WebIDE to connect to various USB devices.  However, I don't think it is directly at fault here.

I am pretty sure this is the same timing / loader problem from bug 1091706.  The add-on happens to invoke the loader at a different time, likely triggering that bug.

If you still see this issue after that bug is resolved, please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jryans)
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: