Forum Moderators: mack
the problem is this : the submenu will be covered by the default.htm page. if i try to increase the ROWS values, then there is a gap between menu.htm and default.htm page.
so is there a way to let the submenu showing over the default.htm without increase the ROWS value for header frame?
I am very appreciated your help
Regards,
yongshan
How about you either answer constuctively or shut up!
Check out the dynamic drive HV Menu v5.5, that deals with frames, I haven't checked how they do it, but you might get some good pointers from it in how to approach the problem.
The main problem is that a frame/iframe window is separated from the container window in most browsers, although I think I got dropmenus to go over IE iframes, maybe not, I can't remember, definitely not in mozilla or opera.
As to dumping frames or iframes, definitely, let me know when there is a functional, stable, cross os and browser substitute for them, I'll be the first onboard. Most myths about frames are myths, search engines read them, users can access their contents, I have tons of top 10 google stuff contained in either frames or iframes, and most of my visitors never know the difference.
As for bad for quality, that's not true, a tweaked out overflow:auto thing that barely works, now that's bad for quality, or making a user scroll down endlessly to reach the content, then back up to get to the navigation, that's really a great feature.
Orlando offered sound advice. Frames are circa 1999 technology and make any site appear dated. Worse yet, frames are not dhtml-friendly+when indexed by the search engines, visitors often get access to your site by way of an orphan frame without the accompanying ones.
Framed sites have to remain simple to work without too many problems. By the next generation of browsers, they're history anyway, and you'd have to re-engineer your site all over again, without the frames.
**********************************
and you over there, Mr. Rudeness, whose name I can't see from this page view. Have the courtesy to show some respect when you open your mouth to give advise...especially BAD advise. You owe Orlando an apology. He was only trying to be helpful and save the poster the blood, sweat and tears we've all been through trying to get unruly frames to behave.
Now play nice, or take your mouth somewhere else!
kat
By the next generation of browsers, they're history anyway, and you'd have to re-engineer your site all over again, without the frames.
While the difficulties of working with frames/iframes exist as you noted, most of the problems can be solved, and they still have no adequate substitute in certain situations, it's still a choice on your part to use them or not, if you are willing to accept the problems and deal with them. The web is the only place in the world where something 5 years old is considered 'out of date', 5 years is not a long time in real world time.
Frame support isn't going anywhere, no browser maker is going to release a version with no frame/iframe support, especially when current HTML 4 and XHTML 1 transititional specifications fully support iframes, and almost fully support frames, which means that if a browser maker stopped supporting either technology, they would be releasing a screen browser that didn't support standards compliant basic html tags. This is not going to happen. I would expect full frame support for at least 5 more years, probably more.
The one place you will not find decent frame support is in handheld devices, and that's the real reason you should probably begin thinking of moving away from that kind of technology.
