db-popover postion broken after upgrade to 2.2.0 when using CSS classes

[Vexx662]

Which generators are impacted?

• All
• HTML
• React
• Angular
• Vue
• Web components
• Power Apps

Reproduction case

Hi db-ux core,

we just upgraded today to the new version of 2.2.0 in our regular updates. After the upgrade our test showed that the db-popover is broken when using the css classes

Data shown in screenshot is mock data and fake data auto generated!

Please fix the issue and inform me about the resolution!

Regards,

Steven

Expected Behaviour

DB Popover is correctly using the position via data-placement when using the css classes in 2.2.0

Screenshots

Data shown in screenshot is mock data and fake data auto generated!

Browser version

Chrome

Add any other context about the problem here.

No response

[nmerget]

@Vexx662 I reverted some changes to allow a pure html/css for popover. You should know that the pure solution wouldn't have all features like auto-detection if the popover is out of screen etc.

[Vexx662]

yes but the version 2.1.2 is working right now and after the upgrade it is broken position wise. We had from db-ui many many issues with using the native react components that why we don't want to use them at all!

[nmerget]

#4360 should revert those position changes.

db-ui uses stenciljs and they provide wrappers for the frameworks like react. That's one reason why we swtiched to Mitosis to generate "real" react components.
We solved a lot of issues with this switch, it's worth to checkout the current components :)