248310 - Clicking on https:// links (with target= other frame) does nothing

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Michal Kosmulski]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9

On one particular page I use (which I can't unfortunately give a link to since
it's password protected and contains sensitive information) there are quite a
lot of frames, one of which contains a menu with links which open in another
frame. All of them are https:// and in firefox 0.9 clicking on them does
nothing. However, MMB clicking them does indeed open them in new tabs. The page
worked correctly with another Mozilla (I don't recall the version).

Reproducible: Always
Steps to Reproduce:
Must go to that page, unfortunately. I couldn't find another similar setup, but
I think what's important are the multiple frames and that the links are https://
rather than http://
Actual Results:  
Links were not opened after clicking

Expected Results:  
They should open

Comment 1

[PikeUK]

Does the third bullet of the known issues section of the release notes help?

http://www.mozilla.org/products/firefox/releases/#issues

Comment 2

[Michal Kosmulski]

Yes, after setting docshell.frameloadcheck.disabled to true, that page works as
it should.

Comment 3

[T Meyer]

Some help to reproduce this bug (always):

You can try http://www.cpr-online.fr
1)Hit "Connexion" button
2)Type in any combination in the "Code utilisateur" and "Mot de passe" boxes
3)Hit "Acceder au site" button : nothing happens!

This bug is present only since Firefox v0.9 (0.8 and older where OK).

Turnaround:
1)Right click on the frame and choose "Frame / Show only this frame"
2)Type in any user code/password (or the right ones) : Works fine!

[e-mail]

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.