Open Bug 1726986 Opened 3 years ago Updated 2 years ago

"Invalid chrome URI (need path): chrome://messenger/" when opening Thunderbird preferences

Categories

(Thunderbird :: Theme, defect)

Thunderbird 92
x86_64
Linux
defect

Tracking

(Not tracked)

People

(Reporter: aceman, Unassigned)

Details

When opening Thunderbird preferences (on Linux) I get this message in the Error console:
Invalid chrome URI (need path): chrome://chat/

When opening any of the preferences subdialogs (like General->Check Now...) I get:
Invalid chrome URI (need path): chrome://messenger/

This repeats for any subdialog.

Maybe these generic theme references are no longer needed?

Hmm, WFM over here.

It may need some stricter JS debugging output.
Like MOZ_REPORT_ALL_JS_EXCEPTIONS=1 env variable,

prefs.js:
user_pref("javascript.options.strict", true);
user_pref("javascript.options.strict.debug", true);

aceman, do you still see this in current versions?

Flags: needinfo?(acelists)
Version: Trunk → Thunderbird 92

Yes, even with current trunk.

Flags: needinfo?(acelists)

I hate to report this, but under linux with the current C-C (update about 10 days ago)
I got the following.
This is with FULL DEBUG version of TB (thus strict checking, etc., I suppose)

With mochitest log, I get 195 (<- typo, was 165) such warnings.
grep "Invalid chrome URI" /FF-NEW/log1486-mochitest.txt | wc
195 1953 16495

Surprisingly, there was none with xpcshell test.

The breakdown is as follows.

ishikawa@ip030:~$ grep "Invalid chrome URI" /FF-NEW/log1486-mochitest.txt  | cut --delim=" " -f 2- | sort | uniq -c | sort -n -k 1 -r
    110 INFO Console message: Invalid chrome URI (need path): chrome://messenger/
     60 INFO Console message: Invalid chrome URI (need path): chrome://calendar/
     14 INFO Console message: Invalid chrome URI (need path): chrome://chat/
      7 INFO Console message: Invalid chrome URI (need path): chrome://global/
      3 INFO Console message: Invalid chrome URI (need path): chrome://openpgp/
      1 GECKO(100110) monitorConsole | extra message | {"message":"Invalid chrome URI (need path): chrome://messenger/","errorMessage":null,"cssSelectors":null,"sourceName":null,"sourceLine":null,"lineNumber":null,"columnNumber":null,"category":null,"windowID":null,"isScriptError":false,"isConsoleEvent":false,"isWarning":false}
ishikawa@ip030:~$ 

I am aware of many warning, but not sure how to prioritize them. Thus I have not reported these (or have i?)

It can be seen immediately when viewing the Account central pane, or the Account settings (Account manager).
I remember in the past we had such generic paths loaded in the css themes to inherit some global styling from toolkit. But I no longer see such URLs in css files.

I don't see this. Do you use a debug build?

(In reply to Richard Marti (:Paenglab) from comment #7)

I don't see this. Do you use a debug build?

I use a debug build (It seems I even added -DDEBUG to CFLAGS over the years).

aceman seems to set some environment variables and stuff in comment 2

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