You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhat related to #152: If the post selector makes multiple requests to the search endpoint, the last of those requests to return will be the one whose results are displayed, even if it wasn't the last request that was actually sent for the current search term.
Open the post selector and the Network tab of your browser tools. Search for park in the post selector (or use a different word that works better with your test data). You should see search requests for par and park.
The request for park will return first and populate the selector results. The request for par returns second, and the results for that search will replace the results that were there for park.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Somewhat related to #152: If the post selector makes multiple requests to the search endpoint, the last of those requests to return will be the one whose results are displayed, even if it wasn't the last request that was actually sent for the current search term.
Steps To Reproduce
Add this snippet somewhere:
Open the post selector and the Network tab of your browser tools. Search for
park
in the post selector (or use a different word that works better with your test data). You should see search requests forpar
andpark
.The request for
park
will return first and populate the selector results. The request forpar
returns second, and the results for that search will replace the results that were there forpark
.Additional Information
No response
The text was updated successfully, but these errors were encountered: