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
Since we're now using clip-path we can use % units instead of pixels.
This may remove the need for the ResizeObverser in the main component as the percentage value will still be the same even when the component resizes. It should also should hopefully resolve the Safari keyboard increment issue from #69 and the Safari console error from #103.
^ The above is probably not possible because boundsPadding is pixel based, so it needs to be recalcuated on resize relative to the root container.
Considerations:
boundsPadding and CSS scaling should still be respected
The text was updated successfully, but these errors were encountered:
nerdyman
changed the title
Try using percentage units everywhere instead of percentage and pixel mix
Try using percentage units internally instead of percentage and pixel mix
Nov 10, 2022
Since we're now using
clip-path
we can use%
units instead of pixels.This may remove the need for theResizeObverser
in the main component as the percentage value will still be the same even when the component resizes. It should also should hopefully resolve the Safari keyboard increment issue from #69 and the Safari console error from #103.^ The above is probably not possible because
boundsPadding
is pixel based, so it needs to be recalcuated on resize relative to the root container.Considerations:
boundsPadding
and CSS scaling should still be respectedThe text was updated successfully, but these errors were encountered: