-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
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
AppMenu: Not able to set module tabs appMenuTriggerText to empty string #4590
Comments
As an alternate workaround does setting it to |
@tmcconechy Forgot to mention that I've already tested that too, with the same outcome as So in order for the menu icon to look centered on hover (before one clicks it) when there isn't a trigger text in the |
Is this using this example https://master-enterprise.demo.design.infor.com/components/tabs-module/example-app-menu-button.html but just without the Menu text? Or maybe you werent aware of this configuration? The more i look at this it looks like that example |
Correct, I'm using that appMenuTrigger with appMenuTriggerText set to |
QA Passed. |
Describe the bug
For the module tabs you can provide options to have and set the application menu trigger text:
If
appMenuTrigger
is true butappMenuTriggerText
is not set, it will default toLocale.translate('AppMenuTriggerText')
. We would like to be able to not have a title text i.e. "" (blank). Currently, if we provide empty string it defaults to 'Menu' due to the following on line 543 in tabs.js:So we currently specify
" "
a space which won't evaluate false, but has the side effect of the icon becomes misplaced.To Reproduce
Steps to reproduce the behavior:
Expected behavior
When provide empty string i.e.
""
there shouldn't be a default.Version
Screenshots
The menu icon becomes misplaced by adding the space:
Platform
Additional context
Using the nullish coalescing operator (??) (CanIuse) instead of the logical or (||) would let empty string through, but at the same time set the default text appMenuTriggerText
is null or undefined.
The text was updated successfully, but these errors were encountered: