Open
Bug 1973497
Opened 3 days ago
Updated 15 hours 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
()
ASSIGNED
Tracking | Status | |
---|---|---|
firefox142 | --- | affected |
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•3 days 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•15 hours ago
|
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•