If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Calling listTabs twice makes webconsole tests fail

NEW
Unassigned

Status

()

Firefox
Developer Tools: Console
P3
normal
4 years ago
4 years ago

People

(Reporter: anton, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
This is a bit of a mystery. While working on bug 817836 I discovered that if you call listTabs twice (once on toolbox-ready and once from within the makeRemote for example) then the following webconsole tests fail with some weird errors like 'value was not discarded':

[X] browser_bug_869003_inspect_cross_domain_object.js
[X] browser_webconsole_bug_600183_charset.js
[X] browser_webconsole_bug_630733_response_redirect_headers.js
[X] browser_webconsole_netlogging.js

I worked around this issue in the aforementioned bug but the whole thing still seems to be very fragile.
Did you investigate to see why they actually break?

They all seem to relate to network logging (in the console actor), or tab navigation (in the tab actor).
(Reporter)

Comment 2

4 years ago
I attempted (and so did dcamp if I recall correctly) but when I discovered the workaround I decided to focus on finishing my console.profile bug instead.

So far it seems like one of the listTabs calls somehow sets all those properties such as discardProperty but I couldn't find where it happens in the code.

Sorry for not being too helpful.
test-related.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.