Developer Tools panel opens incessantly since installing v. 21

RESOLVED INCOMPLETE

Status

()

Firefox
Developer Tools
RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: Agostinho Couto, Unassigned)

Tracking

22 Branch
x86
Windows 8
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.2; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130511120803

Steps to reproduce:

Just installed version 21. It wasn't happening before.
(Reporter)

Comment 1

5 years ago
I've tried safe mode. My add-ons are updated. The problem goes on.

Updated

5 years ago
Component: Untriaged → Developer Tools
(Reporter)

Comment 2

5 years ago
I had to downgrade to Firefox v. 20.0.1.

Comment 3

5 years ago
Any Chrome errors in the console? You can select to view them using Console2 addon.
(Reporter)

Comment 4

5 years ago
Yes, I got the following message from Console2 (free trasnlation from portuguese): 
Warning: the box XUL for element h1 contained a element inline #text, forcing all descendants to be placed in a block.
Source file: chrome://browser/content/profiler.xul
(Reporter)

Comment 5

5 years ago
I got that message from Console2 after reinstalling v. 21. I'll downgrade again, since the bug still is going on.
(Reporter)

Comment 6

5 years ago
(In reply to Luke from comment #3)
> Any Chrome errors in the console? You can select to view them using Console2
> addon.

Yes, thanks. I got the following message from Console2 (free trasnlation from portuguese): 
Warning: the box XUL for element h1 contained a element inline #text, forcing all descendants to be placed in a block.
Source file: chrome://browser/content/profiler.xul
I got that message from Console2 after reinstalling v. 21. I'll downgrade again, since the bug still is going on.

Comment 7

5 years ago
I don't think that's the problem. Warnings aren't usually serious, and I remember seeing that same message on my working install. Make sure "Chrome" is checked, and uncheck all but errors to see only errors.
(Reporter)

Comment 8

5 years ago
(In reply to Luke from comment #7)
> I don't think that's the problem. Warnings aren't usually serious, and I
> remember seeing that same message on my working install. Make sure "Chrome"
> is checked, and uncheck all but errors to see only errors.

No Chrome errors were detected.
(Reporter)

Comment 9

5 years ago
I've upgraded to v.22 and the bug still goes on. I got the following Chrome errors from Console2:
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: NTK.faviconService.getFaviconImageForPage is not a function
Arquivo fonte: chrome://newtabking/content/newtabking-pre-min.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: NTK.faviconService.getFaviconImageForPage is not a function
Arquivo fonte: chrome://newtabking/content/newtabking-pre-min.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: ReferenceError: NOTIFICATION_CHECK_INTERVAL is not defined
Arquivo fonte: chrome://memfx/content/mfxOverlay.js
Linha: 699
 ----------
Erro: TypeError: xmlHttp.responseXML.documentElement.getElementsByTagName(...)[0] is undefined
Arquivo fonte: chrome://newtabking/content/rss_view.js
Linha: 1
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: ntk.pnl.contentDocument.body is null
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: NTK.faviconService.getFaviconImageForPage is not a function
Arquivo fonte: chrome://newtabking/content/newtabking-pre-min.js
Linha: 1
 ----------
Erro: TypeError: aTab is null
Arquivo fonte: chrome://browser/content/tabbrowser.xml
Linha: 2084
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: ReferenceError: NOTIFICATION_CHECK_INTERVAL is not defined
Arquivo fonte: chrome://memfx/content/mfxOverlay.js
Linha: 699
 ----------
Erro: ReferenceError: NOTIFICATION_CHECK_INTERVAL is not defined
Arquivo fonte: chrome://memfx/content/mfxOverlay.js
Linha: 699
 ----------
Erro: TypeError: xmlHttp.responseXML.documentElement.getElementsByTagName(...)[0] is undefined
Arquivo fonte: chrome://newtabking/content/rss_view.js
Linha: 1
 ----------
Erro: TypeError: Components.classes['@mozilla.org/privatebrowsing;1'] is undefined
Arquivo fonte: chrome://newtabking/content/ntk3.js
Linha: 1
 ----------
Erro: TypeError: xmlHttp.responseXML.documentElement.getElementsByTagName(...)[0] is undefined
Arquivo fonte: chrome://newtabking/content/rss_view.js
Linha: 1
(Reporter)

Comment 10

5 years ago
Another Chrome error, after deactivating the New Tab King addon:
Erro: ReferenceError: NOTIFICATION_CHECK_INTERVAL is not defined
Arquivo fonte: chrome://memfx/content/mfxOverlay.js
Linha: 699

Thanks for your help.
Version: 21 Branch → 22 Branch
Could you please test only with *all* add-ons disabled? This way we could see if the problem still occurs and any errors in the log will be relevant. Thanks.
(Reporter)

Comment 12

5 years ago
Thanks for your time, but I used the "about:config" and turned all devtools instances into "false". The annoyance is now over.
(Reporter)

Comment 13

5 years ago
(In reply to Panos Astithas [:past] from comment #11)
> Could you please test only with *all* add-ons disabled? This way we could
> see if the problem still occurs and any errors in the log will be relevant.
> Thanks.

Thanks for your time, but I used the "about:config" and turned all devtools instances into "false". The annoyance is now over.

Comment 14

5 years ago
Interesting - Could you turn them back on one by one to see when it causes this problem? Do you notice the problem in 23 beta?
(Reporter)

Comment 15

5 years ago
(In reply to Luke from comment #14)
> Interesting - Could you turn them back on one by one to see when it causes
> this problem? Do you notice the problem in 23 beta?

Hello, thanks for your concerns. The bug came back when I turned "devtools.toolbar.enabled" as "true". I don't install beta versions, sorry.

Comment 16

5 years ago
(In reply to Agostinho Couto from comment #15)
> (In reply to Luke from comment #14)
> > Interesting - Could you turn them back on one by one to see when it causes
> > this problem? Do you notice the problem in 23 beta?
> 
> Hello, thanks for your concerns. The bug came back when I turned
> "devtools.toolbar.enabled" as "true". I don't install beta versions, sorry.

Luke is interested in your results of having "devtools.toolbar.enabled" as "true" and ALL addons disabled, then enable them one by one.
Flags: needinfo?(acanto)
We've not been able to reproduce this issue, so I'm going to close it for now. We can open it again if we find that it's not add-on related and still happening in latest releases.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
(Reporter)

Comment 18

5 years ago
(In reply to Joe Walker [:jwalker] from comment #17)
> We've not been able to reproduce this issue, so I'm going to close it for
> now. We can open it again if we find that it's not add-on related and still
> happening in latest releases.

Thanks for your reply. I've been traveling and couldn't log in at Bugzilla until today. I hope it's only a specific matter and don't affect others.
Flags: needinfo?(acanto)
You need to log in before you can comment on or make changes to this bug.