Closed
Bug 1421383
Opened 7 years ago
Closed 7 years ago
WebExtension can interfere with requests from about:newtab
Categories
(WebExtensions :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: 5i13ghzt462u, Unassigned)
Details
(Whiteboard: [design-decision-needed])
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171113102334
Steps to reproduce:
Sometimes NoScript blocks requests from about:newtab. The issue now is: Why can it do so at all?
Because should not WebExtensions have no access to about:newtab as it is a Firefox-internal site? At least it looks as if they do not have, as all add-ons do not display any information about the site. Same with NoScript. It is labeled "NoScript" there and clicking on it takes you to the settings…
This continues Bug 1421095.
Actual results:
NoScript blocks request.
Note that I am not entirely sure it is about:newtab requesting it, but it seems to be something internal in Firefox.
Expected results:
AFAIK addons (WebExtensions) should not be able to interfere with Firefox-internal components, do they?
Updated•7 years ago
|
Component: Untriaged → WebExtensions: General
Product: Firefox → Toolkit
Updated•7 years ago
|
Whiteboard: [design-decision-needed]
Comment 1•7 years ago
|
||
Hi rugk, this has been added to the agenda for the December 19, 2017 WebExtensions APIs triage. Would you be able to join us?
Here’s a quick overview of what to expect at the triage:
* We normally spend 5 minutes per bug
* The more information in the bug, the better
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details
Relevant Links:
* Wiki for the meeting: https://wiki.mozilla.org/WebExtensions/Triage#Next_Meeting
* Meeting agenda: https://docs.google.com/document/d/1KwfTum8Ow5w4afPAOvShpu_d_MNtahhOIqL3-Em9lLc/edit#
* Vision doc for WebExtensions: https://wiki.mozilla.org/WebExtensions/Vision
Updated•7 years ago
|
Flags: needinfo?(amckay)
Comment 2•7 years ago
|
||
Thanks for the bug, but this is by design. The only requests that we feel should be locked down are ones vital to the functioning of the browser, such as block list requests or OCSP requests.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(amckay)
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•