1465047 - Developers tools console while debugging an extension clears itself when the extension closes

Status: RESOLVED INVALID

(DevTools :: Debugger, defect)

Description

[sgibb641]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180516032328

Steps to reproduce:

Upgraded from Firefox 52 ESR to Quantum on Windows 7
Load temporary addon, in this case, the one I'm trying to port from Chrome
Open the debugging console
Click the addon to open the popop


Actual results:

Error messages were displayed
Clicking on the developer console to copy-paste the errors closed the popup which cleared the console



Expected results:

Developer console should not clear itself until the next time the popup is opened as happened in the old FF 52 ESR

Comment 1

[Abe - QA (:Abe_LV)]

Hi sgibb641 (reporter),

I tested this on Windows 7 x64 with the latest esr 60.0.2, but could not manage to reproduce it.

The console works for me. I can copy logs. Logs are not deleted. 

Screen capture is here- https://testing-1.tinytake.com/sf/MjY4MzYzMF84MDUzNDAx

Do you suggest to test this on specific add-on? 


Test Env't
----------
Version 	60.0.2
Build ID 	20180605201706
Update Channel 	esr
User Agent 	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

Comment 2

[sgibb641]

I had this issue on Quantum with an unsigned addon

I should have clarified that I was not planning on getting the addon signed until it was working smoothly in unsigned mode

I have tried a signed addon from the store and it seems to work

The addon I am testing only has a popup script, no background or content scripts are involved, I suspect that might be part of the issue

Comment 3

[Abe - QA (:Abe_LV)]

Could you please provide the addon if possible? Thanks
(In reply to sgibb641 from comment #2)
> I had this issue on Quantum with an unsigned addon
> 
> I should have clarified that I was not planning on getting the addon signed
> until it was working smoothly in unsigned mode
> 
> I have tried a signed addon from the store and it seems to work
> 
> The addon I am testing only has a popup script, no background or content
> scripts are involved, I suspect that might be part of the issue

Could you please provide the addon for testing purpose if possible? Thanks

Comment 4

[sgibb641]

I've stripped the addon down to a little more than a bare minimum
https://drive.google.com/file/d/1MiZJnGlGXMHer3dI5zoKnSOzGHiQzMOB/view?usp=sharing

My test steps on FF Quantum 60.0.1 (64-bit) build ID 20180516032328 on Windows 7 are as follows:
Unzip my addon
Go to about:debugging
Check Enable add-on debugging
Load addon with Load Temporary Add-on
Click the debug button for the loaded addon
Allow connection
Drag debug window to second monitor (probably optional)
Click addon in bar, it will show a basic popup and log a bit to the debug console
Click anywhere else, the debug console wipes itself making copying any error messages out impossible

I believe I also have loading unsigned addons enabled but I'm told that that makes no difference in Quantum

Comment 5

[Jason Laster [:jlast]]

Honza, could you look into this?

Comment 6

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Click anywhere else, the debug console wipes itself making copying any error messages out impossible

Does it help if you check the "Persist" option in the Console toolbar?

Honza

Comment 7

[sgibb641]

I don't remember seeing such an option, why isn't it checked by default?
Assuming the option existed in FF 52 it must have been checked by default then, why not now?

I'm no longer at the job where I encountered this so if no-one else has encountered this issue then I guess this thread can be closed.

Comment 8

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks for the update!

I was testing this and checking the "Persist" options solves the problem.

It can be 'on' by default since it's memory/performance expensive, so users need to do it manually. The option (checkbox) is available in the Toolbar.

Honza