Hey, how can i call a function in another frame
with Netscape 4.* & 6
i use this with Explorer
parent.frames.menu.goto('/Corporates');
or
parent.parent.frames.menu.goto('/Corporates');
if it's nested frameset!
tx
Printable View
Hey, how can i call a function in another frame
with Netscape 4.* & 6
i use this with Explorer
parent.frames.menu.goto('/Corporates');
or
parent.parent.frames.menu.goto('/Corporates');
if it's nested frameset!
tx
wouldn't it be like
parent.frames[0].goto('/Corporates');
Probably, Scoutt, but that would imply you've actually looked at the standards.
HINTHINT, SEBS
I know, that is scary isn't it. :D
I know i know!Quote:
Originally posted by CiberTHuG
HINTHINT, SEBS
But what was so scary scoutt!!
not to get off topic or get anyone into a fit but.....
could you (anyone) explain why the standards are so important?
if something works, it works.
right?
i get the feeling i'm gonna get bashed for that question.....
oh well.....
****edit****
ok, i think i get it.
if your designing for new browsers, be complient.
cuz it's easy and why not
****end edit****
not by me anyway!Quote:
Originally posted by pnj
i get the feeling i'm gonna get bashed for that question.....
oh well.....
The standards are good when you want to satisfy everybody!
i.e. the maybe 1.3% that still use a non frame browser!
Anyway, the main idea of this thread is no good anymore,
cuz i just found out that NN6 javascript can't communicate with
flash movie anymore!!
That was the all point :(
Tx anyway!
I actualy went out of my way to look at the standards like Travis said. I guess that was it. :rolleyes:Quote:
Originally posted by sebs
I know i know!
But what was so scary scoutt!!
Dude, I wish I had a way to just make everyone understand. All modern browsers are frame browsers, and there is a standard that dictates frame use. And on a big tangent, the problem with frames isn't that browsers don't support them, but that 99% of the people who try to use them can't spell UI.Quote:
Originally posted by sebs
The standards are good when you want to satisfy everybody!
i.e. the maybe 1.3% that still use a non frame browser!
This is why the standards are so important:
HTML is an open format. If everyone rights it the same way, then there is no guess work, and every browser will render it the exact same way. If you think, "Well this works, so...." well, you are just setting yourself up for a failure. It may only work in a single busted browser. And when the next version of that browser comes out, it may not work because the browser has been fixed.
Furthermore, if you write your page to the standard, then you can say, YBMS! If the page doesn't render like I want, it is your fault not mine. Whereas, if you don't stick to the standard, then if a page doesn't render correctly (a la vBulletin) then the surfers can say, "this page is lame, the layout sucks, and the javascript doesn't work. Must've been written by some kid".