Skip to content

fix(w3c/sotd): ensure REC is next step after CR (process 2025) #3688

fix(w3c/sotd): ensure REC is next step after CR (process 2025)

fix(w3c/sotd): ensure REC is next step after CR (process 2025) #3688

Triggered via pull request February 19, 2026 14:35
Status Failure
Total duration 2m 34s
Artifacts

pr.yml

on: pull_request
Check linting issues
34s
Check linting issues
Headless Tests
59s
Headless Tests
Validate HTML
34s
Validate HTML
Matrix: test-karma
Fit to window
Zoom out
Zoom in

Annotations

7 errors
Headless Tests
Process completed with exit code 3.
Karma Unit Tests (ChromeHeadless)
Process completed with exit code 1.
Karma Unit Tests (ChromeHeadless): tests/spec/core/validators-spec.js#L65
Core - Validators validateDOMName generates an error if the attribute name is invalid attribute name: -crossorigin: Expected true to be false.
Karma Unit Tests (ChromeHeadless): tests/spec/core/validators-spec.js#L37
Core - Validators validateDOMName generates an error if the element name is not valid element name: crypto$: Expected true to be false.
Karma Unit Tests (ChromeHeadless): tests/spec/core/dfn-spec.js#L424
Core — Definitions CSS class based definitions types handles attributes Expected [ ] to have size 1.
Karma Unit Tests (FirefoxHeadless)
The strategy configuration was canceled because "test-karma.ChromeHeadless" failed
Karma Unit Tests (FirefoxHeadless)
The operation was canceled.