While the logo is still loading, the wordmark is held unseen like the built-in image, so it does not flash up and disappear.
A custom APP_NAME still shows.
Without a custom logo the page is unchanged, except the footer now says "inbuxa Webmail" (component name, capital W).
Translation: one new string, Powered by {product} v{version}, added to all ten catalogs (AI-written).
Checked locally: typecheck, npm test (192 files, 1618 tests, incl. a new component test for the default, custom and loading states), release-version.test.sh, build, i18n:check. Screenshots taken in headless Chromium against a stub /api/logo, both with and without a custom logo.
Fixes #122.
With a logo set on the mail server, the sign-in card no longer shows the inbuxa wordmark under it. inbuxa is credited in the footer instead:
> Powered by [inbuxa Webmail](https://inbuxa.org) v27.1-…
> AGPL-3.0 source
- The heading stays for screen readers (`sr-only`).
- While the logo is still loading, the wordmark is held unseen like the built-in image, so it does not flash up and disappear.
- A custom `APP_NAME` still shows.
- Without a custom logo the page is unchanged, except the footer now says "inbuxa Webmail" (component name, capital W).
**Translation:** one new string, `Powered by {product} v{version}`, added to all ten catalogs (AI-written).
**Checked locally:** typecheck, `npm test` (192 files, 1618 tests, incl. a new component test for the default, custom and loading states), `release-version.test.sh`, build, `i18n:check`. Screenshots taken in headless Chromium against a stub `/api/logo`, both with and without a custom logo.
jcoffey-dev
added this to the 27.1 milestone 2026-11-19 17:34:05 +00:00
With a logo set on the mail server, the sign-in card showed it and then
the inbuxa wordmark right under it: two logos crowding each other (#122).
Under a custom logo now:
- the wordmark is gone; the heading stays for screen readers (sr-only);
- the footer credits inbuxa as "Powered by inbuxa Webmail v…", with the
name linking to inbuxa.org, and the AGPL-3.0 source link on the line
below. A bare "inbuxa.org" under somebody else's logo read as a stray
URL.
While the logo is still being asked for, the wordmark is held unseen like
the built-in image, so it doesn't flash up and vanish. A name the
administrator set (APP_NAME) still shows: they chose it. Without a custom
logo the page is unchanged, apart from "inbuxa Webmail" now capitalised
as the component name.
The new string is added to all ten catalogs (AI-written, like the rest
of each catalog). Tests: a component test for the default, custom and
loading states.
Fixes#122
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #122.
With a logo set on the mail server, the sign-in card no longer shows the inbuxa wordmark under it. inbuxa is credited in the footer instead:
sr-only).APP_NAMEstill shows.Translation: one new string,
Powered by {product} v{version}, added to all ten catalogs (AI-written).Checked locally: typecheck,
npm test(192 files, 1618 tests, incl. a new component test for the default, custom and loading states),release-version.test.sh, build,i18n:check. Screenshots taken in headless Chromium against a stub/api/logo, both with and without a custom logo.