Bug 58732 – [Qt] Unable to DnD content in certain websites

• Status: RESOLVED
• Resolution: INVALID
• Component: WebCore Misc.

[Aparna Nandyal]

Steps to reproduce:
1. Open QtTestBrowser
2. Launch http://www.webreference.com/programming/javascript/dragdropie/Example2.htm or http://html5demos.com/drag-anything
3. Try to drag and drop content as mentioned

Expected results: 
It works as mentioned in the website

Actual result:
undefined is shown instead of dropped content.

[Aparna Nandyal]

Analysis:
Refer http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#dnd 

As per the document, when getData is called:
If format equals "text", change it to "text/plain".
If format equals "url", change it to "text/uri-list"

Few other webkit ports like Win, chromium adhere to this. 

That is when setData is used with say text/plain or text/uri-list and getData is called with text or url (or vice versa), DnD fails. In the current code, it does not recognize "text" = "text/plain" and "url" = "text/uri-list"

[Aparna Nandyal]

Created attachment 89930 [details]
Patch for review

Fixes the problem. Qt DnD has a problem hence unable to write an auto test.

[Eric Seidel (no email)]

Comment on attachment 89930 [details]
Patch for review

I'm sure this is testable.  Do we have tests which cover this?  If not, we need to add some.  If we do, we should be updating the expected results.

[Eric Seidel (no email)]

Can you please refernece the Qt DnD bug in your ChangeLog if you're prevented in adding tests by it?

[Yael]

(In reply to comment #4)
> Can you please refernece the Qt DnD bug in your ChangeLog if you're prevented in adding tests by it?

It isn't a Qt bug that prevents us from using auto tests for DnD.
I tried to explain the issue in https://bugs.webkit.org/show_bug.cgi?id=31332#c7 and you can see some more discussion in that bug.

[Jocelyn Turcotte]

=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.