Summary: | [Qt] Dragging within webkit with a drag created via Javascript ends up misinterpreting the data | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | andy.shaw | ||||||||||
Component: | WebCore Misc. | Assignee: | QtWebKit Unassigned <webkit-qt-unassigned> | ||||||||||
Status: | RESOLVED FIXED | ||||||||||||
Severity: | Normal | CC: | commit-queue, kling | ||||||||||
Priority: | P2 | Keywords: | Qt, QtTriaged | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||||
Hardware: | All | ||||||||||||
OS: | All | ||||||||||||
Attachments: |
|
Created attachment 60223 [details]
Propsoed patch
Confirmed on ToT + current 4.7. We only treat "text/plain" as UTF-16 text right now. Created attachment 60247 [details]
Proposed patch (trunk)
Comment on attachment 60247 [details]
Proposed patch (trunk)
r- after discussion with Simon. ClipboardQt needs more robustness in both getData() and setData() if we're to support arbitrary mimetypes. New patch coming in a bit.
Created attachment 61231 [details]
Proposed patch v2
Comment on attachment 61231 [details] Proposed patch v2 Clearing flags on attachment: 61231 Committed r63089: <http://trac.webkit.org/changeset/63089> All reviewed patches have been landed. Closing bug. |
Created attachment 60222 [details] Example HTML reproducing the problem Dragging within webkit with a drag created via Javascript ends up misinterpreting the data, in the example attached if you drag from the drag area to the drop area then you will see that the data looks like it has been converted incorrectly.