#12008 closed defect (fixed)
Editor EnterKeyHandling plugin causes IE to crash
Reported by: | Katie Vance | Owned by: | Jared Jurkiewicz |
---|---|---|---|
Priority: | high | Milestone: | 1.7.6 |
Component: | Editor | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Plugin crashes IE when blockNodeforEnter='BR'
Steps to reproduce:
- Open tests\editor\EnterKeyHandling?.html
- In the first editor window, select all the text and delete it.
- Type in anything.
- Select all of your new text and copy and paste a couple of times.
- Hit enter.
IE will crash. The crash may not be a bug in the editor plugin. I've traced it down to the dojo.stopEvent(e); line of the setEditor method of the plugin. Further debugging will need to be done to determine the cause of the IE crash.
This happens on IE6-8.
Change History (16)
comment:1 Changed 10 years ago by
Owner: | Jared Jurkiewicz deleted |
---|
comment:2 Changed 10 years ago by
comment:4 Changed 10 years ago by
It's crashing for me on line 398 of range.js. When we try to access htmlText of the range. It looks as though the range is wrong because in the debugger the text indicates there was some kind of error.
comment:6 Changed 10 years ago by
comment:7 Changed 10 years ago by
The problem seems to be an issue with placing an empty text node at the beginning of a new range. Once we add the new range to the selection we are setting IE up to crash. (Not sure why) It will however work the very first time we hit enter and do not do any copy and pasting. However, subsequent times after that, IE will crash. We can work around the issue by not placing empty text nodes into the dom, however, without doing so I have not been able to find a way to place the caret on the next line (after the <BR>). Any ideas?
comment:8 Changed 10 years ago by
Place a text node with a space instead of an empty one, perhaps, and position before that in the case of IE? It introduces an extra space, but I don't know what else to do.
comment:9 Changed 10 years ago by
comment:10 Changed 10 years ago by
Milestone: | tbd → 1.6 |
---|---|
Owner: | set to Jared Jurkiewicz |
comment:11 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:12 Changed 10 years ago by
The above seems to resolve the problem fairly well. As noted, avoid inserting an empty text node, then just clear it after the fact.
comment:15 Changed 6 years ago by
Milestone: | 1.6 → 1.7.6 |
---|
It's crashing in the code where it tries to reposition the cursor in front of the range. Around line 272:
Why, I have no idea.