<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Use Blob URL instead of webkit-fake-url when pasting an image and no URL is available"
href="https://bugs.webkit.org/show_bug.cgi?id=49141#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Use Blob URL instead of webkit-fake-url when pasting an image and no URL is available"
href="https://bugs.webkit.org/show_bug.cgi?id=49141">bug 49141</a>
from <span class="vcard"><a class="email" href="mailto:aleksander@nowodzinski.pl" title="Aleksander Nowodziński <aleksander@nowodzinski.pl>"> <span class="fn">Aleksander Nowodziński</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=49141#c23">comment #23</a>)
<span class="quote">> If the plan is to use Blob URLs instead of data-uris (like Firefox), will
> there be a way to convert them to data uris like Chrome does? That's main
> use case here: pasting an image into a WYSIWYG editor and being able to save
> the image.</span >
So +1.
The point is that whatever the output in DOM (webkit-fake-url or data-uri in the <img> tag), an easy way to obtain the data-uri in the paste event is needed, so the content that has been pasted in the WYSIWYG editor can be i.e. uploaded to the server.
At this moment, the webkit-fake-url gives no way to the developers to obtain the actual image and do anything with it. Users paste/drag&drop tons of content into WYSIWYG (contenteditable) editors like that.</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>