Closed Bug 1754841 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 32804 - Remove disabled condition from :active matching

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 32804 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/32804
Details from upstream follow.

Joey Arhar <jarhar@chromium.org> wrote:

Remove disabled condition from :active matching

Fixed: 1287171
Change-Id: Idab2abbbc94cc73fac70e34ef391c5d63518d569

Reviewed-on: https://chromium-review.googlesource.com/3453424
WPT-Export-Revision: 8b7a6db0312239a7cb4a1ac9086071b4b8457dff

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, and Chrome on GitHub CI

Total 1 tests and 5 subtests

Status Summary

Firefox

OK : 1
PASS: 4
FAIL: 1

Chrome

OK : 1
PASS: 4
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/html/semantics/selectors/pseudo-classes/active-disabled.html
Clicking on a disabled textarea should make it get the :active selector.: FAIL (Chrome: PASS)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0d506833c31b [wpt PR 32804] - Remove disabled condition from :active matching, a=testonly https://hg.mozilla.org/integration/autoland/rev/cf01f380f1da [wpt PR 32804] - Update wpt metadata, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2fac34327c50 [wpt PR 32804] - Remove disabled condition from :active matching, a=testonly https://hg.mozilla.org/integration/autoland/rev/9a318cc66cd1 [wpt PR 32804] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.