diff --git a/packages/components/src/components/post-card-control/post-card-control.tsx b/packages/components/src/components/post-card-control/post-card-control.tsx index 36ebcae76e..024df1c94c 100644 --- a/packages/components/src/components/post-card-control/post-card-control.tsx +++ b/packages/components/src/components/post-card-control/post-card-control.tsx @@ -26,7 +26,7 @@ let cardControlIds = 0; /** * @class PostCardControl - representing a stencil component * - * @slot default - Content to place into the `default` slot.
Markup accepted: block content.
Even if it is generally possible, we do not recommend using interactive elements in this slot because the background of the card control is clickable. This can lead to confusion when the hit box of nested interactive controls is not clearly separated from the background, is invalid HTML and click events bubbling up to the card control will unexpectedly toggle it if they're not captured. More info: https://accessibilityinsights.io/info-examples/web/nested-interactive/
+ * @slot default - Content to place into the `default` slot.Markup accepted: block content.
Even if it is generally possible, we do not recommend using interactive elements in this slot because the background of the card control is clickable.
This can lead to confusion when the hit box of nested interactive controls is not clearly separated from the background, is invalid HTML and click events bubbling up to the card control will unexpectedly toggle it if they're not captured.
More info: https://accessibilityinsights.io/info-examples/web/nested-interactive/
Markup accepted: inline content.
It is only meant for img
or svg
elements and overrides the `icon` property.
Markup accepted: block content.
Even if it is generally possible, we do not recommend using interactive elements in this slot for accessibility reasons.
| -| `"icon"` | To insert a custom icon into the named `icon` slot.Markup accepted: inline content.
It is only meant for img
or svg
elements and overrides the `icon` property.
Markup accepted: block content.
Even if it is generally possible, we do not recommend using interactive elements in this slot because the background of the card control is clickable.
This can lead to confusion when the hit box of nested interactive controls is not clearly separated from the background, is invalid HTML and click events bubbling up to the card control will unexpectedly toggle it if they're not captured.
More info: https://accessibilityinsights.io/info-examples/web/nested-interactive/
Markup accepted: inline content.
It is only meant for img
or svg
elements and overrides the `icon` property.
Valid markup: block content.
Even if it is generally possible, we do not recommend using interactive elements in this slot because the background of the card control is clickable. This can lead to confusion when the hit box of nested interactive controls is not clearly separated from the background, is invalid HTML and click events bubbling up to the card control will unexpectedly toggle it if they're not captured. More info: https://accessibilityinsights.io/info-examples/web/nested-interactive/
Even if it is generally possible, we do not recommend using interactive elements in this slot because the background of the card control is clickable.
+This can lead to confusion when the hit box of nested interactive controls is not clearly separated from the background, is invalid HTML and click events bubbling up to the card control will unexpectedly toggle it if they're not captured. More info: https://accessibilityinsights.io/info-examples/web/nested-interactive/
+