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
When reducing viewport width and crossing a breakpoint value boundary, an autoplay value defined in a breakpoint will not update from autoplay false, to a number value eg. autoplay: 4000;
I tested this with a very high number for autoplay ie 100000 instead of false to see what happens.
In that scenario when decreasing the browser width and crossing into a breakpoint that's using autoplay: 4000 the new autoplay value is not used / updated until the autoplay value from the higher breakpoint is "complete". So in this scenario you'd have to wait 100000 after crossing the boundary before the new value of 4000 starts being used.
I can deduce from this the new breakpoint's autoplay value needs updating on the leading edge immediately when crossing from a higher breakpoint to a lower one, rather than on the trailing edge.
I will add a reduced test case on codepen for this later.
The text was updated successfully, but these errors were encountered:
When reducing viewport width and crossing a breakpoint value boundary, an autoplay value defined in a breakpoint will not update from
autoplay false
, to a number value eg.autoplay: 4000;
I tested this with a very high number for autoplay ie
100000
instead offalse
to see what happens.In that scenario when decreasing the browser width and crossing into a breakpoint that's using
autoplay: 4000
the new autoplay value is not used / updated until the autoplay value from the higher breakpoint is "complete". So in this scenario you'd have to wait100000
after crossing the boundary before the new value of4000
starts being used.I can deduce from this the new breakpoint's autoplay value needs updating on the leading edge immediately when crossing from a higher breakpoint to a lower one, rather than on the trailing edge.
I will add a reduced test case on codepen for this later.
The text was updated successfully, but these errors were encountered: