Opened 12 years ago
Closed 12 years ago
#9257 closed Bug (duplicate)
[Safari 5] Pasted data are wrapped with styling <div>
Reported by: | Piotrek Koszuliński | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 4.0 |
Keywords: | Cc: |
Description
- Open any replacebyclass sample.
- Delete everything.
- Write one paragraph of text.
- Select all and copy.
- Press ctrl+v, enter few times.
- Switch to source mode.
Editor content:
<p>test.</p> <div style="font-family: Arial, Verdana, sans-serif; font-size: 12px; color: rgb(34, 34, 34); background-color: rgb(255, 255, 255); "> <p>test.</p> <div style="font-family: Arial, Verdana, sans-serif; font-size: 12px; color: rgb(34, 34, 34); background-color: rgb(255, 255, 255); "> <p>test.</p> <div style="font-family: Arial, Verdana, sans-serif; font-size: 12px; color: rgb(34, 34, 34); background-color: rgb(255, 255, 255); "> <p>test.</p> <div style="font-family: Arial, Verdana, sans-serif; font-size: 12px; color: rgb(34, 34, 34); background-color: rgb(255, 255, 255); "> <p>test.</p> </div> </div> </div> </div>
This issue is reproducible on v3 as well.
Chrome wraps pasted content in styling span only when "styling" contexts of copied content origin and paste place differ. It looks like Safari unfortunately always does this.
Change History (5)
comment:1 Changed 12 years ago by
Milestone: | CKEditor 4.0 |
---|
comment:2 Changed 12 years ago by
I cannot reproduce this in CKEditor 4.0 DEV (revision 20c9d6f) and Chrome v22...
comment:3 Changed 12 years ago by
Summary: | [Safari] Pasted data are wrapped with styling <div> → [Safari 5] Pasted data are wrapped with styling <div> |
---|
Because that's Safari's 5 problem. I believe that it was occurring in old version of Chrome, but was fixed in Webkit's version released between Safari 5 and Safari 6 (so it's also fixed in Safari 6).
comment:4 Changed 12 years ago by
comment:5 Changed 12 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
DUP od #7146
@Reinmar I have moved your comment to that ticket.
We'll be very hard to handle this right now.