You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate intermittent WebKit contrast failure during Reveal entrance #12
The browser check for PR #11 at commit 674b4dedb181ba32144a5b307373698078adcd91 reported one failure in the light-theme Reveal catalog example. The tested file tree was unchanged by the DCO sign-off update and had passed earlier.
Evidence: browser run, first job 128889017266: 58 passed, 1 skipped, 1 failed. Test: all component details: light accessibility rules and mobile overflow (WebKit), component reveal, axe rule color-contrast, target article > p. The run retains its browser-evidence artifact.
The contrast scan starts immediately after checking the heading; Reveal uses a finite opacity entrance animation. This suggests an animation/scan timing issue, but the root cause still needs confirmation. A single failed-job retry is being used to distinguish intermittency; this issue retains the original failure regardless of its result.
Acceptance:
Confirm whether the scan observes the entrance animation or a persistent contrast problem.
If timing is the cause, wait for finite entrance animations before scanning, as the website suite already does; keep contrast rules enabled and preserve separate motion/reduced-motion coverage.
Repeat the affected WebKit case and run the browser suite; retain concise evidence.
The single bounded retry passed with no code changes: browser job 128910742220, run 42532324492. The same signed commit is green across DCO, native and browser verification. This confirms intermittency, but does not by itself establish the root cause. Keep this issue open for a focused investigation.
Activity
wilkinsantana commentedon Nov 9, 2026
The single bounded retry passed with no code changes: browser job
128910742220, run42532324492. The same signed commit is green across DCO, native and browser verification. This confirms intermittency, but does not by itself establish the root cause. Keep this issue open for a focused investigation.