The autocomplete for hops in the recipe editor appear to have some kind of performance bug.
When you select (with tab or mouse) an item that has been autocompleted in the hops editor, there is a little pause as the text field is filled and the AA field is updated. But that pause gets longer and longer the more times you interact with any of the Hop text fields.
Say I make a recipe with 8 hop entries. First one autocompletes just fine. Next one, noticable pause. Next one annoying pause. Next one, painful pause. It does not take too many interactions before trying to autocomplete a field takes 10-15+ seconds. The whole time, the item shows as selected in the drop down, the drop down is just hanging out there and the rest of the page is non-interactive.
I profiled it in chrome - it keeps firing cliick .ui-menu-item over and over and over. Each of those triggers a call to lookupHopsAA that takes longer and longer to run each time it is triggered (41ms up to 433ms)
It looks like there is both some rendering trigger loop that it gets stuck in and that maybe something is not getting cleared out between updates and it has to chug through a bunch of duplicate items.
When you select (with tab or mouse) an item that has been autocompleted in the hops editor, there is a little pause as the text field is filled and the AA field is updated. But that pause gets longer and longer the more times you interact with any of the Hop text fields.
Say I make a recipe with 8 hop entries. First one autocompletes just fine. Next one, noticable pause. Next one annoying pause. Next one, painful pause. It does not take too many interactions before trying to autocomplete a field takes 10-15+ seconds. The whole time, the item shows as selected in the drop down, the drop down is just hanging out there and the rest of the page is non-interactive.
I profiled it in chrome - it keeps firing cliick .ui-menu-item over and over and over. Each of those triggers a call to lookupHopsAA that takes longer and longer to run each time it is triggered (41ms up to 433ms)
It looks like there is both some rendering trigger loop that it gets stuck in and that maybe something is not getting cleared out between updates and it has to chug through a bunch of duplicate items.