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
Current bounds have a descriptive API. Usually specifying the element or parent or body is enough. However, the coords API is not good enough. Right now it has a CSS-like model of { top, left, right, bottom }. What if I wanna specify square of [from, to]. Of a specific area. I feel practically top left right bottom is useless unless it can behave exactly like CSS. with percantages, vh, vw, rem, em etc.
Secondly, how do we want to deal with partially overlapping bounds
The text was updated successfully, but these errors were encountered:
Just collecting some ideas here.
Current bounds have a descriptive API. Usually specifying the element or parent or body is enough. However, the coords API is not good enough. Right now it has a CSS-like model of
{ top, left, right, bottom }
. What if I wanna specify square of [from, to]. Of a specific area. I feel practically top left right bottom is useless unless it can behave exactly like CSS. with percantages, vh, vw, rem, em etc.Secondly, how do we want to deal with partially overlapping bounds
The text was updated successfully, but these errors were encountered: