On Wed Feb 4 20:44:44 2009 PST, noel wrote:
> OK, so I asked you to mull over this some more and write some test
> js to see how it feels for the api user perspective. How did that
> go exactly?
Very straightforward. The event handler looks something like:
------------------------
if (isFirefox) {
if (isDrop || !accept) {
evt.stopPropagation();
}
} else if (isSafari || isIE) {
if (accept && !isDrop) {
evt.returnValue = false;
}
}
------------------------
Given that you have to write some browser-specific code anyway for v2, in order
to attachEvent/addEventListener, then I think it's quite cheap, and simple.
> Chatting to you, you mentioned you'd maybe retract this CL. I can
> see go arguments for and against. So how about this ...
>
> Provide both methods on the API - setDragCursor *and* acceptDrag ?
I've changed this CL to not remove the acceptDrag method, so that Gears indeed
provides both. Eventually we should really decide on one or the other, but we'll
punt that decision to probably the same time we decide on v1 versus v2.
--
To respond, reply to this email or visit http://mondrian.corp.google.com/9955210
