<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - text/rtf clipboard data is empty (makes TinyMCE and textbox.io require Flash)"
href="https://bugs.webkit.org/show_bug.cgi?id=124391#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - text/rtf clipboard data is empty (makes TinyMCE and textbox.io require Flash)"
href="https://bugs.webkit.org/show_bug.cgi?id=124391">bug 124391</a>
from <span class="vcard"><a class="email" href="mailto:cdumez@apple.com" title="Chris Dumez <cdumez@apple.com>"> <span class="fn">Chris Dumez</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=124391#c4">comment #4</a>)
<span class="quote">> We put the RTF data on the pasteboard but we do not allow WebContent to read
> it at the moment. In PasteboardMac.mm's cocoaTypeFromHTMLClipboardType():
> // Blacklist types that might contain subframe information.
> if (lowercasedType == "text/rtf" || lowercasedType == "public.rtf" ||
> lowercasedType == "com.apple.traditional-mac-plain-text")
> return String();
>
> If you replace with:
> if (lowercasedType == "text/rtf" || lowercasedType == "public.rtf")
> return NSRTFPboardType;
>
> then the test case works.
>
> However, it looks like someone intentionally blacklisted those (likely for
> security reasons) so we'll have to investigate why and how to better deal
> with RTF.</span >
This was done in <a href="https://trac.webkit.org/changeset/115513">https://trac.webkit.org/changeset/115513</a>.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>