> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/sandbox/icon-behaviour.md).

# Icon behaviour

Proves what the package selector does for each combination of logo and iconOnly, including a logo filename that does not exist.

Five cards, one per case. Open the browser console before clicking anything: two of these are meant to log an error there and nothing on the page.

| Card                       | Expected                                                                                                     |
| -------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Icon and label             | Logo, then the label. This is the default when `iconOnly` is absent.                                         |
| Icon only                  | Logo alone. The label is still the accessible name and the tooltip.                                          |
| No logo declared           | Label alone. Nothing logged, this is a normal card.                                                          |
| Logo that does not resolve | Label alone, plus a console error naming the file.                                                           |
| Bad logo, icon only        | Label alone. `iconOnly` is ignored when no icon resolved, otherwise the card would be empty and unclickable. |

{% @harness-package-selector-staging/package-selector platforms="%5B%7B%22label%22%3A%22Icon%20and%20label%22%2C%22slug%22%3A%22icon-and-label%22%2C%22path%22%3A%22sandbox%2Far-quickstart%2Fdocker-quickstart%22%2C%22logo%22%3A%22docker-logo.svg%22%2C%22logoSize%22%3A24%7D%2C%7B%22label%22%3A%22Icon%20only%22%2C%22slug%22%3A%22icon-only%22%2C%22path%22%3A%22sandbox%2Far-quickstart%2Fdocker-quickstart%22%2C%22logo%22%3A%22maven-logo.svg%22%2C%22iconOnly%22%3Atrue%7D%2C%7B%22label%22%3A%22No%20logo%20declared%22%2C%22slug%22%3A%22no-logo%22%2C%22path%22%3A%22sandbox%2Far-quickstart%2Fdocker-quickstart%22%7D%2C%7B%22label%22%3A%22Logo%20that%20does%20not%20resolve%22%2C%22slug%22%3A%22bad-logo%22%2C%22path%22%3A%22sandbox%2Far-quickstart%2Fdocker-quickstart%22%2C%22logo%22%3A%22there-is-no-such-logo.svg%22%2C%22logoSize%22%3A24%7D%2C%7B%22label%22%3A%22Bad%20logo%2C%20icon%20only%22%2C%22slug%22%3A%22bad-logo-icon-only%22%2C%22path%22%3A%22sandbox%2Far-quickstart%2Fdocker-quickstart%22%2C%22logo%22%3A%22also-missing-logo.svg%22%2C%22iconOnly%22%3Atrue%7D%5D" search="false" disableSort="true" iconLibrary="<https://developer.harness.io/sandbox/logo-library>" %}

Every card points at the same Docker page, so a click that lands anywhere else means the path handling is wrong rather than the icon handling.

Both console errors name the file: one from the worker, visible with `gitbook integrations events list harness-package-selector-staging`, and one from the webframe in the browser console. Readers see neither.

{% @harness-feedback/feedback module="sandbox" pagePath="sandbox/icon-behaviour" %}