[6.x] Fix field alignment when field actions are visible - #15487
Merged
jasonvarga merged 2 commits intoSep 22, 2026
Merged
Conversation
jasonvarga
enabled auto-merge (squash)
September 22, 2026 20:20
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.
This pull request fixes an issue where a field with visible field actions sits a few pixels lower than a neighbouring field without them. The asset fieldtype in the linked issue shifts the moment an asset is selected, since that's when its actions appear.
The field header puts the label and the actions in the same row, so the row takes the height of whichever is taller. The actions row is unconstrained and measures 26px against the label's 20px line box, pushing the field down by 6px.
This PR fixes it by giving the actions row
h-5, matching the label's line height, so the header is the same height whether the actions are there or not.Fixes #15486