Closed Bug 1850464 Opened 10 months ago Closed 10 months ago

Firefox Load temporary addon not working

Categories

(WebExtensions :: Untriaged, defect)

Firefox 116
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: chenzero, Unassigned)

Details

Steps to reproduce:

Firefox version: 116.0.3 Ubuntu 22.04
the standard borderify addon is not working.
borderify addon code:
https://github.com/mdn/webextensions-examples

Reproduce steps:
1 git clone borderify code
2 in Firefox, select menu "Add-ons and Themes" >> "Debug Add-ons" >>
"Load Temporary Add-on...",
then select the borderify manifest.json,
3 after install the addon, no any mozilla.org page is borderified.
e.g: a page with url: https://www.mozilla.org/en-US/
further more, when refresh the tab https://www.mozilla.org/en-US/,
in debug console, it will show a log "undefined: undefined",
I am certain that if no install the borderify addon, this log will not be printed.

Actual results:

after install the addon, no any mozilla.org page is borderified.
e.g: a page with url: https://www.mozilla.org/en-US/

Expected results:

mozilla.org page should be borderified

I also tried Firefox version 117, borderify add-on also not work, except in debug console, no "undefined: undefined" printed.

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Product: Firefox → WebExtensions

(this was reported before at https://github.com/mdn/webextensions-examples/issues/538)

I tried again in a VM with Ubuntu 22.04.3 LTS and can still not reproduce the issue. I'm therefore closing this issue.

The only reason for the observed issue that I can think of is if you've set History to "Never Remember History" (same as bug 1661906). If this is the case, visit about:addons, click on the Borderify extension and set "Allow in Private Windows" to "Allow".

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.