-
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
calcite-navigation-logo: allow slot/property for icon instead of image #7124
Comments
FYI: found a workaround by adding a do-nothing calcite-action to the 'navigation-action' slot of the calcite-navigation. Not ideal as we don't have the direct ability to disable pointer interactions and calcite-icon won't align correctly... but ok for now. |
Thanks @jgrayson-apl - this makes sense and was something we had considered but didn't add to the first iteration. |
**Related Issue:** #7124 ## Summary Adds `icon` and `iconFlipRtl` properties to `calcite-navigation-logo`. Because `calcite-navigation` and related components are offered in one scale, this unique `icon` case will use `scale="l"` due to the prominence and usage of the component, and to ensure `icon` adjacent to `thumbnail` are presented at equal sizes: <img width="558" alt="Screenshot 2023-10-25 at 12 18 31 PM" src="https://github.com/Esri/calcite-design-system/assets/4733155/fa49bc25-c5b1-4051-82b5-785ced404f17">
Installed and assigned for verification. |
Verified in <calcite-shell>
<calcite-navigation slot="header">
<calcite-navigation-logo heading="Whale sightings" icon="globe" description="2023 data observations" slot="logo">
</calcite-navigation-logo>
</calcite-navigation>
</calcite-shell> |
Description
For the new calcite-navigation-logo, please provide a slot/property for an icon instead of image as most of the time we don't have an application specific image and use a simple icon instead.
Acceptance Criteria
We need the ability to use an icon instead of a in image
Relevant Info
No response
Which Component
calcite-navigation-logo
Example Use Case
No response
Priority impact
p4 - not time sensitive
Esri team
N/A
The text was updated successfully, but these errors were encountered: