Closed Bug 251804 Opened 21 years ago Closed 19 years ago

Clicking a link from a frame doesn't open the corresponding page on the other frame

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 249603

People

(Reporter: lcalcada, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Clicking a link from a frame doesn't open the corresponding page on the other frame. Setting docshell.frameloadcheck.disabled to true in about:config circumvented the problem. Reproducible: Always Steps to Reproduce: 1. Open website 2. Click a link from the LEFT frame Actual Results: Notthing happens Expected Results: Page should change on the right frame Setting docshell.frameloadcheck.disabled to true in about:config circumvented the problem.
I've had the same problem with browsing threads on groups.google.com. As far as I can see, I have the same problem with all sites, where the target-attribute of the link is not quoted (i.e. myphpadmin cross-frame links work)
This occurs in the URL provided because the two frames are not on the same site. bp.tc.uol.com.br vs batepapo.uol.com.br This is a security measure to prevent cross site scripting. I think. I can't explain the behaviour in comment 1.
I get the same problem intermittently with Bloglines. The right-hand frame contains a list of postings from an RSS feed. The problem manifests itself intermittently and as yet I have been unable to ascertain the exact circumstance which triggers this behaviour.
Makes you wonder why the release notes for 0.9 asked that bugs like this be filed about sites where docshell.frameloadcheck.disabled is needed, if nobody planned on doing anything about them... *** This bug has been marked as a duplicate of 249603 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.