re:
!>> What happens if you use the XHTML 1.0 Frameset dtd :
!> You get stuck in a quagmire since it doesn't support the necessary
!> attributes on the various tags to make the frames actually work
properly.
Gee, I wonder why this frameset and its frames work properly :
http://asp.net.do/test/frameset/default.aspx
???
re:
!> Not to mention that VS doesn't validate XHTML 1.0 Frameset.
VS 2008 validated the sample frameset I'm using as an example.
Look at the source for the default page...
It uses :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
The moral of this story is : test, test and test,
if you are going to state that something doesn't work.
In this case, it does work.
The source for the test's files is attached as frameset.zip, so anybody
can verify that :
1. The frameset does work properly
2. VS 2008 validates XHTML 1.0 Frameset
Thank you.
You get stuck in a quagmire since it doesn't support the necessary
attributes on the various tags to make the frames
actually work properly. Not to mention that VS doesn't validate XHTML
1.0 Frameset.
ere:
!> Framesets are not supported in XHTML 1.0, which is what VS 2005/08
validate against.
!> people tend to use CSS and DHTML to simulate what frames used to
provide.
What happens if you use the XHTML 1.0 Frameset dtd :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
???
Framesets are not supported in XHTML 1.0, which is what VS 2005/08
validate against.
Generally, people tend to use CSS and DHTML to simulate what frames
used to provide.
-Scott
I avoid iFrames like the plague for the same reason as Framesets. I
agree AJAX will support what is wanted by
refreshing a portion og the page without a noticeable PostBack but I
also think looking at MasterPages should be
considered. I would avoid AJAX though or use very very sparingly as
AJAX can drag down performance if not used
sparingly. Like iFrames and Framesets not everything that has been
created has proven to be usefull in --all--
circumstances and tends to get overused. Personally, I think trying
to beat the stateless model of the web is a
no-win compromise for the same reasons.
in message
You don't need to put the menu into a frame. Instead, show a new
page in a iframe control.Alternatively you can
look into Ajax-based solutions, depends on your task.
--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
Thanks for the reply.
I have a HTML page with frames, but I cannot open it in Dotnet
development environment(Visual Studio). It says
"element Frameset is not supported".
If frames are not good then I am ready to remove it.
As a junior developer please suggest me how to do it?
I have one menu page with few hyperlinks. On click I want to show
a new page on another frame without reloading
the menu page.
Let me know if it is possible or any other way to do it.
Please help this junior developer.
Thanks, Mark.
Frames are HTML and if you can't write HTML yet you are not ready
for ASP.NET. Furthermore, the use of Frames is
generally considered the best way to create a web site that is
not user friendly nor search engine friendly.
IMO Frames are only useful for very limited tasks such as a
Frameset using a Frame as a fixed header with a
scrolling Frame of columnar data below it. Otherwise? Framesets
are ca-ca
As a neophyte though if you explain what you think you need to
achieve I or others may have better suggestions
Hi Guys,
I am very new to ASP.NET world.
I need to create three frames. One at the top, one on the left
and another on the right side.
I don't know how to do it. So please help me with it.
I'll appreciate any help/example you can provide.
I am using visual studio 2005.
Thanks, Mark