User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0 In the attached test case, after entering a value in the text field and pressing enter the text field has no flashing cursor and is unresponsive to the mouse events (i.e. text can't be highlighted by double clicking or clicking and dragging). Reproducible: Always Steps to Reproduce: 1. Open the test case. 2. Enter some text in the field and press enter. 3. Click in the field with the mouse to give focus back to it. 4. Try to select the text by double clicking or clicking and dragging it. Actual Results: After step 3 there is no flashing cursor in the field. In step 4 nothing happens. Expected Results: After step 3 there should be a flashing cursor in the field. In step 4 it should be possible to select the text using mouse actions. The field is responsive to typing but the effect is very off-putting - it seems like the field is not going to accept input and it's a surprise when it does.
Perhaps I should point out that although the test case is pointless - disabling and instantly re-enabling - what I'm actually doing is disabling straight after submitting the form and re-enabling when the server response is loaded in a frame - to stop the user typing or re-submitting the form until that time.
Fun focus issues... Duncan, do you happen to know whether this is a regression from Firefox 2? In any case, the key is that focus ends up in lala-land when we disable the control.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #4) > Fun focus issues... Duncan, do you happen to know whether this is a regression > from Firefox 2? I get the same behaviour using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:18.104.22.168) Gecko/20080623 Firefox/22.214.171.124
Created attachment 328652 [details] Workaround The attached seems to be a way to work around this. Just set focus on something other than the text field itself and the field starts behaving normally.
Yeah. This doesn't sound like a form controls bug so much. Sadly, we seem to have no good place to put focus bugs.
You need to log in before you can comment on or make changes to this bug.