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] Change Search Button Type to submit for Clarity #292

Open
1 task done
Silvia-Wachira opened this issue Oct 15, 2024 · 2 comments
Open
1 task done

[Bug] Change Search Button Type to submit for Clarity #292

Silvia-Wachira opened this issue Oct 15, 2024 · 2 comments
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: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback

Comments

@Silvia-Wachira
Copy link

Description

The current implementation of the search feature uses a button element that does not specify a type. This can lead to inconsistent behavior across different browsers and may prevent the form from submitting correctly.

Expectation

The button should be of type submit to indicate its purpose clearly. While the form submits as expected, It is better to change the type to submit so as to improve code clarity and maintainability across various browsers.

Environment

  • Device: (laptop)
  • OS: (Ubuntu)
  • Browser: (Chrome)
  • Version: (129.0.6668.100)

Resolution

  • I would be interested in resolving this bug.
@Silvia-Wachira Silvia-Wachira 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 15, 2024
@possumbilities
Copy link
Contributor

Hi @Silvia-Wachira , thanks for noting this.

The form isn't actually submitted, but actually captured via JS, and then opens a page from the values. I'm unsure if setting the type here as any meaningful use, but I'm not opposed to it.

Does anyone else know of a reason why leaving or adding it might be worth doing, given that the form doesn't submit in a formal sense?

@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback 🟩 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 15, 2024
@Silvia-Wachira
Copy link
Author

Silvia-Wachira commented Oct 15, 2024

I appreciate the clarification that the form submission is handled via JavaScript and doesn’t submit in the traditional sense so in this case it might not have a significant impact on functionality but it could still be beneficial to future contributors or developers maintaining the project who might expect a form button to be of type submit, especially in form-based interactions. Adding the type makes the intention clearer, even if JavaScript handles the actual submission. @possumbilities

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: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

2 participants