Skip to content
Pull request

fix: [#1592] Fixes bug where Document.activeElement is set to the wrong target when triggering HTMLSelectElement.focus #1242

Sign in to view logs

fix: [#1592] Fixes bug where Document.activeElement is set to the wrong target when triggering HTMLSelectElement.focus

fix: [#1592] Fixes bug where Document.activeElement is set to the wrong target when triggering HTMLSelectElement.focus #1242

Triggered via pull request November 11, 2024 20:25
@capricorn86capricorn86
opened #1600
1592-unable-to-get-focused-htmlselectelement-since-1500
Status Failure
Total duration 2m 55s
Artifacts –

pull_request.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
build (20)
happy-dom#test: command (/home/runner/work/happy-dom/happy-dom/packages/happy-dom) /opt/hostedtoolcache/node/20.18.0/x64/bin/npm run test exited (1)
test/fetch/SyncFetch.test.ts > SyncFetch > send() > Updates cache after a failed revalidation with a "If-Modified-Since" request for a GET response with "Cache-Control" set to a "max-age".: packages/happy-dom/test/fetch/SyncFetch.test.ts#L2647
AssertionError: expected 'some text' to be 'some new text' // Object.is equality Expected: "some new text" Received: "some text" ❯ test/fetch/SyncFetch.test.ts:2647:18
build (20)
Process completed with exit code 1.
build (18)
The job was canceled because "_20" failed.
build (18)
The operation was canceled.
build (22)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/