[Webkit-unassigned] [Bug 6839] New: shouldInsertNode delegate returning NO shouldn't necessairly cancel a drag and drop

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Thu Jan 26 07:20:14 PST 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=6839

           Summary: shouldInsertNode delegate returning NO shouldn't
                    necessairly cancel a drag and drop
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTML Editing
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: duncan at mclink.it


Editing delegate methods exist both to forbid some behaviours and to replace
built-in behaviours with more application specific ones.

Specifically, when performing a drag and drop into an editable area, this
delegate method will be called:

- (BOOL)webView:(WebView *)webView shouldInsertNode:(DOMNode *)node
replacingDOMRange:(DOMRange *)range givenAction:(WebViewInsertAction)action

if the delegate returns NO, the drop won't be accepted and the system will
animate the dropped object returning where it came from.

This is the correct behaviour if the delegate wants to forbid the drop, but if
the delegate wants to replace it with a different one, in fact it does want the
drop to be accepted, albeit providing its own custom implementation of the
functionality.

The delegate method above should be extended to reflect this.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list