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

Performing a search causes the defined values for filter parameters to be set to the default ones #4255

Closed
Ricky-Tigg opened this issue Mar 6, 2024 · 2 comments

Comments

@Ricky-Tigg
Copy link

Describe the bug

v.: 5.191.0 | Hello. Regardless of the search category among All, Images, Videos, News, performing a search after editing the existing search expression causes the value of each filter parameter that is located to the right of the Safe search filter parameter to be set to their default one, therefore indicating an issue. That is, only the defined values of the first two filter parameters, Region, Safe search are not set to their default ones, which is the intended behavior.

duckduckgo_android_search_page

How to Reproduce

  1. Select a search category among All, Images, Videos, News,
  2. Set a value for each of those filter parameters that are involved in the issue so that it is no longer the default one.
  3. Edit the existing search expression.
  4. Perform a search.

Expected behavior

Performing a search must not cause the defined values for filter parameters to be set to the default ones.

Environment

No response

Copy link

github-actions bot commented Mar 6, 2024

Thank you for opening an Issue in our Repository.
The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate.
As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

@CDRussell
Copy link
Member

Thanks for the detailed report! 🙏

I think this is largely working as intended and the behavior you observe is consistent across both our Android and iOS apps. When you enter a new search term, we treat that as a brand new search meaning the filters return to their defaults. That said, I definitely understand why that's unexpected or undesirable in a lot of cases.

I'll close this task for now because we won't immediately make any changes to this behaviour, but will discuss it more internally. Thanks for bringing it to our attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants