Closed Bug 251904 Opened 21 years ago Closed 20 years ago

CNTL KEY WORKS OPPOSITE FOR MOZILLA WHEN USING HISTORY KILL

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: DIAMONDTIE, Assigned: aaronlev)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 There is an excellant product called History Kill, used to provide privacy on the PC after internet usage. It can be seen at the URL provided. It basically overwrites all temporary internet files when you are finished with the browser. The bug is that the CNTL key, which normally is needed to allow a pop up, will actually prevent any and all pop-up, even when desired, if using the FireFox Mozilla browser. At a mimimum, a warning is needed for those using History Kill. This is irregardless of whether the pop-up stopper is turned on or off. Reproducible: Always Steps to Reproduce: 1. Have History Kill running on the PC and using the Firefox Mozilla browser. 2. Hold down the CNTL key and click on a desired pop-up icon or underlined blue URL address. 3. Regardless of whether the pop-up stopper is turned on or off in History kill, the pop-up will NOT come up. Normally, the CNTL key ALLOWS the pop up to occur. Actual Results: No pop up, even when wanted, if the CNTL key is held down. Not a problem if it is not held down.
Do you know that Moz/FF has their own popup blocking software? Do they support Popup Blocking with NS7/Moz/FF?
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.