Page MenuHomePhabricator

[BUG] Search results content visible beneath status bar
Closed, ResolvedPublicBUG REPORT

Description

Steps to reproduce

  1. Settings > Search > enable Show languages on search
  2. Go to search tab, type a search term
  3. Scroll down through search results

Expected results

Search bar does not hide upon scroll when scrolling search results (See Explore tab search results for example of it working as expected).

Actual results

Search bar hides upon scroll and content is visible underneath

Screenshots

out.gif (428×900 px, 2 MB)

Environments observed

App version: 7.7.0 (4870)
OS versions: 18.3
Device model: iPhone 12 mini
Device language: EN

Event Timeline

Tsevener updated the task description. (Show Details)
Tsevener updated the task description. (Show Details)

Hi @Chandrapg !

We noticed you closed this PR, are you still working on it? If you are, please feel free to move the ticket back to the Doing column, but in the meantime I'll put it in blocked and waiting.

Thanks so much!

Hi @GOlson-WMF

Sorry yes, I'm still working on the task. I've moved the task back to doing from review. Will send out PR once i've tested everything one more time.

ABorbaWMF subscribed.

This is fixed on 7.7.1 (4936), but the keyboard no longer auto-hides when scrolling results.

@ABorbaWMF This is the same behavior in Explore tab and I observed this while testing.

Thanks @Chandrapg ! My understanding was that you've put in a fix for Explore: T385397, and a separate fix for Search with this current task.

It's fixed on Explore, but I am still seeing the bug on Search with these steps:

  • Open Search Tab
  • Initiate Search results by typing in bar and choosing blue "Search" button on keyboard
  • Navigate to another root view like Saved
  • Go back to Search Tab and start scrolling on results

Version: 7.7.1 (4944)

@HNordeenWMF The issue in the current task specifically relates to scroll behavior in the Search tab. The fix for this is already included in PR #5183.

However, the steps you outlined describe an issue similar to what I reported in T385397—which I’m already aware of. I have a fix for that in a separate branch, but I was waiting for the current fix to be deployed first, as the issue you reported cannot be reproduced without the fix in PR #5183.

My understanding is that each bug should have an associated task rather than merging multiple issues into a single task. However, if you’d prefer to include a fix similar to T385397 in PR #5183, I’m happy to update the PR accordingly.

Let me know how you’d like to proceed!

Hi @Chandrapg,
It's ok to solve the sample problem happening in multiple places or scenarios on the same task, or have multiple PRs on the same task if they're all related to fixing the same bug.
But since the follow-up fix is depending on this one deploying, I've created a separate task T386274 for the steps I mentioned above & added you.

HNordeenWMF removed Chandrapg as the assignee of this task.
HNordeenWMF added a subscriber: Chandrapg.