450254 - netError.dtd/netErrorApp.dtd are missing strings

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect)

Description

[timeless]

securityOverride.getMeOutOfHereButton 
securityOverride.exceptionButtonLabel

steps to reproduce:
1. instead of packaging firefox's netError.dtd, package the standard netError.dtd and netErrorApp.dtd
2. load any netError.xhtml driven error page

expected results:
an error page about some network error

actual results:
an xml validation/parser error complaining about missing entities.

note that in the non firefox overrides case, strings are split

Comment 1

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #0)
> securityOverride.getMeOutOfHereButton 
> securityOverride.exceptionButtonLabel

These entities are only referred to from within the DTD where they are defined, so I don't see how they would be causing trouble if you're not packaging that DTD.

What do you mean by "in the non firefox overrides case, strings are split"?

Comment 2

[therube]

> What do you mean by "in the non firefox overrides case, strings are split"?

Non-firefox, as in like SeaMonkey perhaps?

"Error pages broken in recent builds"
http://forums.mozillazine.org/viewtopic.php?f=6&t=983055

Comment 3

[Boris Zbarsky [:bzbarsky]]

No idea what's with that thread.  The dtd Seamonkey uses (the dom/ one) defines that entity (or rather includes a DTD which defines it).

Or is the problem that both DTDs (netError and netErrorApp) include the string?

Comment 4

[Boris Zbarsky [:bzbarsky]]

I should note that this is worksforme in current comm-central, by the way.

Comment 5

[[e-mail]]

As I recall these didn't exist in the first netError page, then they were added, but unfortunately only Firefox supplied the correct DTD, then netErrorApp was created to fix that, then SeaMonkey acquired an enhanced netError page, then Firefox switched to a certError page, and then SeaMonkey switched too.

So this should be WFM or DUP.