Miki

this happens also when using [karibu testing for v8](https://github.com/mvysny/karibu-testing/tree/master/karibu-testing-v8) when the main UI class is a UI-scoped bean; fetching it from `ApplicationContext` to pass to `MockVaadin.setup()` raises exactly the same...

this requires some reworking of the poms looks like the parent module will actually become a parent pom as well - there will be three modules (demo, superfields, object-field-utils), two...

it seems a crucial part of the abovementioned solution is `IndexHtmlRequestListener`, which is not present in Vaadin 14 (it runs flow 2.X, whereas the class has been added for flow...

not sure if this is even doable in a way I would like to see it - with themes packaged neatly into their own folders - so putting it on...

Lit might be coming to Vaadin 14.6 or 14.7, so hopefully there will be some transition period and some documentation to work with.

@mperktold thanks for feedback! I looked at the Beacon API and there were two reasons why I did not do any further work; my JS skills are less than I...

Great! I will adapt this code in one of the next releases.

hello @jorgheymans - thanks for using SuperFields and apologies for the delay (just ended the summer holiday and I am getting back to regular work) `SuperTabs` is a *select* component,...

@jorgheymans fyi superfields `0.19.2` and `0.19.2-vaadin14` were just released with this feature in; please try it out and report any bugs and problems by reporting a new issue - thanks!