www.diesel.com bug?

warenhaus · Post by **warenhaus** » April 16th, 2003, 12:46 am

can it be that a simple frameset doesn't work in Phoenix (WinXP, TBE, NukeImage, AdBlock, RadialContext, Px 03-20) - works on IE6

http://www.diesel.com/successfullivingguides/

the frame itself works, if i enter it manually: http://www.diesel.com/successfullivingg ... nager.html

not that i'd desperately need this site, i just wondered.

dakboy · Post by **dakboy** » April 16th, 2003, 4:36 am

WFM, Moz 1.3, except I don't have Flash.

But I think I see the problem in the source as I did see something like this in a previous release or maybe in Netscape 4. The BODY tag should not anywhere in a frameset document. But there is one in that frameset's NOFRAMES section (and it's empty to boot). This is probably making Pheonix choke because it's not legit.

It was also incredibly slow. Plenty of other errors as well; they specify a DTD but don't comply with it. http://validator.w3.org/check?uri=http% ... gguides%2F

cdn · Post by **cdn** » April 16th, 2003, 5:16 am

1:
2: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">
3: 
4: <html>
5: <head>
6: <title></title>
7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
8: </head>
9: <frameset rows="100%,*" frameborder="NO" border="0" framespacing="0" cols="*">
10: <frame name="content" scrolling="NO" noresize src="blank.html" >
11: <frame name="manager" src="archive_manager.html">
12: </frameset>
13: <noframes>
14: <body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
15: </body>
16: </noframes>
17: </html>

even better if noframes was in the frameset where it is supposed to be

also when rearranged the validator only complains about attributes that don't exist, not about a <body> in <noframes>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">

<html>
<head>
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<frameset rows="100%,*" frameborder="NO" border="0" framespacing="0" cols="*">
<frame name="content" scrolling="NO" noresize src="blank.html" >
<frame name="manager" src="archive_manager.html">

<noframes>
<body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
</body>
</noframes>
</frameset>
</html>

Below are the results of attempting to parse this document with an SGML parser.

1. Line 8, column 36: there is no attribute "FRAMEBORDER" (explain...).

<frameset rows="100%,*" frameborder="NO" border="0" framespacing="0" cols="*">
^

2. Line 8, column 48: there is no attribute "BORDER" (explain...).

<frameset rows="100%,*" frameborder="NO" border="0" framespacing="0" cols="*">
^

3. Line 8, column 65: there is no attribute "FRAMESPACING" (explain...).

...s="100%,*" frameborder="NO" border="0" framespacing="0" cols="*">
^

4. Line 13, column 53: there is no attribute "LEFTMARGIN" (explain...).

...="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" margin
^

5. Line 13, column 67: there is no attribute "TOPMARGIN" (explain...).

..."#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
^

6. Line 13, column 83: there is no attribute "MARGINWIDTH" (explain...).

...margin="0" topmargin="0" marginwidth="0" marginheight="0">
^

7. Line 13, column 100: there is no attribute "MARGINHEIGHT" (explain...).

...gin="0" marginwidth="0" marginheight="0">
^

...

dtobias · Post by **dtobias** » April 16th, 2003, 10:49 am

dakboy wrote:But I think I see the problem in the source as I did see something like this in a previous release or maybe in Netscape 4. The BODY tag should not anywhere in a frameset document. But there is one in that frameset's NOFRAMES section (and it's empty to boot). This is probably making Pheonix choke because it's not legit.

No, there is supposed to be a BODY tag in the NOFRAMES section (there isn't supposed to be a BODY tag anywhere else in a frameset document besides within NOFRAMES). However, this particular site did commit the popular idiocy of having a completely empty NOFRAMES section... and, I've noticed that in such cases, the sites in question invariably specify the background color in the empty BODY element, showing that they're very nitpicky about exactly what color their completely blank page will come up in for non-frame users.

www.diesel.com bug?

www.diesel.com bug?

would work better with the correct doctype