| | |
|
|
|
Frameset will not validate!! |
|---|
| message from Real World Televisual on 19 Jul 2004 |
Hi there
Okay, I know framesets are a BIG no, no -- but there really is no way around
it [the client demands!!]. Anyway, using the template as supplied with
Dreamweaver MX and then putting the resulting frameset file through the
trusty W3C validator I continually receive the following errors...
there is no attribute "FRAMEBORDER"; there is no attribute "BORDER"; there
is no attribute "FRAMESPACING"
...in relation to the following;
<frameset rows="202,*" cols="*" frameborder="NO" border="0"
framespacing="0">
... and finally and more worryingly ...
document type does not allow element "NOFRAMES" here
... but the document is using the header as set-up by Dreamweaver, ie,...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd"
... I'm confused - as in very!!
|
| James Shook replied to Real World Televisual on 19 Jul 2004 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd"
<html>
<head>
<title>A simple frameset document</title>
</head>
<FRAMESET cols="20%, 80%">
<FRAMESET rows="100, 200">
<FRAME src="contents_of_frame1.html">
<FRAME src="contents_of_frame2.gif">
</FRAMESET>
</FRAMESET>
<NOFRAMES>
<BODY>
<P>What you see if frames cannot be displayed.</P>
</BODY>
</NOFRAMES>
</HTML>
DW's structure makes sense to me, but according to the W3C consortium of
HTML pundits, the correct format is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd"
<HTML>
<HEAD>
<TITLE>A simple frameset document</TITLE>
</HEAD>
<FRAMESET cols="20%, 80%">
<FRAMESET rows="100, 200">
<FRAME src="contents_of_frame1.html">
<FRAME src="contents_of_frame2.gif">
</FRAMESET>
<FRAME src="contents_of_frame3.html">
<NOFRAMES>
<P>What you see if frames cannot be displayed.</P>
</NOFRAMES>
</FRAMESET>
</HTML>
Notice there is no <BODY> tag and the <NOFRAMES> content is within the
outer <FRAMESET>. This seems odd to me. Anyway.
Framesets written by DW will work, in my experience, but they do not
conform to the W3C standards and so will not validate.
Your other errors relate to frame properties which do not validate under
your doctype. Don't use them and validate, or use them and don't
validate. I don't know of any way to get the effects of "FRAMEBORDER",
"BORDER" and "FRAMESPACING" in such a way that they will validate, but I
haven't tried to find one. I just use them.
|
| Real World Televisual replied to James Shook on 19 Jul 2004 |
Cheers James, that does the trick - but not the frame border and spacing
issues as you've already highlighted; I'll have a look round and see if
there's anything obviously obvious!
Thanks again everyone ;-)
|
| Joe Makowiec replied to Real World Televisual on 19 Jul 2004 |
What URI is the w3c validator checking?
|
| Real World Televisual replied to Joe Makowiec on 19 Jul 2004 |
Hi Joe
I'm running the validator locally; could this hold some relation to the
errors experienced?
|
| Joe Makowiec replied to Real World Televisual on 19 Jul 2004 |
Probably not. It would be a great help to us to see the code. If you
have some test webspace, could you post it there?
|
| Murray *TMM* replied to Real World Televisual on 19 Jul 2004 |
How can the client demand that you use frames? You are the web developer,
right?
|
| Real World Televisual replied to Murray *TMM* on 19 Jul 2004 |
There is some history to this project, in that as the sole developers of the
site we had complete control over its implementation [as you would normally
be more that accustomed to as we are] however the site is dynamic by means
of capturing visitor information and writing it to a MySQL db through the
user of PHP as its companion.
So? And? You're no doubt asking... well, local authority became involved and
the question of "data protection" came into view whereby the local authority
agency decided they should take over the capture and storing of said visitor
information. This in turn requires us to develop the site as is but put into
place the use of frames for the registration section to "cloak" the fact
that the visitor has moved away from the initial site.
If you guys have any other suggestions then please [pretty please!] feel
free to suggest away -- I hate the use of frames with a passion!! It feels
as if our hands are tied on this one to ensure the end client gets what
they're after... oh well!! I hope this makes sense!!
|
|
Archived message: Frameset will not validate!! (Macromedia Dreamweaver)
