Issue confirmed in Firefox (62b13) and Chrome.

I think this is a 'known issue'. Right now the aim is to leave as many of the select elements in native browser select as possible. There are two exceptions 1) Tags (ajax submit etc) 2) Where we need filtering (categories, module positions etc)

Do i understand correct that the shown Drodown is provided by Browser? In Firefox, Safari and Chrome (all latest on Mac) all look same.

As far as I'm aware yes? There's some padding etc provided by the stylesheet. But the multiselect ultimately is browser rendered

thanks for Information, @wilsonge. So in Future no need for Report if a Layout look different to J3 in Cases like that.

This is as part of intention to remove / replace chosen JS ?

If there is something known about the replacement of it ?
then please say so that we adapt to it earlier

This is as part of intention to remove / replace chosen JS ?

Pretty much. As to a replacement/keeping the original there's still no full decision made. But definitely the aim is to remove it where it's not required. So unless there's some sort of search/ajax functionality required (tags, category filtering, module position filtering/dynamic creation etc) then we'll just use native select not chosen

and this is still my preferred option https://alphagov.github.io/accessible-autocomplete/examples/

either as an element or easier as a progressive enhancement