Closed
Bug 1608879
Opened 5 years ago
Closed 5 years ago
Setting the value of an <input type="date" disabled> has no effect
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1465979
People
(Reporter: bugzilla, Unassigned)
Details
Attachments
(1 file)
918 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
- Open the HTML file attached to this ticket
- Initialize the date field with a value
- Make the field disabled or read-only using the provided button
- Try the mutation button (change field value or clear using empty string/null)
Actual results:
- Using the set value buttons with an actual date sets the value of the disabled field
- The Set empty string / Set null button has no effect
Expected results:
- All mutation buttons should work the same, not matter the disabled/readonly state. At least though setting a new value and setting an empty value should behave the same.
Background:
The HTML 5.3 spec says about disabled :
A form control that is disabled must prevent any click events that are queued on the user interaction task source from being dispatched on the element.
So it states that only USER INTERACTION should be prevented, not script interaction. I could not find any hint, that clearing the field should be prevented.
Comment 1•5 years ago
|
||
seems related to Bug 1465979
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Ah yes it looks like an exact duplicate. I am sorry... My Google-Fu is weak.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•