You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ViewTimelines depend on the size of the scrollport, and in cases where that is the root viewport, this is a dynamic value that may change, and when it changes this causes a visual jump in animations.
This causes a visual nuisance that is avoided when authors use JS-based polyfills by using either the small or large viewport units, but it's currently not possible in the native implementation.
So, proposing to allow authors to specify whether to use small/large viewport units, which will only take effect when used with the root scroller.
Adding a new property to ViewTimelineOptions, (name TBB) unit-size with values small, large, and auto.
While I can calculate the difference between the large and small viewports and adjust the offsets dynamically based off of that, there’s also the issue that the origin of the viewport relative to the entire screen changes as the viewport size changes. So ideally, you’d have adjust a bit at the top and bit at the bottom in order to get non-jumpy behavior.
I think you can get to it using the new safe-area-max-inset-bottom but I have not dug into that (yet).
ViewTimelines depend on the size of the scrollport, and in cases where that is the root viewport, this is a dynamic value that may change, and when it changes this causes a visual jump in animations.
This causes a visual nuisance that is avoided when authors use JS-based polyfills by using either the small or large viewport units, but it's currently not possible in the native implementation.
So, proposing to allow authors to specify whether to use small/large viewport units, which will only take effect when used with the root scroller.
Adding a new property to
ViewTimelineOptions
, (name TBB)unit-size
with valuessmall
,large
, andauto
.cc @bramus @flackr @fantasai
The text was updated successfully, but these errors were encountered: