Skip to content

style[banner]: adjust banner content navigation button size#1736

Open
Antoliny0919 wants to merge 2 commits into
toss:mainfrom
Antoliny0919:fix-banner-button-size
Open

style[banner]: adjust banner content navigation button size#1736
Antoliny0919 wants to merge 2 commits into
toss:mainfrom
Antoliny0919:fix-banner-button-size

Conversation

@Antoliny0919

@Antoliny0919 Antoliny0919 commented May 24, 2026

Copy link
Copy Markdown
Contributor

Summary

The navigation buttons inside the banner located at the bottom right of the screen are too small.(6 * 6)
too-small

Even I, who don't usually have difficulty with small buttons, had to attempt clicking two or three times.

According to W3C guidelines, a minimum size of 24 x 24 is recommended.
However, applying this standard to these buttons would likely involve style trade offs.

That said, I still think the button size needs to be increased somewhat, even if it doesn't fully meet the 24 x 24 requirement.

Change

Before (6 * 6)

look-example-full-sc

After (12 * 12)

(If 12 feels a bit too large, 10 would look fine as well 😁)

look-example-af-img

@vercel

vercel Bot commented May 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
es-toolkit Ready Ready Preview, Comment May 31, 2026 1:41pm

Request Review

@raon0211

Copy link
Copy Markdown
Collaborator

I think adding previous/next buttons works better aesthetically than making the dots bigger.

@Antoliny0919

Copy link
Copy Markdown
Contributor Author

I think adding previous/next buttons works better aesthetically than making the dots bigger.

I agree. Adding navigation buttons would be more visually explicit.
Thanks for suggesting the direction!

@raon0211 🙌
If you have time, could you also take a look at this comment?
#1735 (comment)

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