Bug 294027 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050128 Mnenhy/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050128 Mnenhy/0.7

The editor does not fire an events when, e.g., the current "paragraph mode" is
switched to an ordered list or back again, or the text style is discontinued, or
other such occurences which do not trigger a keypress event.

Extensions may need to monitor such occurences for various purposes, so it
stands to reason that there should be some notification of them. Surely if we
have a 'compose-from-changed' we can have a 'compose-message-changed' event, right?

One could think of such an event which complements keypresses or such an event
which is triggered both when a key is pressed and when the message changes
otherwise.

Reproducible: Always

Steps to Reproduce:
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050128 Mnenhy/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050128 Mnenhy/0.7

The editor does not fire an event when - for example - the current "paragraph mode" is switched to an ordered list or back again, or the text style is discontinued, or other such occurrences which do not trigger a keypress event.

Extensions may need to monitor such occurrences for various purposes, so it stands to reason that there should be some notification of them. Surely if we have a 'compose-from-changed' we can have a 'compose-message-changed' event, right?

One could think of such an event which complements keypresses or such an event which is triggered both when a key is pressed and when the message changes otherwise.

Back to Bug 294027 Comment 0