[Autocomplete] - Listbox Jumps to the first option when more items are loaded

I have a component called QueryField, that makes a query to a GraphQL API with Apollo and shows the results as selectable options in the Listbox of Autocomplete component.

<Autocomplete
    ...
    ListboxComponent={ListboxComponent}
    loading={loading}
    options={starships}
    renderInput={params => (
      <TextField
        {...params}
        ...
        label="Starships"
      />
    )}
    renderOption={option => option.string}
/>

The Listbox is a FixedSizeList of react-window library. To generate more options when user scroll down, I use the components InfiniteLoader of react-window-infinite-loader. I have an issue when the fetchMore function executes (of useQuery hook). In this case, the list jumps to the first option, and we have to scroll down again to see the new options loaded.

const ListboxComponent = forwardRef((props, refListbox) => {
    const { children, ...other } = props;
    const itemData = Children.toArray(children);
    return (
      <div ref={refListbox}>
        <OuterElementContext.Provider value={other}>
          <InfiniteLoader
            isItemLoaded={isOptionLoaded}
            itemCount={itemsCount}
            loadMoreItems={loadMore}
          >
            {({ onItemsRendered, ref: refList }) => (
              <FixedSizeList
                ref={refList}
                height={200}
                itemCount={itemsCount}
                itemData={itemData}
                itemSize={35}
                onItemsRendered={onItemsRendered}
                outerElementType={OuterElementType}
                width="100%"
              >
                {renderListItem}
              </FixedSizeList>
            )}
          </InfiniteLoader>
        </OuterElementContext.Provider>
      </div>
    );
  });

How can I keep the scroll offset when more items are added?

Thanks in advance!

The complete demo is here:

https://codesandbox.io/s/infallible-wu-u6ocb

[jlramosr]

@sibelius no yet. Nobody provides me a correct solution 😦

[cmnstmntmn]

@jlramosr have you find a fix for this issue?