Repository navigation
[6.x] Bard set selection/focus outline improvements - #14336
Merged
Merged
Conversation
… handled with the pseudo content
…den briefly so it doesn't flicker back to the parent while focus settles.
…roup] to prevent focus drifting back to container
…prevent focus drifting back to container
…tline hidden briefly so it doesn't flicker back to the parent while focus settles." broken by the merge conflict
… outline will no longer be correct
…s outline will no longer be correct
jasonvarga
previously requested changes
Mar 24, 2026
# Conflicts: # resources/js/components/fieldtypes/bard/Set.vue
Match the readOnly prop added in 6.x, which also disables the button, so the pointerdown and click focus helpers bail out in the same cases as disabled and loading.
Focusing every Button on pointerdown broke anything relying on @mousedown.prevent to keep focus elsewhere, like the Markdown floating toolbar and Bard toolbar buttons. Re-focusing button group buttons after every click also stole focus from modals and popovers app-wide. - Button is back to matching 6.x - The Bard set now focuses clicked buttons on mousedown (for Safari), skipping any mousedown that's already been prevented - Button group buttons are only re-focused when focus has fallen back to the body or a wrapper, not when the click moved it somewhere on purpose
After we focus a clicked button on mousedown, Safari's default mousedown action moves focus off it again, so the outer outline briefly reappears until the button is re-focused. Prevent the default once the button has focus so it stays put.
jackmcdade
enabled auto-merge (squash)
October 13, 2026 21:01
jackmcdade
disabled auto-merge
October 13, 2026 23:52
This file contains hidden or 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
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.
Description of the Problem
Bard set selections can be confusing because focus states are shifted around with JavaScript.
This is documented in issue #14185 where a video shows the blue outline shifting around.
What this PR Does
…dropdown so it's only shown around the set you're interacting withBefore Fixes
Here you can see the selection outline is frequently pushed to the outer set when interacting with inner elements
Before.mp4
After Fixes
The selection outline does not jump to outer sets, instead keeping on the current set you're working on
After.mp4
How to Reproduce
Set up a Bard field with a set that houses a replicator, that contains a button group, and a further replicator (just for testing some inception replicators)
Try the following to see how the outline behaves:
…in the inner replicator to access the dropdown. Currently, the outline selection will be pushed to the outer Bard field, which is misleading