This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
Blob UI: Disable return to target logic in blame popover UI #43353
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.
Fixes https://github.com/sourcegraph/sourcegraph/issues/43335
Background
Previously before we merged https://github.com/sourcegraph/sourcegraph/pull/43029 the PopoverContent didn't do anything with focus (didn't return it to the original target) if
focusLocked
is specified and set tofalse
. In https://github.com/sourcegraph/sourcegraph/pull/43029 I changed this behaviour, and now PopoverContent exposes thereturnTargetFocus
prop to turn on/off focus preservation after Popover has been closed.The recursion (why we have problem in Blame annotations) is
returnTargetFocus
by default is true the Popover 1 returns popover to the target 1I shared my feedback about this that this blame popover should use a tooltip pattern and doesn't have any interactive element as content. And in this case, we wouldn't be needed in any focus popover-like management in this UI.
Test plan
App preview:
Check out the client app preview documentation to learn more.