Closed
Bug 1388603
Opened 8 years ago
Closed 8 years ago
NoScript breaks view source on nightly
Categories
(WebExtensions :: General, defect)
WebExtensions
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jtojnar, Unassigned)
Details
(Keywords: nightly-community)
In Nightly 2017-08-07, when I try to view source, only a blank page opens. The following message appears in the browser console:
Component returned failure code: 0x805e0007 [nsIWebNavigation.loadURI] viewSource-content.js:352
The file is chrome://global/content/viewSource-content.js
| Reporter | ||
Updated•8 years ago
|
Keywords: nightly-community
Comment 1•8 years ago
|
||
(In reply to Jan Tojnar from comment #0)
> In Nightly 2017-08-07, when I try to view source, only a blank page opens.
> The following message appears in the browser console:
>
> Component returned failure code: 0x805e0007 [nsIWebNavigation.loadURI]
> viewSource-content.js:352
>
>
> The file is chrome://global/content/viewSource-content.js
On which pages does this happen? How are you opening view source? Which platform?
WFM on nightly for Aug. 8 as well as Aug. 9 on OS X, tested on google.com and mozilla.org by using the keyboard shortcut (accel-u).
Component: General → View Source
Flags: needinfo?(jtojnar)
Product: Firefox → Toolkit
| Reporter | ||
Comment 2•8 years ago
|
||
I am running Nightly on NixOS (Linux). Seems to happen on all pages either by using menu or the keyboard shortcut. It happens even when clicking the file name in the browser console.
It looks like a collision with NoScript – it works on clean profile until I install the extension.
Flags: needinfo?(jtojnar)
Comment 3•8 years ago
|
||
This sounds like breaking changes in Nightly broke something noscript relies on.
Component: View Source → Add-ons
Flags: needinfo?(g.maone)
Product: Toolkit → Tech Evangelism
Summary: Cannot view source → NoScript breaks view source on nightly
Version: 57 Branch → unspecified
Comment 4•8 years ago
|
||
There's no expectation for legacy add-ons to work on 57 and above, so I don't think this is something we need to track. I suggest reporting this issue in the NoScript forum (https://forums.informaction.com/viewforum.php?f=3), though I suppose their focus right now is in getting the ported WebExtensions version out.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(g.maone)
Resolution: --- → WONTFIX
Comment 5•8 years ago
|
||
:jorgev is right, breakages will happen very often on Nightly and you'll very soon (already?) need to flip an about:config preference to make NoScript and other "legacy" add-ons keep struggling there while the WebExtension version is rolling out.
This is particularly true for NoScript, since it needs to support the Tor Browser (thus ESR) during the migration, and it also contains very ancient code much likely to break.
Therefore, if you need NoScript stay on 56 at most until 57 gets stable, or even better stay on ESR/Tor Browser as long as possible.
Anyway, the first two major Nightly breakages have just been fixed by 5.0.9rc1, https://noscript.net/getit#devel
| Assignee | ||
Updated•6 years ago
|
Component: Add-ons → General
Product: Tech Evangelism → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•