Design/UX #4592

Event Creation - Venue Dropdown Slow

Added by Samantha Raddatz over 6 years ago. Updated over 6 years ago.

Priority name:
Category name:
Target version:
Start date:
Due date:
% Done:


Estimated time:


During testing, a few users missed the venue dropdown due to the delay between typing/down-arrow-click and the dropdown appearing. If there's any way for that feedback to happen more quickly it could prevent users from passing it by.

Screenshot of the dropdown I'm describing attached.

Venue Dropdown.png (102 KB) Venue Dropdown.png Samantha Raddatz, 2015-09-11 11:34 AM


#1 Updated by Boone Gorges over 6 years ago

  • Target version set to Future release

It seems like overkill to me that the event creation works entirely by AJAX. A couple possible ideas:

- Load all venues into a JS object and autocomplete over those instead
- Load the most popular venues into a JS object. Autocomplete checks those first, and performs an AJAX request when the term typed is not in that list.
- Load the specific user's most-used venues into a JS object, etc

I haven't looked at the JS library being used for autocomplete in EO, but I assume it's possible to do this sort of partial preloading through a custom keyup callback.

This seems like a good enhancement for EO, but at the very least it's something we could implement locally.

Ray, if you have any ideas or thoughts, please chime in.

#2 Updated by Raymond Hoh over 6 years ago

These all sound like good suggestions. If we can limit the number of venues fetched instead of grabbing all of them as proposed above (popular, most used), that would be best.

Also available in: Atom PDF