[EuiComboBox] Pressing enter after searching can throw an error

[stacey-gammon]

Hitting this in tests so I'm guessing it's a timing issue. Ran kbn yan clean && yarn kbn bootstrap to assure it's not a bad cache issue.

See elastic/kibana#22233 for some more context.

To repro I added await PageObjects.common.pressEnterKey(); in the combobox service, in the set function to get around the above but then hit this issue when running input control selenium tests.

I'm thinking maybe an async timing issue which matchingOptions and options? Actually I see:

    if (areOptionsDifferent) {
      this.options = [];
      this.setState({ matchingOptions: newMatchingOptions });

      if (!newMatchingOptions.length) {
        // Prevent endless setState -> componentWillUpdate -> setState loop.
        if (this.state.hasActiveOption) {
          this.clearActiveOption();
        }
      }
    }

Which seems like then options might be an empty array but matchingOptions might not in which case I could see how it would get hit.

[cee-chen]

Closing this as not reproducible due to the age of the bug. In addition, this issue will likely go away when EuiComboBox is converted to use EuiSelectable (#2841)