By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,879 Members | 1,809 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,879 IT Pros & Developers. It's quick & easy.

Invalid Framset

P: n/a
In trying to have my site validated, the W3 validator was
annoyed with the FRAMEBORDER, BORDER, and FRAMESPACING
attributes that were included in my index.html file.
( http://www.ke6pij.org/index.html )

If this file were strict HTML then these attributes would
not exist, but then the page would also not be rendered
properly by Netscape, IE, or Opera since these browsers
don't seem to render frames appropriately using only the
W3C standard.

The rest of my site validates without a hitch and I have
in my index.html source the reasoning, and annoyance with,
the attributes for setting up the frames.

Is it wrong, then, for me to say the site is validated when
I have included these attributes in order to have the site
rendered as intended?

Is there a way to have the site rendered properly by all
browsers and still have it validate?

(If only Netscape and IE will get a clue and realize they
don't control the standard, then all these probnlems would
go away!)

-Paul

Jul 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
ke6pij <pa**@ke6pij.org> wrote:
In trying to have my site validated, the W3 validator was
annoyed with the FRAMEBORDER, BORDER, and FRAMESPACING
attributes that were included in my index.html file.
No, it's not annoyed at all. _You_ seem to be annoyed, when the validator
did what you asked it to do.
If this file were strict HTML then these attributes would
not exist,
What are you talking about? _Frames_ themselves do not exist in HTML.
Is it wrong, then, for me to say the site is validated when
I have included these attributes in order to have the site
rendered as intended?
Yes, of course.
Is there a way to have the site rendered properly by all
browsers and still have it validate?


Assuming "properly" means "as I want", the answer is "no".

BTW, there _is_ a FAQ entry about your problem.

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

Jul 20 '05 #2

P: n/a
ke6pij wrote:
In trying to have my site validated, the W3 validator was annoyed
with the FRAMEBORDER, BORDER, and FRAMESPACING attributes

If this file were strict HTML then these attributes would not exist
If it were HTML(4)/strict, then frames would not exist. To successfully
validate a document with frames, you must use HTML/frameset dtd.
in my index.html source the reasoning, and annoyance with, the
attributes for setting up the frames.
The best solution is to get rid of frames. They cause far more serious
problems than minor visual artifacts that you don't like.
Is it wrong, then, for me to say the site is validated when I have
included these attributes in order to have the site rendered as
intended?
An analogous question:

Is it wrong to claim that my car has passed the inspection if it failed
the emissions test?
Is there a way to have the site rendered properly by all browsers and
still have it validate?
I don't know. What is your definition of "rendered properly?"
(If only Netscape and IE will get a clue and realize they don't
control the standard,
There seems to be a lot that you don't realize. Netscape and IE are 2
important members of the W3C, the organization that publishes
recommendations like HTML 4.01/frameset. You also don't seem to
understand what validation is.[1]
then all these probnlems would go away!)


The problems that you're aware of, maybe.

http://dorward.me.uk/www/frames/

[1] Yes, fellow ciwah netizens, I realize how much that sounds like J.
Korpela. The longer I hang around here, the more I see how correct he is
about validation.

http://www.cs.tut.fi/~jkorpela/html/validation.html

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.