diff options
| author | idanan@chromium.org <idanan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-03-26 19:58:51 +0000 |
|---|---|---|
| committer | idanan@chromium.org <idanan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-03-26 19:58:51 +0000 |
| commit | 6c50fc5e707429c227493f565e05fbc1e7a4b9b9 (patch) | |
| tree | ec27981373f21bbc975965c62e488b4275433245 /site_scons/site_tools | |
| parent | 3c8bd9f45bfeb09acc2fbad3407e7b2c14d7c7be (diff) | |
| download | chromium_src-6c50fc5e707429c227493f565e05fbc1e7a4b9b9.zip chromium_src-6c50fc5e707429c227493f565e05fbc1e7a4b9b9.tar.gz chromium_src-6c50fc5e707429c227493f565e05fbc1e7a4b9b9.tar.bz2 | |
Issue 21268: The RemakeSee http://codereview.chromium.org/21268 for the original issue which was partially reverted due to a possible regression. Issue 8819 was created to track the part of the original fix which was reverted.A double-click come as an event which follows a single-click. The core of this change is to makesure that a double-click arrives at the object which handled the single-click which preceeded it.If it does not, then the double-click is transformed into a single-click at the dispatch level.The tricky part is that a single-click and the double-click which follows it may not both be clientor non-client. So, all double-clicks (client or non-client) are now centrally handled and replacedwhen needed by second single-clicks.Note that the behavior which was reverted was to discard a double-click rather than reducing it toa single-click. The bug filed as a regression involved using a double-middle-click as two single-clicks when destroying compressed tabs sequentially.BUG=8819
Review URL: http://codereview.chromium.org/50017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12590 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'site_scons/site_tools')
0 files changed, 0 insertions, 0 deletions