alignandpaddingno longer erroneously required as props
- Removed some debugging statements erroneously published
- Rolled back
DOMRectchanges as it interferes with SSR, replaced with customRectinterface that mirrors the same API
contentLocationprop has been renamed topositionTransform, behaves exactly the samepositionsprop now accepts a single string in addition to an array of prioritized strings- Migrated from deprecated
ClientRecttoDOMRect(thanks @jafin)
- A new
transformModeprop now accepts string values of"absolute"or"relative"."absolute"mode is its default, and causes behavior identical tocontentLocation. The"relative"value, however, will cause the providedtopandleftvalues of the transform to merely be summed to the existingnudgeTopandnudgeLeftvalues, behaving as a relative positioning system.
- popover positioning miscalculation issue
- blurry popover on non-retina displays (thanks @D34THWINGS)
- click-outside support now works across different windows (thanks @dutziworks)
- added
clickOutsideCaptureprop toPopover
- added
violationsproperty toPopoverState - added
hasViolationsproperty toPopoverState - React 18 is now an accepted peer dependency
onClickOutsidenow uses event capturing (thanks @davidjgross)
usePopovernow returns immediately when popover is not open, fixing an issue where utility and positioning functions sometimes fired even when popover was not open
- Issue where popovers within a new stacking context would sometimes not render at the correct position
- SSR support
boundaryElementprop
- Renamed
containerParenttoparentElement
- Popovers not rendering at proper location within translated container elements
- Removed
customstring type frompositionandalignprops, replaced withundefined useArrowContainerdoes not render an arrow ifpositionisundefined
ArrowContainernow handles custom class names properly (thanks KWLEvans)
- Inline source maps