[Security] Uncaught TypeError: Cannot read property 'position' of null error during role creation

[inqueue]

Kibana version: 6.7.0 build: 20107

Elasticsearch version: 6.7.0

Original install method (e.g. download page, yum, from source, etc.): yum/RPM

Describe the bug:
When creating a new security role, the browser is immediately redirected to a Something went wrong error page after updating the Indices field under Index privileges.

Uncaught TypeError: Cannot read property 'position' of null

It happens with a particular index pattern *pcf*, though that could be a coincidence.

Steps to reproduce:

1. Enter a role name
2. Focus the Indices field under Index privileges and type *pcf*
3. Hit the tab key twice

[elasticmachine]

Pinging @elastic/kibana-security

[azasypkin]

Hmm, can't reproduce this on the latest 6.7 branch locally. @inqueue do you know Kibana git revision your build is based on?

[inqueue]

Hi @azasypkin, I just know it is build 20107. It was difficult for me to reproduce and having both the starting and trailing * seems to be key since it does not happen with any other pattern.

[inqueue]

BUILD 20107
COMMIT 617affef

[azasypkin]

Hi @azasypkin, I just know it is build 20107. It was difficult for me to reproduce and having both the starting and trailing * seems to be key since it does not happen with any other pattern.

Aha, right, somehow missed the leading * part , now I see it, thanks! Investigating...

[azasypkin]

Apparently this issue will happen to any EuiComboBox if you type option name completely and then press Tab twice. @chandlerprall pointed to two PRs that fixed that issue in EUI already elastic/eui#1576 and elastic/eui#1619.

So we're waiting for these to be backported to EUI 6.10.5: elastic/eui#1722 and Kibana should have this fix in 6.7.1 and 7.0.1

[chandlerprall]

This should be fixed in the 6.7 and 7.0 branches

[kobelb]

Thanks @chandlerprall! I'll confirm here momentarily and close out this issue.

[elasticmachine]

Pinging @elastic/eui-design (EUI)