Closed Bug 188844 Opened 22 years ago Closed 22 years ago

Nothing displays on Magelo.com

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 187790

People

(Reporter: dannybush, Assigned: asa)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104 Going to http://www.magelo.com, I don't get anything displayed. Using IE6 the page displays correctly. When I view source I get : <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Magelo - Powering Communities</title> <link rel="stylesheet" type="text/css" href="./style/magelo.css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> </head> <!-- Header for Magelo --> <script type="text/javascript" src="http://www.magelo.com/components/website_get_info.jsp"></script> <script src="magelo.js" type="text/javascript"></script> <script type='text/javascript'> if(website_up==true) { document.write("<frameset rows='72,*' cols='*' frameborder=0 framespacing=0>"); document.write("<frame name='top' src='top.html' marginwidth=0 marginheight=0 scrolling='no' frameborder=0 framespacing=0 noresize>"); document.write("<frameset cols='170,*' rows='*' frameborder=0 framespacing=0>"); document.write("<frame name='menu' src='menu.html' marginwidth=0 marginheight=0 scrolling='auto' frameborder=0 framespacing=0 noresize >"); document.write("<frame name='main' src='news.html' marginwidth=0 marginheight=0 scrolling='auto' frameborder=0 framespacing=0 noresize>"); document.write("<\/frameset>"); document.write("<\/frameset>"); } </script> </html> Reproducible: Always Steps to Reproduce: 1. just go to the website 2. 3.
*** This bug has been marked as a duplicate of 187790 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Component: Browser-General → Parser
QA Contact: asa → moied
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.