Events: workflow when triggering show/hide events and follows a link

[humitos]

While working on #268, Anthony found this use case wouldn't work:

if anyone tries to do anything async from the SEARCH_HIDE event, the code will likely be cut off. The operation order can be something like:

• User clicks results
• Event SEARCH_HIDE is fired off
• Browser navigates to link href
• Event SEARCH_HIDE is never consumed, or async code like fetch never finishes.

The user doesn't have the ability to affect the event propagation, so the browser will always follow the link.

I'm not sure what's the solution here, but I'm opening this issue to have a place to track this conversation.

Reference: #268 (comment)