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.
Accepting bug and setting milestone to M12...
Summary: When apprunner is used as a rendering engine it hiccups badly on unresolve entities. → [DOGFOOD] When apprunner is used as a rendering engine it hiccups badly on unresolve entities.
I think this qualifies as a DOGFOOD bug.
*** Bug 11562 has been marked as a duplicate of this bug. ***
We need this for beta, but not dogfood, putting on PDT- radar.
Move non-PDT+ bugs to M13...
Moving non beta-stoppers to M16...
Putting dogfood in the keyword field.
Summary: [DOGFOOD] When apprunner is used as a rendering engine it hiccups badly on unresolve entities. → When apprunner is used as a rendering engine it hiccups badly on unresolve entities.
This no longer happens in the latest builds. Marking worksforme.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
Adding 'verifyme' keyword
Marking verified in the Sept 5th build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.