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
Describe the bug
Whenever the prop callToActionMode is set to button, a button is renderd inside an anchor tag. This button element is not valid content for an anchor element. As per documentation:
No descendant may be interactive content or an a element, and no descendant may have a specified tabindex attribute.
To Reproduce
Steps to reproduce the behavior:
Add info card to your template with callToActionMode set to button
Inspect the button
See that it is nested inside an anchor element.
Expected behavior
The anchor should be styled as a button, or it should be a button element. But not nested.
Screenshots
Desktop (please complete the following information):
*
Smartphone (please complete the following information):
*
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever the prop
callToActionMode
is set to button, a button is renderd inside an anchor tag. This button element is not valid content for an anchor element. As per documentation:No descendant may be interactive content or an a element, and no descendant may have a specified tabindex attribute.
To Reproduce
Steps to reproduce the behavior:
callToActionMode
set to buttonExpected behavior
The anchor should be styled as a button, or it should be a button element. But not nested.
Screenshots
Desktop (please complete the following information):
*
Smartphone (please complete the following information):
*
The text was updated successfully, but these errors were encountered: