diff options
| author | thakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-13 03:44:31 +0000 |
|---|---|---|
| committer | thakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-13 03:44:31 +0000 |
| commit | dd6afcae7bffda8cf9a70e01191f0a08e5a0f7e3 (patch) | |
| tree | 38c47aa3ba8908b05d8010f4f0853f1a71af4ac0 /content/renderer/renderer_webidbcursor_impl.cc | |
| parent | 48352a17719783565d2e7c97de5eeddd6b0e9b8d (diff) | |
| download | chromium_src-dd6afcae7bffda8cf9a70e01191f0a08e5a0f7e3.zip chromium_src-dd6afcae7bffda8cf9a70e01191f0a08e5a0f7e3.tar.gz chromium_src-dd6afcae7bffda8cf9a70e01191f0a08e5a0f7e3.tar.bz2 | |
Pipe "is pinned to left/right", "has horizontal/vertical scrollbar",
"number of wheel handlers" to browser process.
We want to implement two-finger-swipe for history like safari does on
os x lion. The way this works is:
* If a page has no horizontal scrollbars, or the page is all the way
to the left, scrolling to the left will go back in history instead.
* Same for right/forward.
Hence, this data needs to be available in the browser process.
This is modelled after the WebKit2 functions
WKPageIsPinnedToLeftSide(), WKPageIsPinnedToRightSide(),
WKPageHasHorizontalScrollbar(), and
webPageProxy::willHandleHorizontalScrollEvents().
Depends on https://bugs.webkit.org/show_bug.cgi?id=66094
BUG=90228
TEST=No observable effect yet
Review URL: http://codereview.chromium.org/7635011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96670 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/renderer_webidbcursor_impl.cc')
0 files changed, 0 insertions, 0 deletions