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
Following up on #8282, scroll-driven animation primitives like view() are useful for any scroll-related behavior, such as setting view-transition-name only when an element is in the viewport.
However, when implementing a precise user-experience, the fact that view() doesn't account for ink overflow leaves some inaccuracies - it's impossible to precisely tune the behavior such that it will be different when the entire element (including its ink overflow is within/outside the viewport).
Using a timeline-range for it might be useful, though we have to take into account that ink overflow is somewhat platform specific.
The text was updated successfully, but these errors were encountered:
Following up on #8282, scroll-driven animation primitives like
view()
are useful for any scroll-related behavior, such as settingview-transition-name
only when an element is in the viewport.However, when implementing a precise user-experience, the fact that
view()
doesn't account for ink overflow leaves some inaccuracies - it's impossible to precisely tune the behavior such that it will be different when the entire element (including its ink overflow is within/outside the viewport).Using a timeline-range for it might be useful, though we have to take into account that ink overflow is somewhat platform specific.
The text was updated successfully, but these errors were encountered: