Paul BakausandClaude 1fec78d3d2 fix: keep zero-offset glow findings when the surface is unreadable ...

The browser glow adapter abstained from the whole element when
resolveBackgroundInfo reported an unreadable surface, which also dropped
zero-offset chromatic halo findings that do not depend on the background
at all. It now skips only the gradient hunt past the unreadable layer and
scores the halo tell against a null surface, matching what the static
loop already did. Fixture cases pin both sides: the halo over a url()
image ancestor flags in both engines, and an offset chromatic shadow on
the same unknown surface stays abstained.

Also hardens the currentcolor background substitution with the
parseColorResolved fallback used by the text-color path, and adds fixture
coverage proving tokenized currentcolor surfaces already resolve through
the static cascade (flag when knowable, abstain when the token is
undefined).

Addresses Cursor Bugbot review findings on PR #541.

AI-assisted-by: Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-11 13:50:49 -04:00

..

bin

Fix: skip POSIX hook guard on Windows installs (#452) (#453)

2026-08-03 14:55:01 -07:00

engine

fix: keep zero-offset glow findings when the surface is unreadable

2026-08-11 13:50:49 -04:00

lib

Simplify CSS color channel parsing (#520)

2026-08-05 15:28:17 -07:00