-
Notifications
You must be signed in to change notification settings - Fork 108
Open
0 / 40 of 4 issues completedLabels
P1 - importantPriority: High impact on UXPriority: High impact on UX
Description
❌ 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
KTooltipin favor ofuseKFloatingPositionanduseKFloatingInteraction, whereuseKFloatingPositionwill use either FloatingUI or Popper2. - Add lazy-loading and event delegation to
KTooltipto 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.
Sub-issues
Metadata
Metadata
Assignees
Labels
P1 - importantPriority: High impact on UXPriority: High impact on UX
