Closed
Bug 1973497
Opened 11 months ago
Closed 10 months ago
Command & Commandfor: form buttons must explictly set type=button to be command buttons
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
142 Branch
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: keithamus, Assigned: keithamus)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
Button activation behaviour requires command & commandfor to be ignored if the button is a form participant without an explicit button type content attribute. Trunk currently dispatches command events for buttons with command/commandfor regardless of type.
| Assignee | ||
Comment 1•11 months ago
|
||
This refactoring aligns the button activation behaviour to the exact
steps specified in HTML, which has some small changes from the prior
implementation:
- button activation returns early after submitting, or resetting, not
triggering popovers or command/commandfor. - buttons with form owners and a type attribute in the Auto state must
return early, not triggering popovers or command/commandfor.
This also has some other non-observable changes to the code:
- collapses the HandleCommandForAction method directly into
ActivationBehavior. - adds code comments for each of the spec steps
Updated•11 months ago
|
Severity: -- → S3
Pushed by mozilla@keithcirkel.co.uk:
https://github.com/mozilla-firefox/firefox/commit/6282a5468b41
https://hg.mozilla.org/integration/autoland/rev/16ecb9de093b
Refactor HTMButtonElement::ActivationBehavior r=dom-core,edgar
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•10 months ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•