Opened 20 months ago

Last modified 14 months ago

#22431 new defect

Firefox bug - Browser Console stops auto-scrolling sometimes

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Minor Keywords: ff52-esr, tbb-usability, tbb-7.0-issues, tbb-regression
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It happens randomly, often after some error has appeared in console.
E.g.

"Handler function threw an exception: TypeError: this.transport is null
Stack: send@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1465:5
NEA_addSecurityInfo@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/webconsole.js:2217:5
NetworkResponseListener.prototype._getSecurityInfo<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:488:5
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
NetworkResponseListener.prototype.onStartRequest@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:429:5
Line: 1465, column: 5"  ThreadSafeDevToolsUtils.js:80
TypeError: this.transport is null[Learn More]  main.js:1465:5
TypeError: aPool is null[Learn More]  webconsole.js:499:5

So, some breakage in DevTools now affects auto-scrolling. (e10s?)

Child Tickets

Change History (5)

comment:1 Changed 20 months ago by cypherpunks

NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIProgressEventSink.onStatus]  network-monitor.js:314

comment:2 Changed 20 months ago by gk

Keywords: tbb-7.0-issues tbb-regression added

Regressions since 6.X.

comment:3 Changed 14 months ago by cypherpunks

Summary: Browser Console stops auto-scrollingFirefox bug - Browser Console stops auto-scrolling sometimes

Not fixed with new Browser Console in Firefox 57.

comment:4 in reply to:  3 ; Changed 14 months ago by gk

Replying to cypherpunks:

Not fixed with new Browser Console in Firefox 57.

I think step 1 would be to file a bug at https://bugzilla.mozilla.org as I suspect there are some devs at Mozilla who could help with that? Has that been done (ideally with some steps to reproduce the problem or to narrow it down) already? If so, what's the bug number?

comment:5 in reply to:  4 Changed 14 months ago by cypherpunks

Replying to gk:

Replying to cypherpunks:

Not fixed with new Browser Console in Firefox 57.

I think step 1 would be to file a bug at https://bugzilla.mozilla.org as I suspect there are some devs at Mozilla who could help with that?

Really? Have you found a way to submit tickets anonymously and without JavaScript?

Has that been done (ideally with some steps to reproduce the problem or to narrow it down) already? If so, what's the bug number?

https://bugzilla.mozilla.org/show_bug.cgi?id=1412294

Note: See TracTickets for help on using tickets.