Closed
Bug 1503874
Opened 7 years ago
Closed 7 years ago
Responsive design mode throws exception
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: f.rochlitzer, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
Steps to reproduce:
Win7 64Bit clean new installation, latest updates
FF 63 64Bit clean new installation, latest updates
1. Visit a website
2. Entering responsive design mode aka screen size testing (Ctrl + Shift M)
Actual results:
There is only a white page, nothing else.
The browser console logs:
ExceptioncolumnNumber: 0data: nullfilename: "chrome://browser/content/browser.js"lineNumber: 1043location: XPCWrappedNative_NoHelper { QueryInterface: QueryInterface(), filename: Getter, name: Getter, … }message: "Component returned failure code: 0x805e0006 [nsIWebNavigation.loadURIWithOptions]"name: ""result: 2153644038stack: "_loadURI@chrome://browser/content/browser.js:1043:7\nstart@resource://devtools/shared/base-loader.js -> resource://devtools/client/responsive.html/browser/swap.js:156:7\ninit@resource://devtools/shared/base-loader.js -> resource://devtools/client/responsive.html/manager.js:370:11\nResponsiveUI@resource://devtools/shared/base-loader.js -> resource://devtools/client/responsive.html/manager.js:295:17\nopenIfNeeded@resource://devtools/shared/base-loader.js -> resource://devtools/client/responsive.html/manager.js:118:18\ntoggle@resource://devtools/shared/base-loader.js -> resource://devtools/client/responsive.html/manager.js:66:48\noncommand@resource://devtools/shared/base-loader.js -> resource://devtools/client/menus.js:89:7\nfillSubviewFromMenuItems/<@resource:///modules/CustomizableUI.jsm:3927:13\n"<prototype>: ExceptionPrototype { toString: toString(), name: Getter, message: Getter, … }
Expected results:
The website with screen resolution toolbar should be visible.
Comment 1•7 years ago
|
||
Hi,
I haven't been able to reproduce this issue on Windows 7 using Firefox Nightly 65.0a1(2018-11-05), Firefox Beta 64.0b6(2018-11-01) or Firefox Release 63.0.1(2018-10-30).
Could you test if the issue is reproducible in safe mode, here is a link that can help you with that:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
If the issue still occurs please try using a new profile, you can find the steps here:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
Thank you for reporting!
Flags: needinfo?(f.rochlitzer)
| Reporter | ||
Comment 2•7 years ago
|
||
Same behavior in safe mode and with new profile.
As I told before I tested it on a clean new PC.
We have this issue now on all PCs in the company.
Flags: needinfo?(f.rochlitzer)
| Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Frank Rochlitzer from comment #2)
> Same behavior in safe mode and with new profile.
>
> As I told before I tested it on a clean new PC.
> We have this issue now on all PCs in the company.
I've installed FF 63.0.1 now in a Win7 VM without any additional antivirus or firwalls installed.
There was no FF previously installed.
Same issue.
| Reporter | ||
Comment 4•7 years ago
|
||
Ok, I've now installed FF nightly 65.0a1 in the VM.
The issue doesn't exists there!
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•