#2858 closed defect (fixed)
Editor2: focus issues on IE and FF
Reported by: | alex | Owned by: | liucougar |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Editor | Version: | 0.4.2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The editor widget experience is significantly degraded in Trunk vs. 0.4.2. One of the biggest issues is incorrectly managing focus().
This proceedure shows the difference:
- Open the primary Editor2 test page ("test_Editor2.html") on both Trunk and 0.4.2.
- if it's not already created, create the first editor instance
- move cursor to the beginning of the text in the editor
- hit "enter"
On 0.4.x, the page does not "jump" or otherwise affect the scroll position. On Trunk, focus is set to the caret location, causing the page to (incorrectly) scroll. This is disorienting and creates a highly sub-optimal experience.
Note: See
TracTickets for help on using
tickets.
It's much worse than I thought. In many cases, the focus issues render the editor entirely unusable.
Repeating the above procedure, then moving the cursor to the end of the text block and hitting "enter" multiple times scrolls the entire page to the end of the editable area. This is hugely problematic. I'm raising this issue to a "blocker". The entire editor is unusable and is not currently suitable for porting into Dijit.