Michaela Robosova
Michaela Robosova
Thanks @Pandaa007, we will have a look!
Okay, let us know when the time comes ;)
Please note that `release-v1.5.x` branch was renamed back to `main` (part of preparation of the new release and returning back to regular release process after that, more details to come)
Alright `main` is ready to be rebased on
I'm sorry for being a pain in the butt, but the changelog still needs cleanup, @nucleogenesis. There's still a conflict caused by introducing the new changelog format while this branch...
@nucleogenesis I am not sure if I could understand the motivation for two pull requests properly. Do you need anything in this one?
If it's still active and has no breaking updates, please retarget to `release-v3` branch before merging.
I am wondering if using a threshold value [in this condition ](https://github.com/learningequality/kolibri-design-system/blob/v0.2.x/lib/KModal.vue#L266) might help, similarly to how we use it for example [here](https://github.com/learningequality/kolibri-design-system/blob/v0.2.x/lib/KModal.vue#L246). We would need to be careful though...
This was recently observed in Kolibri > Device by @rtibbles [Screencast from 10-12-2023 04 05 17 PM.webm](https://github.com/learningequality/kolibri-design-system/assets/13509191/4187f118-dfc9-45f7-b41d-feeffd309670)
It's a follow-up to this PR https://github.com/learningequality/kolibri/pull/9011 which replaced plenty of hardcoded colors across Kolibri by tokens or palette as described here https://develop--kolibri-design-system.netlify.app/colors/. The Kolibri issue it resolved is here...