Java plugin textpane unresponsive after dismissing dialogs or when mouse outside applet area



16 years ago
7 years ago


(Reporter: simonmorgan, Assigned: blackconnect)



Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

When swing dialogs are dismissed via their OK or Cancel buttons the caret in a
JTextPane disappears and text cannot be entered into the pane. Dismissing these
dialogs via the window manager does not have this affect. Also, if the mouse
pointer is outside of an applet area text cannot be entered but positioning the
pointer inside any part of any applet allows text to be entered again.

Reproducible: Always

Steps to Reproduce:
1.Need an applet using swing controls, specifically a JTextPane with additional
2.Select text then place mouse pointer outside text area 

Actual Results:  
No text can be entered while mouse is outside applet.
If a swing dialog is shown dismissing this via the swing OK/Cancel will have
same effect.
Effect not present if dialog dismissed via window manager.

Expected Results:  
Caret should have reappeared in the text pane and text should be enterable once
the applet is selected regardless of the mouse pointer position. Dismissing
dialogs should reactivate the text pane and re-enable keyboard input.

This only happens on the Linux version of Mozilla, the Windows version is
unaffected which leads me to beleive it is a problem with

This seems to affect all versions of Mozilla I have tested on the SuSE Linux
platform with the Java 1.4.1 plugin symlinked into the plugins directory.

Comment 1

16 years ago
Reporter can you reproduce this bug with a newer build (1.4 final) and java 1.4.2?
If not, then please close this bug as worksforme. Thanks.
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:
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.
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.