13115 - When apprunner is used as a rendering engine it hiccups badly on unresolve entities.

Status: VERIFIED WORKSFORME

(Core :: XML, defect, P3)

Description

[Brad Neuberg]

I have been experimenting with using apprunner as a rendering engine.  I run:
apprunner -chrome chrome:/test/HelloWorld.xul
where I have created a HelloWorld.xul file in the chrome directory under a test
directory:
HelloWorld.xul:
<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

<window id="main-window" xmlns:html="http://www.w3.org/TR/REC-html40"

xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
			  title="&badentity;"
			  width="640" height="480">

</window>

Notice that in the title attribute I have an entity named badentity.  If I run
apprunner with this example XUL file it completely crashes and just opens a tiny
little window in the upper left corner of the screen (i.e. it renders absolutely
nothing and just makes a tiny window).  It is dangerous that apprunner crashes
for unresolved entities because a large app written in XUL probably has hundreds
of entities, and one unresolved entity shouldn't bring down the whole system.

Comment 1

[Nisheeth Ranjan]

Accepting bug and setting milestone to M12...

Comment 2

[Nisheeth Ranjan]

I think this qualifies as a DOGFOOD bug.

Comment 3

[Nisheeth Ranjan]

*** Bug 11562 has been marked as a duplicate of this bug. ***

Comment 4

[leger]

We need this for beta, but not dogfood, putting on PDT- radar.

Comment 5

[Nisheeth Ranjan]

Move non-PDT+ bugs to M13...

Comment 6

[Nisheeth Ranjan]

Moving non beta-stoppers to M16...

Comment 7

[leger]

Putting dogfood in the keyword field.

Comment 8

[Nisheeth Ranjan]

This no longer happens in the latest builds.  Marking worksforme.

Comment 9

[Christine Hoffman]

Adding 'verifyme' keyword

Comment 10

[Chris Petersen]

Marking verified in the Sept 5th build.