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
The category filters are updated based on the keyword search, but the selected filter on the form is still "Rumah Sakit" which doesn't exist in new category filters so Kategori doesn't have selected item.
Or in another case like in #203, different filter is selected (probably based on the order on previous filter option?)
The result is also empty because it applies both keyword and the filter (searching for "Cahaya Gas" keyword with "Rumah Sakit" category.
Expected Behaviour
When cari button is clicked, the filter should be cleared/reset(?)
I'm still not sure what behavior will be more natural.
When user already select a category and search for another keyword:
Does user looking for a completely new result based on keyword? or
User wants to search those keyword for items under selected filter?
After the rule is fixed, then the bug should be fixed accordingly.
The text was updated successfully, but these errors were encountered:
Description
Just like previous bug in FAQ page #203, the same bug still exists on
Province
page.For example:
The category filters are updated based on the keyword search, but the selected filter on the form is still "Rumah Sakit" which doesn't exist in new category filters so Kategori doesn't have selected item.
Or in another case like in #203, different filter is selected (probably based on the order on previous filter option?)
The result is also empty because it applies both keyword and the filter (searching for "Cahaya Gas" keyword with "Rumah Sakit" category.
Expected Behaviour
When
cari
button is clicked, the filter should be cleared/reset(?)I'm still not sure what behavior will be more natural.
When user already select a category and search for another keyword:
After the rule is fixed, then the bug should be fixed accordingly.
The text was updated successfully, but these errors were encountered: