-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move LayoutObject ScrollIntoView to their own file
These methods don't belong in LayoutObject/LayoutBox. Since we now have scroll_into_view.cc these methods can be made into free-standing functions. We also improve handling cases where the scroll is prevented from bubbling. The LayoutBox version was simply a helper used by LayoutObject so this now becomes an implementation detail. Its one other caller was LayoutBox::Autoscroll. Autoscroll is used when drag and drop or selecting near a scroller's edge. The only difference between the two calls is that LayoutObject sets up a "sequenced scroll" which is used to animate multiple scrollers. Since Autoscroll doesn't use an animation this change is a no-op. PS2 moves the methods into scroll_into_view.cc. Compare PS2 to latest PS to see new diffs. Bug: 1296183 Change-Id: I62d3a6aff34815f8d8cb8e0688c05a43a1460932 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3615931 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1001017}
- Loading branch information
Showing
19 changed files
with
301 additions
and
255 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.