#7696 closed Bug (expired)
IE6: Throwing an error when we open Table dialog on Pasted tables from word
Reported by: | Satya Minnekanti | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Plugin : Paste from Word | Version: | 3.5.3 |
Keywords: | IBM | Cc: | Damian, James Cunningham, Teresa Monahan |
Description
To reproduce the defect:
- set pasteFromWordRemoveFontStyles & pasteFromWordRemoveStyles set to true in editor config.
- Copy the table from attached word doc and paste in to editor using Paste from Word dialog.
- Click in to any table cell & open Table dialog by clicking on Table Properties option in context menu.
Expected Result: Table Properties dialog opens with out throwing any errors.
Actual Result: Table Properties dialog opens but it throws an error and Error is "null is null or not an object".
Attachments (1)
Change History (9)
Changed 14 years ago by
Attachment: | empty table.doc added |
---|
comment:1 follow-up: 2 Changed 14 years ago by
Cc: | damo,jamescun,tmonahan → damo, jamescun, tmonahan |
---|---|
Status: | new → pending |
comment:2 Changed 14 years ago by
Replying to j.swiderski:
I was not able to reproduce the issue. I have followed your scenario but no error was thrown.
Can you still reproduce this issue in the latest demo version?
I was able to reproduce the issue if i have pasted the table using Ctrl + v instead of using Paste from Word dialog and using above config settings
comment:3 Changed 14 years ago by
Status: | pending → confirmed |
---|
True from CKEditor version 3.5.3 revision [6478]
comment:4 Changed 14 years ago by
Error: null is null or not an object.
Location: /_source/plugins/table/dialogs/table.js
Line: 72; ranges = selection.getRanges()
comment:5 Changed 14 years ago by
Status: | confirmed → pending |
---|
Seems like this bug expired on trunk, can you confirm?
comment:7 Changed 14 years ago by
Resolution: | → expired |
---|---|
Status: | pending → closed |
comment:8 Changed 11 years ago by
Component: | General → Plugin : Paste from Word |
---|
I was not able to reproduce the issue. I have followed your scenario but no error was thrown.
Can you still reproduce this issue in the latest demo version?