• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

agama-project / agama / 30261829568
83%

Build:
DEFAULT BRANCH: master
Ran 27 Jul 2026 11:28AM UTC
Jobs 3
Files 1046
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

27 Jul 2026 11:24AM UTC coverage: 83.227% (+0.08%) from 83.148%
30261829568

push

github

web-flow
fix(web): avoid a flash from Agama colors to a product's own palette (#3749)

## Problem

When a product ships a custom appearance skin
(`assets/products/<id>.css`, see `doc/product_theming.md`), the browser
paints with Agama's stock colors first and only switches to the
product's palette once the product config
resolves from the backend and `useProductAppearance` injects the
stylesheet link. Anything rendered before that (most visibly the
full-screen loading spinner) shows the wrong colors, then flips. This is
a visible flash on
every load/reload of a themed product.

Light/dark/high-contrast already avoid the equivalent problem: a small
inline script in `index.html` applies the persisted choice before React
boots. The product skin had no equivalent.

## Fix

- `use-product-appearance.ts` now mirrors the active product id to
`localStorage` (`agm-product-id`), alongside the existing behavior of
injecting/updating the `<link rel="stylesheet"
href="assets/appearance/<id>.css">`.
- `index.html` gains a second pre-boot script, matching the existing
light/dark one: it reads `agm-product-id` and, if present, creates that
same `<link>` element (same id) before first paint. Once the app boots
and the real product resolves, `useProductAppearance` finds the existing
element by id and updates it in place rather than creating a duplicate.
- A missing/404 stylesheet is already harmless (documented in
`doc/product_theming.md`), so an unthemed product or a first-ever visit
behaves exactly as before.

Known, accepted trade-off: if the product changes between two loads, the
pre-paint script briefly shows the *previous* product's colors until the
real query resolves and swaps the stylesheet. Same category of trade-off
the existing script already accepts for OS-level "system" preference
changes between loads.

4917 of 6845 branches covered (71.83%)

Branch coverage included in aggregate %.

3 of 3 new or added lines in 1 file covered. (100.0%)

25609 of 29833 relevant lines covered (85.84%)

123.85 hits per line

Subprojects
ID Flag name Job ID Ran Files Coverage
3 web 30261829568.3 27 Jul 2026 11:28AM UTC 727
80.15
GitHub Action Run
1 rust 19474749743.1 18 Nov 2025 05:18PM UTC 185
22.45
GitHub Action Run
3 service 30083641564.3 24 Jul 2026 09:45AM UTC 319
92.41
GitHub Action Run
Source Files on build 30261829568
  • Tree
  • List 1046
  • Changed 3
  • Source Changed 2
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #30261829568
  • 34daa343 on github
  • Prev Build on master (#30260798705)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc