Opened 9 years ago
Closed 9 years ago
#16409 closed defect (invalid)
Editor behaves differently, on IE, when using customized toolbar – as opposed to default toolbar.
| Reported by: | bakbjo | Owned by: | bill |
|---|---|---|---|
| Priority: | undecided | Milestone: | tbd |
| Component: | Editor | Version: | 1.8.0 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Browser IE10/9/8 - OS Win8. Setting up to different “formEditor” widgets on a test page (see code below) – notice how the console output is different when placing the cursor at the end of the test and hitting the enter key.
editor1 onChange handler:
This instance is created from a div directly with default toolbar and plugins
<br />
editor2 onChange handler: <p>
This instance is created from a div directly with default toolbar and plugins
</p><p></p>
Attachments (2)
Change History (3)
Changed 9 years ago by
| Attachment: | formeditor.html added |
|---|
Changed 9 years ago by
comment:1 Changed 9 years ago by
| Component: | Dijit → Editor |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Summary: | Dijit.FormEditor behaves differently, on IE, when using customized toolbar – as opposed to default toolbar. → Editor behaves differently, on IE, when using customized toolbar – as opposed to default toolbar. |
Note: See
TracTickets for help on using
tickets.
This is working as expected, although admittedly confusing. The Editor's default plugin list includes the EnterKeyHandling plugin, which normalizes how the enter key is processed.
In your test case, you are overriding that default list of Editor plugins, and your list omits the EnterKeyHandling plugin.
Perhaps in the future we'll make that EnterKeyHandling code part of the editor, rather than a plugin, so that this confusion doesn't happen.