We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If show-notifications and notification-count are used in the ui5-shellbar, the notification badge remains even though notification-count is empty.
To reproduce
<ui5-shellbar id="shellbar" primary-title="Corporate Portal" secondary-title="secondary title" notification-count="99+" show-notifications
Isolated example https://sap.github.io/ui5-webcomponents/playground/components/ShellBar/
Expected behavior If the attribute "notification-count" is empty, the counter badge should no longer be displayed.
Context
Affected components @ui5/webcomponents-fiori ui5-shellbar
Priority: Medium
The text was updated successfully, but these errors were encountered:
Hi @maltenorstroem thanks for reporting, we address the issue with #3123
Sorry, something went wrong.
fix(ui5-shellbar): hide notification bubble if empty str (#3123)
33fde82
The notification bubble used to remain displayed when notification-count is an empty string. Fixes: #3121
ilhan007
Successfully merging a pull request may close this issue.
If show-notifications and notification-count are used in the ui5-shellbar, the notification badge remains even though notification-count is empty.
To reproduce
<ui5-shellbar id="shellbar" primary-title="Corporate Portal" secondary-title="secondary title" notification-count="99+" show-notifications
>Isolated example
https://sap.github.io/ui5-webcomponents/playground/components/ShellBar/
Expected behavior
If the attribute "notification-count" is empty, the counter badge should no longer be displayed.
Context
Affected components
@ui5/webcomponents-fiori ui5-shellbar
Priority: Medium
The text was updated successfully, but these errors were encountered: