723810 - nsIWidget::OnIMETextChange() is not called for the document with designMode=on

Status: RESOLVED DUPLICATE of bug 805766

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Alex Pakhotin (:alexp)]

As discussed with Masayuiki in bug 721393:
=========
> When typing text in a document/IFRAME with designMode=on there are no
> nsWindow::OnIMETextChange() calls, unlike when editing a regular INPUT
> box, or a DIV with contentEditable=true. Do you know why is that?

Oh, I didn't realize it. It should be called on designMode editor too. Could you file a bug for it and CC me? I guess that it's failed to listen to DOM mutation events. Document nodes are responsible for handling all events if in designMode. This is the most different point from other editors (Element nodes are responsible for all events for other editors).
=========

Comment 1

[Alex Pakhotin (:alexp)]

Masayuiki, how difficult would it be to fix this? I know you are busy, but if you could give any hints - where to look at - that would help.
Thanks.

Comment 2

[Alex Pakhotin (:alexp)]

Oh, sorry for misspelling your name again - I keep typing an extra letter. :-\

Comment 3

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

I'm not sure.

nsTextStateManager looks like it's handling designMode editor when it was designed at least...
http://mxr.mozilla.org/mozilla-central/source/content/events/src/nsIMEStateManager.cpp#472

I think you should confirm if it succeeds to install the mutation observer, first.
nsIMEStateManager::OnTextStateFocus() is called when editor gets focus. Then, nsIWidget::OnIMEFocusChange() is called. If it returns NS_OK, nsTextStateManager::Init() tries installing the observer.

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

(In reply to Alex Pakhotin (:alexp) from comment #2)
> Oh, sorry for misspelling your name again - I keep typing an extra letter.
> :-\

Don't mind, other language's name are very difficult for everyone. I often do it too.

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Wow, I forgot this bug. I guess that I fixed this already in bug 805766. Please reopen if I'm wrong.