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.

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

[Bug] Search Button: Default Button Border Not Removed Across All Screen Sizes #304

Open
1 task
SisiVero opened this issue Oct 18, 2024 · 0 comments · May be fixed by #308 or #306
Open
1 task

[Bug] Search Button: Default Button Border Not Removed Across All Screen Sizes #304

SisiVero opened this issue Oct 18, 2024 · 0 comments · May be fixed by #308 or #306
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@SisiVero
Copy link
Contributor

Description

The default border of the button was not removed for all screen sizes. The border is still visible on both desktop and mobile screens. It's essential to remove the default button border to maintain design consistency across the interface and avoid a cluttered or outdated appearance, especially when custom button styles are applied. And since the button has a background color, a border is not needed.

Reproduction

  1. Access the interface on a desktop or large screen device.
  2. Observe that the button still has the default border.
  3. Switch to a mobile device or use developer tools to simulate a mobile screen size.
  4. Note that the button's default border is still visible.
  5. See error.

Expectation

The button’s default border should be removed consistently on all screen sizes to ensure a clean and modern appearance

Screenshots

Desktop screen with default:
defaultBorderPresent

Desktop screen without default border:
noDefaultBorder

Mobile screen with default border:
mobileViewWithBorder

Mobile screen without default border:
mobileViewNoBorder

Resolution

  • I would be interested in resolving this bug.
@SisiVero SisiVero added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 18, 2024
@possumbilities possumbilities added 🏁 status: ready for work Ready for work 🟩 priority: low Low priority and doesn't need to be rushed and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟧 priority: high Stalls work on the project or its dependents labels Oct 18, 2024
@Macomi27 Macomi27 linked a pull request Oct 20, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
2 participants