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
One is that the ::after pseudo-element still occupies space underneath the tab-content.
This could be solved by adding overflow: hidden to the mixin
The second is that the height which is set here: src/elements/tabs/tab-group/tab-group.ts#L247 is too small because the margin-top of the paragraph inside isnt included.
This can also be seen in the storybook by changing to "Tab title four" the scrollbar appears.
This could be solved by moving the mixin from the tab-group to the tab itself.
Steps to reproduce the issue
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Bug type
Functionality
It affects the following packages
Components
Which version of Lyne Components are you using
1.0.0
Operating system
No response
Browser / Browser version
No response
Input mode
None
Additional settings
No response
What happened?
Found a bug on a mobile-sized screen when combining map-container with tab-group. An unnecessary scrollbar ist shown.
Reproduction: https://stackblitz.com/edit/tab-content-after-creates-scrollbar-inside-map-container?file=src%2Fmain.html
After some testing it seems to be a combination of 2 issues related to this mixin: src/elements/tabs/tab-group/tab-group.scss#L21
One is that the
::after
pseudo-element still occupies space underneath the tab-content.This could be solved by adding
overflow: hidden
to the mixinThe second is that the height which is set here: src/elements/tabs/tab-group/tab-group.ts#L247 is too small because the margin-top of the paragraph inside isnt included.
This can also be seen in the storybook by changing to "Tab title four" the scrollbar appears.
This could be solved by moving the mixin from the tab-group to the tab itself.
Steps to reproduce the issue
Relevant log output
No response
The text was updated successfully, but these errors were encountered: