Skip to content

Increase mobile input padding in movistar-new - #2551

Merged
aweell merged 2 commits into
productionfrom
aweell-fix-movistar-new-input-padding
Feb 13, 2026
Merged

Increase mobile input padding in movistar-new#2551
aweell merged 2 commits into
productionfrom
aweell-fix-movistar-new-input-padding

Conversation

@aweell

@aweell aweell commented Feb 11, 2026

Copy link
Copy Markdown
Collaborator

Proposes an increase in the mobile input padding for the "movistar-new" design token. The changes specifically adjust the top and bottom padding from 8px to 9px on mobile devices.

Motivation:
The primary motivation behind this change is to enhance the user experience on mobile devices by providing slightly more spacing around input fields. This adjustment aims to improve touch targets, making it easier for users to interact with forms and input elements, thereby reducing the likelihood of input errors.

Improvements:
By increasing the padding, we create a more comfortable and visually appealing interface, which can lead to improved usability and user satisfaction. This small yet impactful change reflects our commitment to continuously refining the mobile experience for our users.

@aweell
aweell requested a review from Marcosld February 11, 2026 12:35
@aweell aweell closed this Feb 11, 2026
@aweell
aweell deleted the aweell-fix-movistar-new-input-padding branch February 11, 2026 15:01
@aweell
aweell restored the aweell-fix-movistar-new-input-padding branch February 13, 2026 10:33
@aweell aweell reopened this Feb 13, 2026
@aweell
aweell requested a review from yceballost February 13, 2026 10:34
@aweell
aweell added this pull request to the merge queue Feb 13, 2026
Merged via the queue into production with commit ecc9c82 Feb 13, 2026
10 checks passed
@aweell
aweell deleted the aweell-fix-movistar-new-input-padding branch February 13, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants