Closed Bug 1525990 Opened 6 years ago Closed 6 years ago

Reload breaks Responsive Design Mode for file:/// URIs (tab goes blank, reload animation plays forever)

Categories

(DevTools :: Responsive Design Mode, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1525188

People

(Reporter: dholbert, Unassigned)

Details

STR:

  1. View any file URI, e.g. file:/// or perhaps file://c/ if you're on Windows.

  2. Change to RDM (Ctrl+Shift+M)

  3. Reload (Ctrl+R)

ACTUAL RESULTS:

  • The tab goes blank and looks like it's reloading (pays the reload animation in tab-title), but it never makes any progress.
  • If you switch tabs away and back, the URLbar is cleared as well.
  • These 4 errors appear in my browser console:

[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheetUsingURIString]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 65" data: no]
runSafeSyncWithoutClone resource://gre/modules/ExtensionCommon.jsm:65
cleanup resource://gre/modules/ExtensionContent.jsm:353
close resource://gre/modules/ExtensionContent.jsm:814
destroyed resource://gre/modules/ExtensionContent.jsm:889
observe resource://gre/modules/ExtensionContent.jsm:905

[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 65" data: no]

Security Error: Content at moz-nullprincipal:{2ae29653-815b-4a9c-a171-8ba6ba029385} may not load or link to file:///.

this.nativeTab.linkedBrowser is null


Ah, looks like this is already filed as bug 1525188.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

Also, for the record: in a fresh profile with mozregression, I actually only see the "Security Error: Content at moz-nullprincipal: [...]" error that I posted in comment 0, when the bug is triggered. The other ones don't appear (not at the time that I reload, at least).

You need to log in before you can comment on or make changes to this bug.