-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(leadspace): in storybook adding long copy to copy knob led to button being clipped away #12117
fix(leadspace): in storybook adding long copy to copy knob led to button being clipped away #12117
Conversation
✅ Deploy Preview for ibm-dotcom-web-components ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for ibm-dotcom-web-components-react-wrap ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this fixes the medium
leadspace, super
, tall
, and short
still have the ability to overflow & clip
@andy-blum This latest commit will address your last comment. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm seeing a visual regression here for the default values. Most obvious in Super. Comparing current v2 to the deploy preview here:
Monosnap.screencast.2024-11-22.11-36-35.mp4
As a sidenote, I was surprised to realize that the Leadspace stories aren't represented in Percy.
Closes #12114 |
Hey there! This issue/pull request was referenced in recently released v2.16.0. |
Related Ticket(s)
ADCMS-6827
Description
Adding long text to the leadspace copy knob leads to clipping the text & CTAs.
Issue:
Fixed:
NOTE
There's an apparent bug in all heading/title knobs in all components, when you try to modify it, we get the below error.
I've been trying to debug this error, but with @m4olivei 's help, we found out it's an issue that's been sitting there for a while now, so It would just be very time consuming for the tiny fix that was the original scope of this ticket