Skip to content
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

Notice variant Toast breaks Pager buttons when it appears #6730

Closed
1 task done
PaulSumner-Sage opened this issue May 10, 2024 · 2 comments · Fixed by #6736
Closed
1 task done

Notice variant Toast breaks Pager buttons when it appears #6730

PaulSumner-Sage opened this issue May 10, 2024 · 2 comments · Fixed by #6736

Comments

@PaulSumner-Sage
Copy link
Contributor

Description

Having a Table Pager at the bottom of the page and popping a Notice variant Toast blocks mouse clicks on the existing pager buttons.
Video attached to related JIRA ticket showing behaviour with detailed steps to replicate

Reproduction

https://carbon.sage.com/?path=/story/toast--notice

Steps to reproduce

No response

JIRA ticket numbers (Sage only)

SBS-95451

Suggested solution

No response

Carbon version

130.0.0

Design tokens version

No response

Relevant browsers

Chrome

Relevant OSs

MacOS

Additional context

No response

Confidentiality

  • I confirm there is no confidential or commercially sensitive information included.
@PaulSumner-Sage PaulSumner-Sage added Bug triage Triage Required labels May 10, 2024
@edleeks87
Copy link
Contributor

FE-6576

@edleeks87 edleeks87 added On Backlog and removed triage Triage Required labels May 14, 2024
nuria1110 added a commit that referenced this issue May 16, 2024
The margin-top on a "notice" Toast would prevent elements behind it from being clicked.

fix #6730
carbonci pushed a commit that referenced this issue May 20, 2024
### [135.1.1](v135.1.0...v135.1.1) (2024-05-20)

### Bug Fixes

* **toast:** margin-top on notice variant prevents elements being clicked ([1732886](1732886)), closes [#6730](#6730)
@carbonci
Copy link
Collaborator

🎉 This issue has been resolved in version 135.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants