Revisit Select about ui HOT 5 CLOSED

Good idea, I think it will be a challenge. See #60 (comment) for info.

I like the usage of a ResizeObserver in the Popper, to let the Popper adjust itself when required. But we did also try an alternative approach using a renderId / renderCount prop to force an update. This also worked fine, but makes for a much more quirky API and moves the responsibility for updating the position out of the popper and into whichever component is rendering the popper. This which isn't the most logical separation of concerns and will lead to code-bloat in the long term. If we can't work out a way of fixing these failing tests due to the ResizeObserver we could consider switching to that more quirky API instead (even though that'd be admitting defeat).

I think we should also look into the setup of our cypress environment... I'm not sure what we are doing now, but we were doing everything in electron, which usually used some older version of chromium. According to the docs we should be able to use Chrome.

from ui.

Agreed. I did create this PR a while back, when testing running our cypress tests in FF and Chrome: dhis2/ui-core#800

from ui.

So about the cypress tests in Chrome (+ maybe FF, etc.), maybe we could split that into a separate issue. To not muddy the scope for the current one.

from ui.

🎉 This issue has been resolved in version 5.0.0-alpha.17 🎉

The release is available on:

• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from ui.

🎉 This issue has been resolved in version 5.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from ui.