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
Then switch disabled to true. Then to false. At that moment the following error is thrown:
Location where it fails:
In both cases (enabled and disabled) the tooltip still renders fine though. But somehow the Tooltip doesn't find the popover content when switching to the enabled state.
Fix can be to just play safe and only call setAttribute when the popover content was found. So in tooltip.component.ts just do
@koenvd What you're currently doing is wrapping a tooltip within a tooltip and I believe that is causing this issue. For accessibility purpose, starting v11, cds-icon-button component is wrapped in cds-tooltip.
To resolve this, you can change the above code to the following:
But I noticed before the tooltip was appearing when the button was disabled. So we could explain in the tooltip why the button was disabled. Now the tooltip is not appearing when the button is disabled.
But I noticed before the tooltip was appearing when the button was disabled. So we could explain in the tooltip why the button was disabled. Now the tooltip is not appearing when the button is disabled.
@koenvd, that is the current behavior defined in Carbon. I'll see if I can add a showTooltipWhenDisabled flag so you can show the tooltip!
To reproduce create a template containing this:
Then switch disabled to
true
. Then tofalse
. At that moment the following error is thrown:Location where it fails:
In both cases (enabled and disabled) the tooltip still renders fine though. But somehow the
Tooltip
doesn't find the popover content when switching to the enabled state.Fix can be to just play safe and only call
setAttribute
when the popover content was found. So intooltip.component.ts
just doBut I think something more fundamental is going wrong if I read the comments above those lines.
Probably there's a better fix?
The text was updated successfully, but these errors were encountered: