chrome is not registered for non-bootstrapped proxy file add-ons

VERIFIED FIXED in Firefox 55

Status

()

Toolkit
Add-ons Manager
--
major
VERIFIED FIXED
10 months ago
9 months ago

People

(Reporter: Denis Lisov, Assigned: kmag)

Tracking

(Blocks: 1 bug, {regression})

55 Branch
mozilla55
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox-esr45 unaffected, firefox-esr52 unaffected, firefox53 unaffected, firefox54 unaffected, firefox55+ verified)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Reporter)

Description

10 months ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170517100341

Steps to reproduce:

I'm developing Brief preparing it for WebExtensions migration. In the extensions directory there is a file named after the addon id containing the path to the git checkout used for development. A chrome package is registered with a line in chrome.manifest

content  brief  chrome/content/ remoteenabled=yes remoterequired=yes


Actual results:

In Firefox Nightly 2017-05-16 and 2017-05-17 the addon is no longer working. The add-on manager and about:support both show it as enabled, but no UI overlay is displayed and trying to navigate to the add-on page ( chrome://brief/content/brief.xhtml ) results in "No chrome package registered for chrome://brief/content/brief.xhtml" in the browser console.

I've narrowed down the regression window with mozregression to https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=9730f88bdbd3d167d3c5b1acb0618cd2533bb570&tochange=23dc7b443bb0528ec880acb7fc0a32aec05f0255

Comment 1

9 months ago
You are hitting bug 1365256 which has been fixed this night. Are you sure your Nightly is up-to-date (2017-05-17)?

I'm able to open and display the page chrome://brief/content/brief.xhtml and I don't have any error message in the console.

Could you test again, please.
Flags: needinfo?(dennis.lissov)
(Reporter)

Comment 2

9 months ago
The About window shows 2017-05-17. Reproduced successfully.

Reproduction steps:

git clone https://github.com/ancestorak/brief/ # development repository

# Start Nightly, create new profile, close Nightly

cd $PROFILE_DIR
mkdir extensions
echo "/path/to/cloned/brief/" > extensions/brief@mozdev.org

# Start nightly
# about:config - switch xpinstall.signatures.required to false
# about:addons - enable Brief, "restart now"

# Now, after restart, Brief is enabled according to about:addons and about:support
# However, there's no Brief button and the URL chrome://brief/content/brief.xhtml does not work


Is the path-based installation for development not supported now?
Flags: needinfo?(dennis.lissov)

Updated

9 months ago
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
Summary: chrome is not registered for an unpacked XUL addon → chrome is not registered non-bootstrapped proxy file add-ons
Duplicate of this bug: 1365134
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: chrome is not registered non-bootstrapped proxy file add-ons → chrome is not registered for non-bootstrapped proxy file add-ons
[Tracking Requested - why for this release]: Regression
Blocks: 1365717, 1358846
Severity: normal → major
status-firefox53: --- → unaffected
status-firefox54: --- → unaffected
status-firefox55: --- → affected
status-firefox-esr45: --- → unaffected
status-firefox-esr52: --- → unaffected
tracking-firefox55: --- → ?
Depends on: 1364878
Keywords: regression
Duplicate of this bug: 1366515
Comment hidden (mozreview-request)

Comment 7

9 months ago
mozreview-review
Comment on attachment 8869784 [details]
Bug 1365568: Enable chrome registration for non-bootstrapped proxy file add-ons.

https://reviewboard.mozilla.org/r/141338/#review144902

r+ assuming there's a good reason not to have a more explict exception for the `catch`... otherwise please fix and land no need for re-review.

::: toolkit/mozapps/extensions/internal/XPIProvider.jsm:133
(Diff revision 1)
> -    let file = base.clone();
> +  // files. Ideally we would try a relative path first, but on Windows,
> +  // paths which begin with a drive letter are valid as relative paths,
> +  // and treated as such.
> -    try {
> +  try {
> +    return new nsIFile(path);
> +  } catch (e) {

I'm not a big fan of catch-all exceptions... what does this throw, `NS_ERROR_FILE_UNRECOGNIZED_PATH`?

Ideally we should only catch the one we care about, especially if we're going to silently swallow it.
Attachment #8869784 - Flags: review?(rhelmer) → review+
Assignee: nobody → kmaglione+bmo
(Assignee)

Comment 8

9 months ago
mozreview-review-reply
Comment on attachment 8869784 [details]
Bug 1365568: Enable chrome registration for non-bootstrapped proxy file add-ons.

https://reviewboard.mozilla.org/r/141338/#review144902

> I'm not a big fan of catch-all exceptions... what does this throw, `NS_ERROR_FILE_UNRECOGNIZED_PATH`?
> 
> Ideally we should only catch the one we care about, especially if we're going to silently swallow it.

Yes, something like that. But the only things this will ever throw for are invalid paths and OOM, and in either case a failure that we need to care about will be caught by the relative path version below, so there's not much point in doing more specific checks.

Comment 10

9 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/d2fc6ed0d641
Status: NEW → RESOLVED
Last Resolved: 9 months ago
status-firefox55: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
tracking-firefox55: ? → +

Comment 11

9 months ago
Confirmed: add-ons installed via proxy files in user's profile/extensions directory are now loading properly in Thunderbird Daily.
Status: RESOLVED → VERIFIED
status-firefox55: fixed → verified
You need to log in before you can comment on or make changes to this bug.