You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The height of the KModal should dynamically adjust to the height of the content it renders.
Actual behavior
If for some reason the content of the KModal is expanded after its first render, the KModal is expanded accordingly, but if it is then shrinked, the KModal remains with the height of the expanded content, and this can lead to cases like this:
If initially we have a componente with a description like this:
But then we want to delete it, we get this view:
Cases like this occur in several places where the height of some element varies while the modal is displayed.
Steps to reproduce the issue
Go to Studio and checkout the branch studio-usability-enhancements
Edit the content nodes of a channel
Edit the title and description of a node
Environment
OS: Ubuntu
Browser version: Chrome Version 122.0.6261.94 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
Hi @shrudge! No, the issue is in the correct repository. KDS is responsible for providing the components that will be used in other Kolibri products, you can learn more about KDS in the repo readme.
Product
Studio
Expected behavior
The height of the KModal should dynamically adjust to the height of the content it renders.
Actual behavior
If for some reason the content of the KModal is expanded after its first render, the KModal is expanded accordingly, but if it is then shrinked, the KModal remains with the height of the expanded content, and this can lead to cases like this:
If initially we have a componente with a description like this:
But then we want to delete it, we get this view:
Cases like this occur in several places where the height of some element varies while the modal is displayed.
Steps to reproduce the issue
studio-usability-enhancements
Environment
The text was updated successfully, but these errors were encountered: