I'd like to add one detail here, that may not be obvious from how we outlined this bug. Tests must be able to tell if a row is "current" (refers to the current query) or not. In the old autocomplete, we reused richlistitems, and we didn't remove them until new results arrive (or when the query was done, or on a timer), but tests needed to differentiate between current or old rows. To do that each row had an an "ac-text" attribute, that we used to compare with the current search string, if they are the same the result refers to the running query. We may want to somehow connect rows to specific queryContexts.
Bug 1523602 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'd like to add one detail here, that may not be obvious from how we outlined this bug. Tests must be able to tell if a row is "current" (refers to the current query) or not. In the old autocomplete, we reused richlistitems, and we didn't hide them until new results arrive (or when the query was done, or on a timer), but tests needed to differentiate between current or old rows. To do that each row had an an "ac-text" attribute, that we used to compare with the current search string, if they are the same the result refers to the running query. We may want to somehow connect rows to specific queryContexts.