"XML Parsing Error: undefined entity" <xul:button>

RESOLVED INVALID

Status

SeaMonkey
General
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: Kamahl Zinier, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4pre) Gecko/20090414 SeaMonkey/2.0b1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4pre) Gecko/20090414 SeaMonkey/2.0b1pre

I'm using the Fierr extension, which makes a better looking error page. (note, this is my own tweaks on the extension http://yeoldesteve.googlepages.com/Fierrtweaked.xpi )

Upon loading this page, Seamonkey gives the following error:
[paste]
XML Parsing Error: undefined entity
Location: file:///D:/USERS/Kamahl/Application%20Data/Mozilla/SeaMonkey/Profiles/dhlgq9c4.default/extensions/%7B2E481B23-66AC-313F-D6A8-A81DDDF26249%7D/chrome/content/netError.xhtml
Line Number 357, Column 5:    <xul:button xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" id="tryBack"   label="&backCmd.label;"    oncommand="backPage();" />
----^
[/paste]

Commenting this out gives the error on the next use of <xul:button>, 
    <xul:button xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" id="tryAgain"  label="&reloadCmd.label;"  oncommand="reloadPage();" />


The identical code works fine under Firefox 3.0, and 3.5.

Reproducible: Always

Steps to Reproduce:
1. Install Fierr - http://yeoldesteve.googlepages.com/Fierrtweaked.xpi
2. Get an error page (I simply navigated to http://www.fsafsaf.foo/ )
Actual Results:  
Received XML Parse error.

Expected Results:  
Show Page load error.
(Reporter)

Updated

9 years ago
Version: unspecified → Trunk

Comment 1

9 years ago
This is a problem with the extension. Please complain to the extension author about these errors. =>INVALID
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.