Closed Bug 1530239 Opened 5 years ago Closed 5 years ago

css transition events must fire even if an element is disabled

Categories

(Core :: DOM: Events, enhancement, P1)

Product:
Core
Component:
DOM: Events
Platform:
Unspecified
All
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla67
Tracking Flags:
Tracking Status
firefox67 --- fixed

People

(Reporter: marcosc, Assigned: marcosc)

References

Details

(Keywords: dev-doc-complete, parity-chrome, site-compat)

Attachments

(1 file)

Bug 1530239 - css transition events must fire even if an element is disabled. r=smaug
47 bytes, text/x-phabricator-request
Details | Review

Currently transitionstart and transitionend events won't fire if an input element is disabled.

Expected:
they should fire.

Actual:
they don't fire.

Bug 329509 contains a reduced test case.

Assignee: nobody → mcaceres

Setting to p1 as I'm preparing a patch for it.

Priority: -- → P1
Keywords: parity-chrome
Summary: transition events should fire even if input element is disabled → css transition events must fire even if an element is disabled

CSS Transitions were not firing when elements were disabled.

Pushed by mcaceres@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c89f5d4d2e86
css transition events must fire even if an element is disabled. r=smaug

https://hg.mozilla.org/mozilla-central/rev/c89f5d4d2e86

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox67: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/15642 for changes under testing/web-platform/tests

Note to MDN team: I've added a note to the Fx67 rel notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/67#DOM_events

not sure what else we need in terms of docs.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: