Fixes #3502 by Changing the Way We 'Queue' Search Queries #3503
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
PR Type
Fixes
Issue Number: #3502
What is the current behavior?
When searching for content within a specific channel, the channel ID for the query gets "stuck". The search results returned will be equal to the last unique channel visit.
Ex.
User views channels A -> B -> C -> D -> E. At this point if the user uses the search field for channels A, B, C or D they'll see results for channel E.
Steps to reproduce:
What is the new behavior?
The search will only return content that belongs to the channel being viewed.
Other information
Image of Search Field in Question