| commit | afee5c83d34001fc8a5ff9fdcb10ff4c4beb0122 | |
| author | mfomitchev@chromium.org <mfomitchev@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Tue, 28 Jan 2014 01:25:28 +0000 (28 01:25 +0000) | ||
| committer | mfomitchev@chromium.org <mfomitchev@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Tue, 28 Jan 2014 01:25:28 +0000 (28 01:25 +0000) | ||
| tree | d3681d2219892df05f8e220793b5351daaede128 | treesnapshot (tar.gz zip) |
| parent | 78b4ceaa43cb24caa89a2d08ef348b4f20956315 | commitdiff |
The issue was that the window slider was initialized and then immediately quiried if the slide was in progress. It happened to return "yes" in this case, which prevented the OverscrollNavOverlay window from being removed (at least until the user interacted with the screen).
Fixed by making sure WindowSlider::IsSlideInProgress() returns "false" if sliding has never been started.
BUG=336930
Review URL: https://codereview.chromium.org/145293002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247372 0039d316-1c4b-4281-b951-d872f2087c98
Fixed by making sure WindowSlider::IsSlideInProgress() returns "false" if sliding has never been started.
BUG=336930
Review URL: https://codereview.chromium.org/145293002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247372 0039d316-1c4b-4281-b951-d872f2087c98
| content/browser/web_contents/aura/window_slider.cc | diffblobblamehistory |