after execute applet screen is locked

RESOLVED INVALID

Status

()

Firefox
Untriaged
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: kcunha, Unassigned)

Tracking

({crash})

10 Branch
x86
Windows XP
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: applet lock)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20120129021758

Steps to reproduce:

I have a system on AppEngine that uses GWT. In this, after user put information and press a button it calls apllet


Actual results:

After applet execution the screen is locked


Expected results:

After applet execution it is focus on a field
(Reporter)

Updated

6 years ago
Severity: normal → blocker
Keywords: crash
Priority: -- → P1
Whiteboard: applet lock
(Reporter)

Comment 1

6 years ago
From the beginning we suggest using this browser to have more reliability but this problem is impacting our users to use this browser.
We would not want to have to change our suggestion and asked that this issue is resolved asap.
thanks

Updated

6 years ago
Severity: blocker → normal
Priority: P1 → --

Comment 2

6 years ago
Please provide a public URL or reduced test case that exhibits this issue.

Does the issue still occur if you start Firefox in Safe Mode? http://support.mozilla.com/en-US/kb/Safe+Mode

How about with a new, empty profile? http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile
(Reporter)

Comment 3

6 years ago
Does the issue still occur if you start Firefox in Safe Mode? 
Yes, it does.

How about with a new, empty profile?
Yes, the error occurs even this

Note: If i click in another tab and come back to this tab, the screen is not locked anymore. But if i don't do this, the tab is still locked.

Only with firefox 10.0 it happens. When i use another version is working fine.
(Reporter)

Comment 4

6 years ago
This problem is not happing on 10.0.2
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.