Summary: | [chromium] Add support for non-text/non-URL types in event.dataTransfer | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Daniel Cheng <dcheng> | ||||||
Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | rniwa, tony | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | PC | ||||||||
OS: | OS X 10.5 | ||||||||
Bug Depends on: | 42121, 44914, 44917, 44992 | ||||||||
Bug Blocks: | |||||||||
Attachments: |
|
Description
Daniel Cheng
2010-08-26 15:47:18 PDT
Created attachment 65977 [details]
Patch
The associated Chromium-side patch is at http://codereview.chromium.org/2868069/show. The Windows side for the Chromium patch is more or less complete (ClipboardWin::WriteData does need to be updated though). I am working on merging in the changes I've made to the Mac/Linux side. I'm currently not sure how to land this patch once it gets past review; there's some dependencies from the browser on renderer side changes, and vise versa. There's also what (I suspect) is a layering violation in the EventSender/WebViewHost changes, so any suggestions on how to resolve that would be welcome. Comment on attachment 65977 [details]
Patch
dcheng and I discussed various ways to break this patch into smaller pieces. r- for now, since this is pretty much unreviewable and not landable anyway (it would break chromium since it's an api change).
Does this bug still exist? The various bits that this involves have landed and been in tree for some time now. Excellent! |