fix(deps): update dependency @floating-ui/react to v0.26.28 #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.26.6
->0.26.28
Release Notes
floating-ui/floating-ui (@floating-ui/react)
v0.26.28
Compare Source
Patch Changes
useHover()
stickIfOpen
prop to determine whether to remain open upon first click when first opened by another eventreturnFocus
is ignored correctly when usingdisabled
propv0.26.27
Compare Source
Patch Changes
virtualItemRef
on floating closeroot
to be reactive fromnull
to an elementv0.26.26
Compare Source
Patch Changes
domReference
instead ofreference
v0.26.25
Compare Source
Patch Changes
restMs
enabled
optionmax-height
only if not scrollablev0.26.24
Compare Source
Patch Changes
React.JSX.Element
types. Ensure you've upgraded to the latest@types/react
patches (versions since May 6, 2023)transform
style propertymaxHeight
and applyminItemsVisible
only when scrollable@floating-ui/react-dom@2.1.2
,@floating-ui/utils@0.2.8
v0.26.23
Compare Source
Patch Changes
onOpenChange
reason string forFloatingFocusManager
'scloseOnFocusOut
handlingstaticOffset
prop if floating element is shifted. Fixes an issue where the arrow could potentially point to nothing if it was shifted enough from its reference element.onNavigate
from potentially passing in anundefined
value instead ofnull
blockPointerEvents
no longer addspointer-events: none
to unintended<body>
elements.disabled
propv0.26.22
Compare Source
Patch Changes
@floating-ui/utils@0.2.7
v0.26.21
Compare Source
Patch Changes
@floating-ui/utils@0.2.6
v0.26.20
Compare Source
Patch Changes
focus
call inact
inuseFocus
tests@floating-ui/utils@0.2.5
v0.26.19
Compare Source
Patch Changes
scrollX
/scrollY
instead of deprecatedpageXOffset
/pageYOffset
@floating-ui/utils@0.2.4
v0.26.18
Compare Source
Patch Changes
reference
andfloating
prop getters had dependencies grouped.FloatingPortalProps
,CompositeProps
,CompositeItemProps
useHover
anduseClick
hooks and a click occurred before the floating element could open on hover, it would unexpectedly close onmouseleave
despite being triggered by a click.@floating-ui/utils@0.2.3
v0.26.17
Compare Source
Patch Changes
restoreFocus
prop. This enables automatic restoration of focus to the nearest tabbable element if the element that currently has focus inside the floating element is removed from the DOM.v0.26.16
Compare Source
Patch Changes
scrollIntoView
andfocus
behavior with virtual focus and inner DOM-focused element +FloatingList
undefined
id with unconditional rendering in React <18selectedIndex
changes from stealing focusdisabledIndices
is inferredscript
tags needlessly@floating-ui/react-dom@2.1.0
v0.26.15
Compare Source
Patch Changes
isMounted
check and remove unneeded initiated state. Prevents an infinite loop when called in a component with an unstable callback ref.v0.26.14
Compare Source
Patch Changes
useFloatingRootContext
Hook, which enables calling interaction hooks in a component higher in the tree thanuseFloating
is called in. This supports spreading reference props onto an "external" reference element.v0.26.13
Compare Source
Patch Changes
React_2
withReact
in generated .d.ts filesReact.JSX.Element
back toJSX.Element
restMs
+ nullish open delay should respectrestMs
v0.26.12
Compare Source
Patch Changes
dataRef
openEvent
property toundefined
on close. Fixes a minor issue whenuseHover
restMs
is combined withuseClientPoint
and focus modality was used before hover modality.v0.26.11
Compare Source
Patch Changes
mouseOnly
is respected whenrestMs
is specified. Also ensurerestMs
is always0
for touch input.FloatingOverlayProps
GroupContext
value from the Hook, and don't require anid
option to be passed. You only need to invokeuseDelayGroup()
and read the context data from it. As a result,useDelayGroupContext()
has been deprecated as it no longer needs to be used.v0.26.10
Compare Source
Patch Changes
v0.26.9
Compare Source
Patch Changes
v0.26.8
Compare Source
Patch Changes
@floating-ui/react-dom@2.0.8
v0.26.7
Compare Source
Patch Changes
@floating-ui/react-dom@2.0.7
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.