fix(deps): update dependency @floating-ui/react-dom-interactions to v0.11.0 #295
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![plural-renovate[bot]](https://avatars.githubusercontent.com/in/259360?s=60&v=4){kind=small}
plural-renovate
bot
force-pushed
the
renovate/floating-ui-react-dom-interactions-0.x
branch
from
8d6eb0e to
3fc491d
Compare
plural-renovate
bot
force-pushed
the
renovate/floating-ui-react-dom-interactions-0.x
branch
from
3fc491d to
85d4ec0
Compare
plural-renovate
bot
deleted the
renovate/floating-ui-react-dom-interactions-0.x
branch
|
🎉 This PR is included in version 1.290.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.10.3->0.11.0Release Notes
floating-ui/floating-ui
v0.11.0Compare Source
New Features
feat(inner): allow custom
scrollRef(#1957)The floating element itself was required to be the scrolling container - however, it can be useful to use an inner element as the scrolling container instead.
This allows you to position inner elements relative to the floating element (e.g. scroll arrows that are direct children, not inside the scrolling container) more easily using standard CSS layout instead of needing to take into account the scroll offsets.
Bug Fixes
fix(FloatingFocusManager): ignore
focusoutevent forreturnFocus(#1955)With non-modal focus management, generally it is still desirable to keep
returnFocusenabled for things like dismissal or closing the element via a button. If the user tabs out of the floating element, it will now focus the next/prev natural element in the DOM order, not the reference element.fix: support falsy values in
middlewareoption for conditionals (#1954)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.