@leabankab/component-library 8.9.1 → 8.11.0

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 8.11.0
+
+### Minor Changes
+
+- 1bea934: - New `Loader`, the library's default loading indicator. It shows the pulse, and with `status="done"` it cross-fades into the check with its confetti. It takes `size`, `color`, `minLoadingMs`, `loadingLabel` and `doneLabel`, and announces each state to screen readers.
+  - `PulseAnimation` takes a `color` (`"primary"` or `"tertiary"`, default `"primary"`).
+  - `StatusAnimation` is deprecated: use `<Loader status={loading ? "loading" : "done"} />`, which renders the same thing. It keeps working, and its pulse now follows `color` too, so `color="tertiary"` shows a teal pulse where it used to be purple.
+  - In `tertiary`, the check of `CheckAnimation` and `StatusIcon` and the spinner of the pulse are dark instead of white, so they meet contrast on teal.
+
+## 8.10.0
+
+### Minor Changes
+
+- 0953963: `AlertBanner` in `@leabankab/component-library/website`: the icon is now red by default, where it was the section's text colour, and the new `color` prop sets it to another status (`"warning"`, `"info"`, `"success"`) or back to the section's text colour (`"inherit"`). On a dark section (`surface` `contrast` or `contrast-accent`) the icon takes a lighter step of its colour by itself, so it stays 3:1 or more against the band. The title and the text keep the section's colour. An image passed as `icon` keeps its own colours.
+- 6c907da: `CookieConsentProvider` in `@leabankab/component-library/cookie-consent/react` takes `onConsentChange` and `autoOpen`, and no longer opens the dialog by itself for crawlers. An app that passes neither behaves as before, the cookie and `COOKIE_CONSENT_REVISION` are unchanged, and visitors keep their consent.
+
+  - `onConsentChange?: (state: ConsentState) => void`: called once after load when there is a valid stored consent, then whenever the choice changes (the first choice, a change, or a step back to necessary only). Never with `null`, and not when the same choice is saved again. Called once per change, also under React StrictMode and when `initCookieConsent` was called elsewhere first. The latest function is the one called, so an inline arrow function is fine. An error thrown in it is reported with `reportError`, and the choice is still saved. Use it for Google Consent Mode, the dataLayer or starting analytics; render the provider through a client component of your own to pass it from a server layout.
+  - `autoOpen?: boolean`, default `true`: `false` keeps the dialog from opening by itself while the visitor has yet to choose, for example on the cookie policy page, which the intro's link opens in a new tab. Until then only necessary cookies are used. `openSettings` and `openCookieSettings` still open it, and it still can't be dismissed without a choice. When it turns `true` with no consent yet, the dialog opens.
+  - Crawlers and audit tools (a user agent with `bot`, `crawl`, `spider`, `slurp`, `teoma` or `lighthouse`) get the page without the dialog, as they did before 8.1.1. The stored consent is still read for them, and browser automation such as Playwright still gets the dialog.
+  - `useCookieConsent().consent` keeps the same object when a save doesn't change the choice, so its consumers don't re-render.
+  - `CookieConsentCopy`: `policyLinkLabel` and `policyLinkUrl` are optional and marked unused. The dialog never rendered them; the link to the cookie policy belongs in `intro`. Passing them still compiles.
+
+  See Docs/Cookie Consent.
+
 ## 8.9.1
 
 ### Patch Changes