Property tree's current scroll offset might be set beyond the scroll limits |
||
Issue descriptionIt's possible for PropertyTree's current scroll offset to be beyond the scroll limits when it's not supposed to. https://cs.chromium.org/chromium/src/cc/trees/property_tree.h?l=422&gs=kythe%253A%252F%252Fchromium%253Flang%253Dc%25252B%25252B%253Fpath%253Dsrc%252Fcc%252Ftrees%252Fproperty_tree.h%2523eUELx22KMG7VIZQc7wOOhRqGKmo9nEhczdqO%25252F5YqLz8%25253D&gsn=current_scroll_offset&ct=xref_usages
,
Sep 29
Can you provide more information? When are you seeing this behavior? Is it causing issues?
,
Sep 29
This problem isn't causing issues. I discovered it when working on this CL for adding overscroll to the property tree: https://chromium-review.googlesource.com/c/chromium/src/+/1094097 I wanted to add a DCHECK to the CL to make sure that the scroll offset isn't set beyond the limits when overscroll is disabled, but the DCHECK kept failing. After some investigation, I discovered that the scroll offset would get set beyond the limits with and without my changes. It's not causing issues right now so this is P3, but it's something that would be good to fix.
,
Oct 1
Does it happen on all scrollers or only in specific scenarios? Can you provide a testcase and instructions on how to hit the DCHECK?
,
Oct 2
|
||
►
Sign in to add a comment |
||
Comment 1 by enne@chromium.org
, Sep 28Status: Available (was: Untriaged)