hello , is there any one who would know to solve this problem
www.fdhost.net/test , site is planed to be made in 2 frames...
up and down. We want to use centered site ( 760 x NNN ) , and the thing is in up frame we use table width 760 for our flash navigation , and down we want to put some txt into table that is 760 too , But down table run away ( to left ) and it wount be centered.... Please Help ?

Thank you ,

Make a table in each frame and set it to 100% width and 100% height. Then you put align="center" and valign="top" in the table.
Insert your tables and other things in these big tables.

100% height align doesnt work in all browsers (such as netscape). So might want to find a way around that.

Look for a javascript to get the screen resolution then define the tables using inline css where height and width come from the javascript variables.

maybe just maybe...

I have found where was a problem , in frameset, up frame was set to no scroll , and I dont know tables wount be centered when this is on. Now you can find my site at www.fdhost,net ( english version is not redy yet :) )

Thank you,

English version here: http://www.fdhost.co.uk :)

No no no , its complity another company ! FDhost.net is Croatian Web Hosting provider :) , our english version of site will be able in few days... ;)
Heh...

mate avoid frames if u can.

Agree...

if (frames) {
echo ("bad");
}

:D

Why is that you suggest avoiding frames?

There are still some browsers that don't handle frames well, but perhaps of wider import is that they increase load times and can create problems if you want your site indexed on search engines. As can splash screens.

Wouldn't just reloading the dynamic portion of the page improve/reduce load times? I would think that not reloading menus, etc., would reduce the size of the downloaded data.

I understand that search engines don't like frames, at least those that don't go beyond the initial level of HTML. In our case, we're not too concerned about that, as we don't rely heavily on search engines to reach our customers.

It's still one of the golden rules of web design... don't use frames

Originally posted by Rich2k
It's still one of the golden rules of web design... don't use frames

If you were wondering, there are a couple of reasons for this:

[list=1]
Your design is available more easily to non-visual and text based browsers. In Lynx for example, I'd have to choose which frame to browse, making it a pain to navigate. I can't imagine what it would be like with Jaws (a speaking browser for the blind).
People like to use bookmarks, and frames are stateless unless you have some sort of slick server-side engine that rewrites the frameset on each hit, which would defeat part of the reason for using frames. When you bookmark a page with frames, you get the original frameset, not the frameset as it exists when you bookmark it. Maybe future browsers will fix this, as I think the concept of frames is kind of cool.
If you aren't careful, you may trap someone elses web site in one of your frames, which may confuse the user into thinking it is your content. If that content offends them, they'll think it came from you.
[/list=1]

That said, I use frames on occasion, but only for web applications where bookmarks aren't needed (or permalinks are offered), and the frames truly add to the functionality of the document.

Judge it case-by-case... for example, if you're developing a web site that will draw a large blind audience, you'd better skip the frames. I'm generally from the more conservative camp that says only use frames if you must.

-Paul

i got a 404 not found...