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]: Unable to navigate using the arrow keys in the New Playlist Name prompt #5232

Closed
6 tasks done
efb4f5ff-1298-471a-8973-3d47447115dc opened this issue Jun 6, 2024 · 0 comments · Fixed by #5243
Closed
6 tasks done
Labels
B: inconsistent behavior bug Something isn't working

Comments

@efb4f5ff-1298-471a-8973-3d47447115dc

Guidelines

  • I have encountered this bug in the latest release of FreeTube.
  • I have encountered this bug in the official downloads of FreeTube.
  • I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
  • I have searched the documentation for information that matches the description of the bug I want to file, without success.
  • This issue contains only one bug.

Describe the bug

  1. Go to the Playlists page
  2. Click on the Create New Playlist button
  3. Put in a name but make a typo
  4. Try to navigate with the arrow keys so you can fix the typo
  5. See that you cannot navigate with the arrow keys

Expected Behavior

User can navigate within the prompt using the arrow keys

Issue Labels

inconsistent behavior

FreeTube Version

v0.20.0 / latest nightly build

Operating System Version

Windows 10 22H2

Installation Method

.exe

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

I still consider this a bug even though support for this was never implemented in the initial Playlist PR.

Nightly Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B: inconsistent behavior bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant