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

UX Issue | Awkward Category Name Field On Add Feed #2545

Open
3 of 5 tasks
Fludem opened this issue Jan 11, 2025 · 1 comment
Open
3 of 5 tasks

UX Issue | Awkward Category Name Field On Add Feed #2545

Fludem opened this issue Jan 11, 2025 · 1 comment

Comments

@Fludem
Copy link

Fludem commented Jan 11, 2025

Describe the bug

The 'Category Name' field on the 'Add Feed' form behaves awkwardly and provides a bad user experience.

If you want to add this feed to a category that doesn't exist, typing in the new category's name allows you to create a new category to store the feed in.

In some scenarios, the user wants to create a category with a name similar to an existing category.
I.E The user has an existing category named Tech, but they wish to add a new category named Technical.

In these scenarios, the UI forces them to select the matching category (Tech) and prevents them from creating a new category.

The user can prevent the Autofill by clicking inside the modal and away from the 'Category Name' field.
However, many users don't click around a form; instead, they use the keyboard to navigate it.

If a user types any of these keys, the autofill will be used, preventing them from creating a new category:

  • Tab - Typically used to jump to the following form field or element.
  • Enter - Typically used to submit the form.
  • Escape - Sometimes used to close floating components. Pressing escape is something I tried as a workaround. Tab and Enter weren't usable. But Escape closes the modal, which is expected.

Feed Info

Attempt to add any valid feed and you can likely reproduce this bug.

Reproduction Video

Gyazo Video Clip: https://gyazo.com/35cb3a8d72a42f2b8e4ea157ab2d74ae

Environment

Latest version, but I am using MacOS if that makes a difference.

Environment

App Version: 0.3.1-beta.0
OS: macOS
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Follow/0.3.1-beta.0 Chrome/130.0.6723.118 Electron/33.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: X_bjqcvXFSIzrcQMxWp-l
Renderer: 0.3.1-beta.0

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • This issue is valid

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Copy link

linear bot commented Jan 11, 2025

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

No branches or pull requests

1 participant