User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 I have a java applet which consists of text fields and buttons. When data validation is performed on the text fields, a pop-up dialog message will be displayed if any data error. However, if the dialog is set to modal, mouse pressed and click events are unable to be detected, and the dialog box simply can't be closed except by pressing the "enter" key. If the dialog is not modal, the mouse events can be detected when click on a button. I read earlier posting on the MozillaBreaker example, which illustrate a pop-up dialog box. When I use use the code in my applet, I found that the mouse actions seems to repond well if the dialog box is the first thing to pop-up. However, when the dialog pops-up after a text field is validated (simulating data error entry, for example), the buttons in the dialog simply can't be reached. And the window can't be closed either, even when I have all the listener implemented. Not sure if this has something to do with the JVM or the way modal dialog is handled in Netscape? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Sorry, as I mentioned "pressing the enter key" to close the dialog box, it should be "pressing the space bar".
...and this happens with the Linux and Mac OS X versions in 1.5 (Linux) and 1.7 (OS X).
This problem still happens on Netscape 7.1 (PC). The cause of the problem seems to be the AWT TextField class I was using. When I tried with JTextField (Swing), the dialog can respond to mouse click event. All the while I thought the problem was with the Dialog class, but it turns out to be the TextField! Not sure if this really a bug in the JVM implementation for browser? I don't encounter such problem when running on Netscape 4 and IE.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Component: Java-Implemented Plugins → Java-Implemented Plugins
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.