Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Woo POS] Create a single component for back button for consistency #14903

Closed
Tracked by #14459
staskus opened this issue Jan 17, 2025 · 3 comments
Closed
Tracked by #14459

[Woo POS] Create a single component for back button for consistency #14903

staskus opened this issue Jan 17, 2025 · 3 comments
Labels
feature: POS priority: low Not many people are affected or there’s a workaround, etc. type: task An internally driven task.

Comments

@staskus
Copy link
Contributor

staskus commented Jan 17, 2025 •
edited
Loading

The POS back button should share a single component to match each other. We have different spacing between the arrow and the text and different sizes of the arrow.

Email Receipt padding Cash Payment padding Cart button padding
@staskus staskus added type: task An internally driven task. feature: POS labels Jan 17, 2025
@dangermattic
Copy link
Collaborator

dangermattic commented Jan 17, 2025 •
edited
Loading

Thanks for reporting! 👍

@staskus staskus mentioned this issue Jan 17, 2025
Merged
4 tasks
@iamgabrielma iamgabrielma mentioned this issue Jan 18, 2025
Open
29 tasks
@joshheald
Copy link
Contributor

Consider also improving the VoiceOver performance when we add this component – see item 1 in #14957

@malinajirka malinajirka added the priority: low Not many people are affected or there’s a workaround, etc. label Jan 23, 2025
@staskus
Copy link
Contributor Author

staskus commented Feb 18, 2025

Addressed in #15076

@staskus staskus closed this as completed Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: POS priority: low Not many people are affected or there’s a workaround, etc. type: task An internally driven task.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@malinajirka @joshheald @staskus @dangermattic