Skip to content

refactor: don't adjust container padding based on border-radius (#11365) (CP: 25.1)#11366

Merged
web-padawan merged 1 commit into25.1from
cherry-pick-11365-to-25.1-1773829619239
Mar 18, 2026
Merged

refactor: don't adjust container padding based on border-radius (#11365) (CP: 25.1)#11366
web-padawan merged 1 commit into25.1from
cherry-pick-11365-to-25.1-1773829619239

Conversation

@vaadin-bot
Copy link
Copy Markdown
Collaborator

This PR cherry-picks changes from the original PR #11365 to branch 25.1.


Original PR description

Adjusting the container (input field, button, side-nav, tabs, etc) inline-padding based on the border-radius can be unexpected, and doesn't provide much added benefit visually.

The default padding stays the same. This can have a minor visual change on apps that use a large --aura-base-radius value.

@sonarqubecloud
Copy link
Copy Markdown

@web-padawan web-padawan merged commit 08811b9 into 25.1 Mar 18, 2026
10 checks passed
@web-padawan web-padawan deleted the cherry-pick-11365-to-25.1-1773829619239 branch March 18, 2026 10:34
@vaadin-bot
Copy link
Copy Markdown
Collaborator Author

This ticket/PR has been released with Vaadin 25.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants