1.0.0-beta.2

[niklasramo]

Bug fixes:

• In the 1.0.0-beta.1 version we introduced a performance optimization to element width/height calculcation, but the optimization mistakenly included the scrollbar size for content and padding widths/heights. Additionally, the optimization produces a bit less accurate values than getBoundingClientRect(), which is otherwise okay, but it also causes the getRect() method to return data where the offsets are not fully in sync with the dimensions. And that is not okay. So I decided to drop it for now and think about it a bit more.
• Fixed an issue with getHeight() method where it would not always subtract the scrollbar correctly.
• You could consider this a feature instead of a bug fix, but let's call it what it really is. Previously, if the element had a scrollbar with a subpixel width/height (possible in Chromium-based browsers) the final width/height calculation for padding and content sizes would be incorrect. Now that's fixed. I think we got this done in nicely performant way without needing to resolve to adding test elements in the DOM (which would have sucked big time). It turns out that subpixel scrollbars vary in behaviour between devices/browsers, which means that we can't use the same assumption for all cases, which also means we have to test the behaviour in the DOM to get accurate results :( I built a cache system to store the corresponding real values for the values that window.getComputedStyle() reports. This way we can keep the DOM testing at minimum and only test when there actually is a custom subpixel scrollbar value defined. Closes More accurate scrollbar width/height. #22