Look at the URL you will notice it itself. moz 2001020804
Trying again... sorry for the inconvenience... It's this little piece of JS in the 'main' page that makes it reload... I don't know *anything* about scripts, so I'm not gonna judge the validity of this... (it has script quotes around it in the real page) if (self.frames.name != 'info' && window.location.search =='') self.parent.location='index.php3?var_frame='+window.location.href;
Opera 4.01 have the same problem. I think it's a bug in the script and not in Mozilla. Changing: self.frames.name != 'info' to: name != 'info' makes it work in Opera and Mozilla too.
The frameset is also odd because there's something like this: <body> <p>Этот сайт использует фреймы, а ваш браузер, к сожалению, их не поддерживает</p> </body> and this shouldn't be in there at all. Or they have to put that in between of the <noframes> tags.
Again, I don't think self.frames.name is supposed to work, but it does in NS4 and IE5, so let's ask the DOM experts.
Assignee: asa → jst
Component: Browser-General → DOM Level 0
QA Contact: doronr → desale
window.frames.name works in 4.x because window.frames == window in 4.x, in mozilla that's not the case (window.frames is just a collection of windows, not a window object). I'm debating wether or not I should fix this and I think I might put this change into the XPConnectifying work that's going on right now. The reason I'm not jumping on to fixing this is that the reason the testcase uses self.frames.name is most likely just a typo, it doesn't make sense to do that, self.name is what they wanted.
*** Bug 75097 has been marked as a duplicate of this bug. ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Fixed by the xpcdom landing
Verified with 2001-08-28-08.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.