DocumentationAll ComponentsContact usChangelog
IntroductionAccessBug Reports and Feature RequestsContactInstallationAngularReactUsageAI UsageVirtual ScrollingBlackduckPortalsData FormatsMobile and TouchFormsDepth levels and stacking contextsTool IntegrationHow to use SkeletonsAngular PackageMicrofrontends

Themes and Customization

ThemesCSS custom propertiesBuild Time ThemingFontsTool SupportMigrationguide and DeprecationsV3 to V4V2 to V3V1 to V2

Known Issues and Workarounds

Invisible Tooltips v3.16.0 or higherCombobox initially open menu width not alignedSetting tabindex on disabled componentsTemplating into default SlotsTruncation limitation in title stackPopover position in small iframesStorybook problemsBrowser bugsFlex layout subsampling issueDead Keys in NumberInputsInteractive icon hitarea

Blackduck is the standard tool within ZEISS to monitor dependencies of software projects and scan for potential security issues in those dependencies. You can find more general information about the usage of Blackduck within ZEISS in the wiki: https://wiki.zeiss.com/spaces/FOSS/pages/387680848/Overview+BlackDuck

All ZUi-Web artifacts are automatically scanned by Blackduck. This way, you can add ZUi-Web as dependency to your project in Blackduck and get notified about potential issues coming from ZUi-Web.

You can find the artifacts here:

Before you can see and use these Blackduck artifacts, you will need to request access to Blackduck itself. See the wiki documentation for this.

In the past, you needed to request access to the ZUi-Web artifacts explicitly to be able to see and use them in Blackduck.

This shouldn't be the case anymore and you should be able to find the artifacts in Blackduck without additional configuration needed. However, this might be a subject to change in the future and might not be in our hand as ZUi-Web team.

Matching unmatched components (e.g. ZUi-Web) in Blackduck

Sometimes Blackduck detects ZUi-Web (or other dependencies) as unmatched components or unmatched IDs/files. You can manually map these to the correct ZUi-Web project version:

  1. Open your Blackduck project and go to the Source tab.
  2. Apply the filter “Unmatched IDs” (or “Unmatched Files”).
  3. Identify the relevant unmatched entries (for example ones related to ZUi-Web).
  4. Click on the “…” menu of the entry and choose Edit adjustment.
  5. Map it to the appropriate ZUi-Web project version (e.g. the matching @zeiss/zui artifact).
  6. After saving, the component will automatically disappear from the Unmatched Components tab.

A short video showing this workflow (using ZUi-Web as an example) plus a short description is available in the FOSS wiki (Requires login with your ZEISS account.)

If you have trouble using ZUi-Web artifacts in your Blackduck project, please use our tech-support channel in Teams.