RESOLVED CONFIGURATION CHANGED 11697
Extra whitespace added when pasting into editable inline-block DIV element 
https://bugs.webkit.org/show_bug.cgi?id=11697
Summary Extra whitespace added when pasting into editable inline-block DIV element
Mark Rowe (bdash)
Reported 2006-11-27 02:16:38 PST
Steps to reproduce: 1) Click inside the paragraph of text. Hit Cmd-A to select all of the text. 2) Hit Cmd-V twice to paste the text twice. Note where the second paragraph of text ends up. 3) Hit Cmd-V to paste the text a third time. Boom!
Attachments
Test case (328 bytes, text/html)
2006-11-27 02:17 PST, Mark Rowe (bdash) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1 2006-11-27 02:17:34 PST
Created attachment 11639 [details] Test case
mitz
Comment 2 2006-11-27 10:33:09 PST
On second paste: ASSERTION FAILED: m_parentNode->isContentEditable() || !m_parentNode->attached() (WebCore/editing/AppendNodeCommand.cpp:45 virtual void WebCore::AppendNodeCommand::doApply())
mitz
Comment 3 2007-01-20 23:05:00 PST
I can no longer reproduce on TOT.
Mark Rowe (bdash)
Comment 4 2007-01-20 23:17:38 PST
The behaviour has changed since this bug was initially opened. What happens now is that a bunch of extra whitespace (roughly 8 or 10 spaces) is added to the end of the content on every paste. The result is that hitting paste multiple times results in your pasted text being broken up by blocks of spaces.
Ahmad Saleem
Comment 5 2022-06-30 16:43:17 PDT
I am able to reproduce this in Safari 15.5 on macOS 12.4. All other browsers such as Chrome Canary 105 and Firefox Nightly 104 does not add any extra spaces at the end as mentioned in Comment 04. Thanks!
Radar WebKit Bug Importer
Comment 6 2022-07-26 19:38:40 PDT
<rdar://problem/97641709>
Ahmad Saleem
Comment 7 2023-02-25 07:56:23 PST
I am not able to reproduce this bug in Safari Technology Preview 164 anymore, it might have been fixed due to HTML Editing changes or Live Range Selection API. Marking this as "RESOLVED CONFIGURATION CHANGED".
Note You need to log in before you can comment on or make changes to this bug.