Response from Paul :

> 1. Load page with single line textboxes
> http://www.csse.monash.edu.au/~jwb/c...wwwnewword.cgi
> 2. Click in a textbox
> 3. Start typing or paste text.
> The text cursor is still displayed flashing in the normal place
> but whatever you type nothing appears on screen.

I'm not *totally* sure if this is the same problem, but I run into
problems sometimes where all of a sudden Firefox does the above.

I open about:config and toggle:

accessibility.typeaheadfind

....and Firefox behaves normally. Sometimes this is not enough and I have
to restart the browser.

> It is now possible to have a text cursor ( | style)
> flashing on non-editable text.

What is the current state of these two configuration entries at the time
of your "problem?":

accessibility.browsewithcaret
accessibility.warn_on_browsewithcaret

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

-Lost wrote:
> Response from Paul :
>
>> 1. Load page with single line textboxes
>> http://www.csse.monash.edu.au/~jwb/c...wwwnewword.cgi
>> 2. Click in a textbox
>> 3. Start typing or paste text.
>> The text cursor is still displayed flashing in the normal place
>> but whatever you type nothing appears on screen.
>
> I'm not *totally* sure if this is the same problem, but I run into
> problems sometimes where all of a sudden Firefox does the above.
>
> I open about:config and toggle:
>
> accessibility.typeaheadfind
>
> ...and Firefox behaves normally. Sometimes this is not enough and I have
> to restart the browser.
>
>> It is now possible to have a text cursor ( | style)
>> flashing on non-editable text.
>
> What is the current state of these two configuration entries at the time
> of your "problem?":
>
> accessibility.browsewithcaret
> accessibility.warn_on_browsewithcaret

Er, well I have to admit that I got lost at "about:config"
but I _did_ find that I had "Always use cursor keys to navigate within
pages" set. I certainly hadn't intentionally set that so I guess it
a) turned itself on during an update or b) I accidentally hit a
short-cut key of some sort. I use the Japanese IME so I do use a lot
of functionkeys / weird key combinations so that could be possible.

That fixed the text cursor, I'll have to see whether the textbox
behaviour has improved or not.

Paul wrote:
> Er, well I have to admit that I got lost at "about:config"

I'm an idiot. I had stuck "about:config" in the _search box_
when I meant to put it in the _address bar_.