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
A fun one! Thanks to this Chromium bug, in combination with these parseInts, you can end up in a situation where ember-collection slowly scrolls upwards with no user input.
To reproduce, take a look at the scroll position demo in Chrome, zoom in to 110%, and scroll down a bit.
If you land on anything other than a nice round number, you'll end up in a feedback loop between the parseInt truncation in the addon code and the rounding glitch in the browser that inexorably drags you back to the top of the collection.
The text was updated successfully, but these errors were encountered:
The problem with removing the parseInts is right now I think that would break the layouts since layout-bin-packer doesn't deal w/ floating point numbers... but I guess it could. This needs more investigation.
A fun one! Thanks to this Chromium bug, in combination with these
parseInt
s, you can end up in a situation whereember-collection
slowly scrolls upwards with no user input.To reproduce, take a look at the scroll position demo in Chrome, zoom in to 110%, and scroll down a bit.
If you land on anything other than a nice round number, you'll end up in a feedback loop between the
parseInt
truncation in the addon code and the rounding glitch in the browser that inexorably drags you back to the top of the collection.The text was updated successfully, but these errors were encountered: