Virtual Trigger as additional option to split what's send to Popper and SWC #1477
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.
Description
Add a
virtualTrigger
option to the overlay process that will supersede the element trigger, when available, as part of interaction directly with PopperJS.new VirtualTrigger(x, y)
will now provide aVirtualElement
that can be passed an option to theopenOverlay
methods for use as the "trigger" in calls to PopperJS. The element makes public both agetBoundingClientRect()
method for position the overlay and aupdateBoundingClientRect(x, y)
method for moving the "trigger" of the overlay.updateBoundingClientRect()
also callsOverlay.update()
internally to reduce the amount of manual interaction required to update overlays opened with the virtual trigger context.Related Issue
fixes #1437
Motivation and Context
Attempt to simplify from #1445
How Has This Been Tested?
Manually in Storybook. If this approach makes sense, some unit tests will be added.
Types of changes
Checklist: