Closed
Bug 28799
Opened 25 years ago
Closed 25 years ago
No display & crash on the URL
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: t8m, Assigned: cbegle)
References
()
Details
(Keywords: crash)
After opening the URL the browser loads the page but doesn't display anything. When I try to switch between the Mozilla and some other application the Mozilla crashes (sometimes it crashes immediately sometimes I need to jump to the URL twice). The stack trace is the same as in the bug 28798. So I think it's related.
Comment 1•25 years ago
|
||
Just tested on NT. I don't get the crash or a freeze. Mozilla seems to load the page but the content is not displayed. I switched between several different applications while mozilla was in this empty state and could not produce a crash. The display area of the browser is empty but the chrome remains responsive and the back and reload buttons work just fine. Looking at the page's source I saw that this is an XHTML page. <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> Could this be a parser issue?
Comment 2•25 years ago
|
||
With 2000022108 win95, I don't crash either (but the stack trace referred to above is for Linux). However, the particular 'non-display' problem is orthogonal to whatever the crash is. Simply, if you remove the <?xml version='1.0'> from the source XHTML, then page displays fine. I know that XHTML is not fully done yet, and there may be a DUPL of this report somewhere. (I'll have a look later today).
Comment 3•25 years ago
|
||
I think this is a dupe of 29125 (I know this one was here first but that one has the momentum and has a fix noted and waiting to be checked in) Marking duplicate. *** This bug has been marked as a duplicate of 29125 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•