299519 - Mouse clicks may leave inline input areas in invalid state

Status: RESOLVED WORKSFORME

(Camino Graveyard :: HTML Form Controls, defect, P2)

Description

[Alexey Proskuryakov]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; ru-ru) AppleWebKit/312.1 (KHTML, like Gecko) Safari/312
Build Identifier: 2005070108 (v0.9a1+)

If one uses mouse with an input method utilizing inline input, it's easy to bring text control into an 
invalid state - in this example, it's impossible to clear it.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.google.ru/advanced_search
2.Using Kotoeri (or any other input method that uses inline input), type something in the first text field 
("with all of the words").
3. Click in this field (after the typed text)
4. Continue typing
  The previously-typed text disappears, and a new inline input area is created
5. Again, click in this field (after the typed text)
6. Continue typing
  This time, the previously-typed text doesn't disappear
7. Without confirming the inline input, click in the next text field
8. Click back in the first one, select its contents (mouse double-click or Cmd+A)
9. Press backspace to delete the selection
Actual Results:  
Nothing happens. Besides, the state of inline input was visually incorrect at previous steps - inability to 
erase the text is just the most obvious problem.

Comment 1

[Jasper]

Could somebody update this report.

Comment 2

[Simon Fraser [no longer active]]

I would guess that this still happens.

Comment 3

[Simon Fraser [no longer active]]

Yes, still happens.

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

IME bugs moved to 1.1 :-(

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Moving IME-related bugs to Camino 1.2 :(

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Mass un-setting milestone per 1.6 roadmap.

Filter on RemoveRedonkulousBuglist to remove bugspam.

Developers: if you have a patch in hand for one of these bugs, you may pull the bug back to 1.6 *at that point*.

Comment 7

[Stuart Morgan]

This appears to be fixed in the latest trunk builds.