Closed Bug 233210 Opened 21 years ago Closed 12 years ago

Focus on an applet's text field components cannot be regained after focus on another window's component has been made

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ericchang591, Unassigned)

Details

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 Using the Java 1.4.x plugin on Mozilla 1.3.1 running on Red Hat 8.0, if one has an applet with a JTextfield component, and focus is gained on another window's component (button, text field, etc.), the focus on the JTextfield in the original window cannot be regained. For example, if there is an applet with a text field, and a button that will bring up Mozilla's print dialog, and the user clicks on the button to bring up the pring dialog and then cancels it by clicking on the Cancel button in the print dialog (thereby, "gaining" focus on the Cancel button), focus cannot be regained in the applet's JTextfield component. The will also apply to Javascript buttons as well. Reproducible: Always Steps to Reproduce: 1. Gain focus on a component outside the applet. 2. Attempt to gain focus on a textfield in the applet. Actual Results: The cursor will not appear in the textfield in the applet. Expected Results: Focus should be able to be obtained in the textfield.
Can you post an URL that contains a testcase? Also, try a newer version of Mozilla as 1.3.1 is almost a year old.
Assignee: yuanyi21 → pete.zha
mass reassign to Alfred
Assignee: zhayupeng → alfred.peng
Assignee: alfred.peng → nobody
QA Contact: java.oji
Product: Core → Core Graveyard
Mass-closing bugs in the "OJI" component: OJI plugin integration was replaced with npruntime long ago, and these bugs appear to be irrelevant now. If there is in fact a real bug that remains, please file it new in the "Core" product, component "Plug-ins".
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.