[Bug][Mobile] Closing home search keeps the thread list filtered with no indicator
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start at the iOS home screen thread list and its search open/close handling, then trace where the query controls the visible threads. Reproduce by searching and closing search without clearing the query. Done when closing search clears the query or the filtered state remains visibly indicated with a way to clear it.
Written by the indexing model from the issue text.
Description
Platform: iOS app, home screen thread list
Steps
- Tap search on the home screen and type a query.
- Close search without clearing the text.
Expected: Closing search clears the query, or the list shows that it's filtered (a chip with the query and a clear button, or a "Filtered by ..." row).
Actual: The list stays filtered by the query with no indication. Threads that don't match look like they've disappeared, and nothing on screen explains why or how to get them back. The only fix is to reopen search and clear the text.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 323
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 pingdotgg/t3code
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
needs more info via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
pingdotgg/t3code#22054 · 3 comments ·
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
engine-rs P3 review-deferral wasm
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
maniator/verticopolis#1154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
telerik/kendo-react#3861 ·
Maintainers usually reply within 1 day
-
[bug]: use-mobile.ts uses pixel logic, causing UI state de-sync with Tailwind CSS rem breakpointsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100