Next KTooltip version

[MisRob]

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

With the research phase and proof of concept for the next generation of our floating components completed, it’s time to start turning parts of it into production-ready implementations.

To support Studio’s migration to KDS, KTooltip will be the first. The main goals are:

• Remove current third-party dependencies from KTooltip in favor of useKFloatingPosition and useKFloatingInteraction, where useKFloatingPosition will use either FloatingUI or Popper2.
• Add lazy-loading and event delegation to KTooltip to allow its use on performance-sensitive Studio pages

Until we make the final library choice and plan release schedule, development will happen as KTooltip/next.

[Sahityaaryan]

Hi @MisRob ,
I would like to work upon this issue.
Please assign me this one.

[learning-equality-bot]

Season’s greetings! 👋

We’d like to thank everyone for another year of fruitful collaborations, engaging discussions, and for the continued support of our work. Learning Equality will be on holidays from December 22 to January 5. We look forward to much more in the new year and wish you a very happy holiday season!

Are you preparing for Google Summer of Code? See our GSoC guidelines.

[learning-equality-bot]

Hi! 👋

Thanks so much for your interest! This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues. If there are no unassigned 'help wanted' issues available, please wait until new ones are added.

We really appreciate your willingness to help. 😊

Are you preparing for Google Summer of Code? See our GSoC guidelines.