Opened 16 years ago
Closed 16 years ago
#3835 closed Bug (fixed)
element path not refreshed on 'newpage'
| Reported by: | Garry Yao | Owned by: | Garry Yao |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.0 |
| Component: | General | Version: | |
| Keywords: | IE Safari Confirmed Review+ | Cc: |
Description
Reproducing Procedures
- Open the replace by class example page;
- Click on 'New Page' button to clear all content;
- Exptected Result: Element path show nothing;
- Actual Result: Element path is still showing the old selection path.
Attachments (2)
Change History (8)
Changed 16 years ago by
| Attachment: | 3835.patch added |
|---|
comment:1 Changed 16 years ago by
| Keywords: | Review? added |
|---|---|
| Status: | new → assigned |
comment:2 Changed 16 years ago by
| Keywords: | Review- added; Review? removed |
|---|
- I'm not able to confirm this bug in IE, only with Safari.
- The patch is broken, and actually we can see a "?" being added at the start of _source/core/dom/window.js.
- It's not clear how the changes on _source/plugins/wysiwygarea/plugin.js could help on this fix.
- There is no changelog.
comment:3 Changed 16 years ago by
| Keywords: | Safari added; Webkit removed |
|---|
Btw, the correct keyword is "Safari", not "WebKit".
Changed 16 years ago by
| Attachment: | 3835_2.patch added |
|---|
comment:4 Changed 16 years ago by
| Keywords: | Review? added; Review- removed |
|---|
Replying to fredck:
- I'm not able to confirm this bug in IE, only with Safari.
Sorry, only IE8 is affected.
- It's not clear how the changes on _source/plugins/wysiwygarea/plugin.js could help on this fix.
Yes, explaination should be putted here: any error that happened inside 'selectionChange' event handler will break other listeners and error is been swallowed by a try/catch in selection plugin. So here elementpath refreshing as a handler is broken by error generated by wysiwyg plugin.
comment:5 Changed 16 years ago by
| Keywords: | Review+ added; Review? removed |
|---|
Well... I'm still not able to reproduce it with IE, not even IE8. That fix doesn't hurt, and Safari got fixed.
Note: See
TracTickets for help on using
tickets.
