Closed Bug 587265 Opened 14 years ago Closed 14 years ago

Firefox Sync 1.4.4 Preferences in Firefox 4.0b3 fires XML error

Categories

(Cloud Services :: General, defect)

x86
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 582571

People

(Reporter: jeronimo, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3) Gecko/20100805 Firefox/4.0b3
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3) Gecko/20100805 Firefox/4.0b3

After install Firefox Sync 1.4.4 from https://addons.mozilla.org/pt-BR/firefox/addon/10868/  in Firefox 4.0b3 (appears as compatible with this version), and clicking in Firefox Sync "Preferences"  (in about:addons), it fires the following XML error:

Erro no processamento de XML: entidade não definida
Posição: chrome://weave/content/options.xul
Número da linha 6, coluna 3:  <setting id="weave-user" type="string" title="&username.label;" />
--^

Whats means:

XML Processing Error: undefined entity
Position: chrome://weave/content/options.xul
Line number 6, column 3:  <setting id="weave-user" type="string" title="&username.label;" />
--^

And no preference screen is shown. It is not possible to use the extension.

Reproducible: Always

Steps to Reproduce:
1.Install Firefox 4.0b3 (in my case is the pt-BR localized version)
2.Install Firefox Sync 1.4.4 from https://addons.mozilla.org/pt-BR/firefox/addon/10868/
3.In about:addons, click in Firefox Sync "Preferences" button.
Actual Results:  
An error message appears:

Erro no processamento de XML: entidade não definida
Posição: chrome://weave/content/options.xul
Número da linha 6, coluna 3:  <setting id="weave-user" type="string" title="&username.label;" />
--^

Whats means:

XML Processing Error: undefined entity
Position: chrome://weave/content/options.xul
Line number 6, column 3:  <setting id="weave-user" type="string" title="&username.label;" />
--^


Expected Results:  
Some configuration window should appear. I hope.
There seems to be something wrong with the language fallback in the nightlies, there have been other reports of errors with the pt-BR and tu locales on the mailinglists as well.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: