search

participedia / frontend

DEPRECATED - see https://github.com/participedia/api/ instead
MIT License
2 stars 2 forks source link

Search BUGS Cannot search from entry view / searches don't clear #836

Closed scottofletcher closed 5 years ago

scottofletcher commented 6 years ago

Search bar does not work on any page except the home page.

scottofletcher commented 6 years ago

Lucy just messaged me on Slack telling me this bug is very disruptive to her workflow

jesicarson commented 6 years ago

Noted. I just messaged Lucy to see if we can find a work around for now. Thanks for the flag.

jesicarson commented 6 years ago

Hi @dethe - I just got clarification from Lucy that its not having to go to the homepage to search that is slowing her down, it's because the map takes so long to load each time. She checked her internet connection and that shouldn't be a problem for her, however, I can't replicate the map loading issue, mine loads quite quickly. I recommended that she try scrolling down the screen (hiding the map) before searching. Hopefully that will make a difference until we can fix this, but not sure.

At any rate, wondering if you think this bug should be prioritized? I hesitate because there are so many other things on your plate. Thanks!

scottofletcher commented 6 years ago

Thanks @jesicarson and @dethe - I'm actually finding that having to go to the homepage to search is slowing down my work not necessarily because it takes so long to load but just because it takes longer in general.

I'm also getting a little frustrated not being able to clear a search or return to just cases, orgs, or methods without going to the homepage first. For example, if I search for citizens' assembly, clicking on 'cases', 'orgs', or 'methods' will filter my search. However, if I want to clear my search and just see all the organizations, I have to first go to the home page and then scroll down and select orgs.

jesicarson commented 6 years ago

Oh ya that is frustrating. Search doesn't clear when you return to the homepage, you have to re-load the page. @dethe I assume these bugs are all connected?