Keyboard menu bug
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- mobile-dev
Research direction
Reproduce the issue on Android TV with Cloudstream 4.8.0-PRE, commit 35a1c76, following the listed menu and settings steps. Trace the menu behavior from the search bar into the General and Player sections; done means the keyboard does not open in those sections while it still behaves correctly for search.
Written by the indexing model from the issue text.
Description
Steps to reproduce
- On TV go to the menu
- Keyboard opens automatically. (might be an intended feature, idk)
- When u scroll down it goes away (as it should)
- Than open either General or Player settings sections (the keyboard opens but you cant search anything with it)
Expected behavior
The keyboard shouldn't open on those two sections.
Actual behavior
On the TV, when you open the menu obviously the starting point is the search-bar, and the keyboard opens automatically. When u scroll down it goes away, than when u open either General or Player settings sections the keyboard opens but you cant search anything with it.
Cloudstream version and commit hash
4.8.0-PRE 35a1c76
Android version
Android 13
Logcat
Other details
But I gotta say I really like the new menu apart for this bug.
Acknowledgements
- I am sure my issue is related to the app and NOT some extension.
- I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
- I have written a short but informative title.
- I have updated the app to pre-release version Latest.
- I will fill out all of the requested information in this form.
- Dominant language
- Kotlin
- Stars
- 10.8k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from recloudstream/cloudstream
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
recloudstream/cloudstream#3100 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
recloudstream/cloudstream#2639 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement potential extension
Difficulty 4/5 3-5 days Newbie friendliness 35/100
recloudstream/cloudstream#3232 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
recloudstream/cloudstream#3231 · 2 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
recloudstream/cloudstream#3230 · 3 comments · 5 reactions ·
Maintainers usually reply within 1 day
All issues in recloudstream/cloudstream
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Bug Domain changed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
keiyoushi/extensions-source#19571 · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
modelcontextprotocol/kotlin-sdk#1090 ·
Maintainers usually reply within 2 days