This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
Update dependency @floating-ui/react to v0.26.23 #12910
Closed
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.11
->0.26.23
Release Notes
floating-ui/floating-ui (@floating-ui/react)
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/[email protected]
v0.26.21
Compare Source
Patch Changes
@floating-ui/[email protected]
v0.26.20
Compare Source
Patch Changes
focus
call inact
inuseFocus
tests@floating-ui/[email protected]
v0.26.19
Compare Source
Patch Changes
scrollX
/scrollY
instead of deprecatedpageXOffset
/pageYOffset
@floating-ui/[email protected]
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/[email protected]
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/[email protected]
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.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.