Opened 15 years ago
Closed 15 years ago
#5712 closed Bug (fixed)
Chrome: enter in pre causes problems
| Reported by: | Tobiasz Cudnik | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.3 |
| Component: | UI : Enter Key | Version: | SVN (CKEditor) - OLD |
| Keywords: | Chrome Confirmed | Cc: | WebSpellChecker.net |
Description
Chrome: enter in pre causes problems
Reproduce
- Use following content:
<pre>f^oo</pre>
- Hit enter to create new line.
Result
- Instead of new line, space is created.
- Editor looses focus.
- After switching to source view and back to RTE, newline is there.
Expected
- Carret is moved to new line.
- Focus remains inside the editor.
Change History (11)
comment:1 Changed 15 years ago by
| Component: | General → UI : Enter Key |
|---|---|
| Keywords: | Confirmed added |
| Version: | → SVN (CKEditor) |
comment:2 Changed 15 years ago by
| Cc: | WebSpellChecker.net added |
|---|
comment:4 Changed 15 years ago by
We have dicovered that this problem is hard-to-resolve quickly. We propose to disable SCAYT for PRE for all browser except FF. We have implemented this in core, but still need to prepare update to plug-in to fire scayt.refresh() on format change.
comment:5 Changed 15 years ago by
What exactly does "disable SCAYT for PRE" means? That sounds strange for us, we don't understand the difficulty for you behind this.
comment:6 Changed 15 years ago by
We have reviewed the problem and found that the reason was in CSS style. The problem fixed by updated of SCAYT core on SpellChecker.net side.
comment:8 Changed 15 years ago by
Please try to clear cache, exit browser and then try again. Seems that just clearing cache is not enough.
comment:9 Changed 15 years ago by
Replying to garry.yao:
The bug is still reproducible on trunk.
I have newline created, but editor looses focus.
comment:11 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fix is confirmed on trunk.
Affected by SCAYT.