175140 - Remove profile-bound chrome registry references to non-existent chrome providers

Status: RESOLVED INCOMPLETE

(Core :: XUL, defect, P3)

Description

[[e-mail] (away - not reading bugmail)]

Comment 1

[[e-mail] (away - not reading bugmail)]

this is a follow-up to bug 130331, bug 76512 and bug 86807

Comment 2

[[e-mail] (away - not reading bugmail)]

some randomly collected comments from aforementioned bugs:

- when a package doesn't have a specified locale or skin, the chrome registry is
supposed to fall back to the default, or perhaps whatever happened to be
registered first.

- I think that we need to be falling back to the default locale, as listed in
installed-chrome.txt file.  This is usually en_US, which is good enough IMHO.

- remove references (in user profile locale/skin) to not existing providers
(instead of simply converting the namespace)

- I think that it's curious that in the chrome.rdf file that's generated in my
home directory when I switch languages, the chatzilla locale url actually is for
the language that I picked, even though there is no locale for that language
with chatzilla. I would expect it to fall back to the default that I have
selected, en-US, which does exist.

Comment 3

[Christopher Blizzard (:blizzard)]

Is there any chance this is 1.2-worthy?

Comment 4

[[e-mail] (away - not reading bugmail)]

Chris, I'd love to see this fixed. With bug 130331 out of the picture, this
might appear a little less pressing and I might not have the bandwidth to make
it happen in 1.2 :-(

Perhaps someone else could?

Comment 5

[Dave Miller [:justdave]]

[e-mail] is about to go on a long vacation to the bit bucket

Comment 6

[timeless]

.

Comment 7

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 8

[Sylvestre Ledru [:Sylvestre]]

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

Comment 9

[Andrei Purice]

Hey Dave,
Does this issue still reproduce for you or should we close it?

Comment 10

[Dave Miller [:justdave]]

I have nothing to do with this bug and don't even have the platform in question to test it on. I think you meant to needinfo someone else.

Comment 11

[Andrei Purice]

Marking this as Resolved > Incomplete since the reporter cannot be contacted further to confirm if the issue is still reproducible.
If anyone can reproduce this issue please re-open the bug or file a new one.