Bugzilla

(In reply to Drew Willcoxon :adw from comment #4)
 > I'm curious how Chrome handles this. Their UI in the video looks incredibly fast and responsive. I wonder if they fetch as many suggestions from the extension as possible up front and so they're cached and ready to go when one is deleted, or if they fetch them as needed.

Certainly the former. I can be reasonably certain of this because resizing the window becomes *incredibly* janky.

> Instead of starting a new search, fetch more extension results than necessary in the original search and cache them somewhere. Slot them in when a result is blocked. This isn't currently possible either and would probably require modifying the muxer.

So, in my head, I'm imagining a new group property ala `maxResultCount` but something like `maxInvisibleOverflowCount` which defines the maximum amount of "invisibly overflowed" results. Then, the `max-width` of `urlbar-results` is set to match `maxResultCount`/`availableSpan` and I add some code somewhere to prevent arrowing down into these invisibly overflowed results and it "just works" with hopefully minimal changes required.

(In reply to Drew Willcoxon :adw from comment #4)
 > I'm curious how Chrome handles this. Their UI in the video looks incredibly fast and responsive. I wonder if they fetch as many suggestions from the extension as possible up front and so they're cached and ready to go when one is deleted, or if they fetch them as needed.

Certainly the former. I can be reasonably certain of this because resizing the window becomes *incredibly* janky.

> Instead of starting a new search, fetch more extension results than necessary in the original search and cache them somewhere. Slot them in when a result is blocked. This isn't currently possible either and would probably require modifying the muxer.

So, in my head, I'm imagining a new group property ala `maxResultCount` but something like `maxInvisibleOverflowCount` which defines the maximum amount of "invisibly overflowed" results. Then, the `max-height` of `urlbar-results` is set to match `maxResultCount`/`availableSpan` and I add some code somewhere to prevent arrowing down into these invisibly overflowed results and it "just works" with hopefully minimal changes required.