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
Need translation support to 'Expand/Collapse Header' tooltips for Dynamic page component
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
Angular: 15.2.0
Fundamental NGX (core, platform, cdk, i18n): 0.43.9
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Please provide relevant source code (if applicable).
@sreekanthkarini - can you please add the tag [P3.1] in the title of the message for tracking purpose @droshev - looks like this translation is missing checked for Portuguese and Deutsch languages
sreekanthkarini
changed the title
[Sourcing] Dynamic page component need translation support for 'Expand/Collapse Header' tooltips
[P3.1][Sourcing] Dynamic page component need translation support for 'Expand/Collapse Header' tooltips
Nov 20, 2023
Is this a bug, enhancement, or feature request?
feature
Describe your proposal.
Need translation support to 'Expand/Collapse Header' tooltips for Dynamic page component
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
Angular: 15.2.0
Fundamental NGX (core, platform, cdk, i18n): 0.43.9
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Please provide relevant source code (if applicable).
https://sap.github.io/fundamental-ngx/#/platform/dynamic-page
Please provide stackblitz example(s).
In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.
Did you check the documentation and the API?
Did you search for similar issues?
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: