Closed
Bug 610844
Opened 15 years ago
Closed 15 years ago
Using the Japanese IME in the save box and clicking outside the box will not commit the text
Categories
(Firefox :: File Handling, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: nhirata, Unassigned)
Details
(Whiteboard: [4b7])
Attachments
(1 file)
|
232.71 KB,
image/png
|
Details |
1. go to file -> save
2. type in "nihongo" do not hit return
3. hit space twice
4. click on the desktop
5. click back to the save as dialog
Expected: Japanese IME is committed
Actual: Japanese IME is not committed
6. click cancel
7. bring back the save as dialog
Expected: the Filename does not have "nihongo" listed
Actual: the Filename still does have "nihongo" listed and underlined.
| Reporter | ||
Comment 1•15 years ago
|
||
Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Updated•15 years ago
|
Whiteboard: [4b7]
Comment 2•15 years ago
|
||
Confirmed on Windows XP+IME2003 and ATOK2006 either.
*does not happens on Windows7
Comment 3•15 years ago
|
||
This isn't a bug.
The common dialog's widgets are native widgets. Each native widgets shares an IME context in top level window, however, the composition transaction continues on the new focused widget. This is a natural behavior on Windows Vista and earlier (I'm not sure why Win7 changes the behavior).
On the other hand, our editors are not native widgets. They share an IME context in each top level window, this is same, however, some resources in our XP level code share the IME related information in process level. Therefore, when focus is switching, we need to commit the composition string forcibly.
This is the reason of the difference between native widgets and our widgets.
Note that after bug 569023, our editor doesn't commit the composition string when it loses focus and another application (including desktop) gets focus. When another our widget gets focus, the composition string is committed forcibly on the old focused editor.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•