Feedback: irt.org FAQ Knowledge Base Q173
Feedback on:
irt.org FAQ Knowledge Base Q173
Sent by Milos Milisavljevic on December 01, 1999 at 16:19:36: - feedback #637
Worth:
Worth reading
Comments:
What browsers DO support location.replace() method? I tried with Netscape Communicator 4.6, and it did not work, but with IE 4.01 works fine. Interesting point is that the replace() worled fine in Netscape Communicator 4.01 ??? ( I mean the script worked fine)
Sent by Murray on February 08, 2001 at 13:59:46: - feedback #2343
Worth:
Very worth reading
Comments:
very worth reading because its a rare solution to find. however i just tried to make test webpages and named them everything thats in the code but it didn't work because the instructions left out what needs to be changed. it lacked depth, and i need help. please send and in depth email back, i really need this code.
thanks.
Murray
Sent by eric on June 27, 2001 at 14:13:36: - feedback #2907
Worth:
Very worth reading
Length:
Just right
Technical:
Not technical enough
Comments:
In frame.html, the frame names are defined as "frameI" and "frameJ". Therefore in frameB.html, any references to frame names "frameA" and "frameB" should instead read "frameI" and "frameJ", respectively, or the script won't work.
Sent by kevin manning on October 12, 2001 at 08:40:21: - feedback #3241
Worth:
Worth reading
Comments:
Worked fine for me until someone right clicks a link and decides to open the page in a new window.
This causes a JavaScript error because its looking for a frame that doesn't exist.
Short of disabling the right click option, I can't think of a way to get round it, any suggestions?
Sent by Stephen Evans on February 07, 2002 at 10:47:45: - feedback #3573
Worth:
Worth reading
Comments:
The code as written did not work with IE6. However, by changing the references to "parent.frameA.location.href" to "parent.frameI.location.href" and "parent.frameB.location.href" to "parent.frameJ.location.href" it does work.
| 