| commit | 9acc6ca9c517196ba49121537effec44c54b3931 | |
| author | Julien "_FrnchFrgg_" RIVAUD <frnchfrgg@free.fr> | |
| Sat, 8 Aug 2009 12:39:47 +0000 (8 14:39 +0200) | ||
| committer | Julien "_FrnchFrgg_" RIVAUD <frnchfrgg@free.fr> | |
| Sat, 8 Aug 2009 14:10:10 +0000 (8 16:10 +0200) | ||
| tree | f30cd79371ec552439062c77477cbd1cbbb30dfa | treesnapshot (tar.gz zip) |
| parent | c9cb828a1eccea7550e8ea3ee36ebd016af99590 | commitdiff |
Update drag'n'drop code to match new firefox API
The API for tab drag'n'drop changed for Firefox 3.5 where canDrop() is
no longer used; provide a suitable _setEffectAllowedForDataTransfer()
instead.
The vanilla _setEffectAllowedForDataTransfer() tries to detect if the
dragged tab has been moved enough to justify a drag, but only verifies
the horizontal movement. We thus munge the screenX member of the event
before calling the function so that it thinks the tab has moved a lot.
Thanks to David Martin for the bug report
The API for tab drag'n'drop changed for Firefox 3.5 where canDrop() is
no longer used; provide a suitable _setEffectAllowedForDataTransfer()
instead.
The vanilla _setEffectAllowedForDataTransfer() tries to detect if the
dragged tab has been moved enough to justify a drag, but only verifies
the horizontal movement. We thus munge the screenX member of the event
before calling the function so that it thinks the tab has moved a lot.
Thanks to David Martin for the bug report
| chrome/content/browser.xul | diffblobblamehistory |