Open Bug 1421555 Opened 3 years ago Updated 2 years ago

Validity State's badInput is not getting set for partially filled date

Categories

(Core :: DOM: Core & HTML, defect, P3)

57 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: parthivshah91, Unassigned, NeedInfo)

Details

Attachments

(1 file)

Attached file demo.html
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce:

1. Open demo.html page.
2. Enter only year as 1991. Do not enter month and date.
3. Click on anywhere other than date control on the page to fire blur event.
4. Observe date is not filled with today's date.


Actual results:

Date field remains as it is and not filled by today's date.


Expected results:

Date field should be filled with today's date.
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Priority: -- → P1
Priority: P1 → P3
I would like to know why it's taking so long to confirm this bug? and why it's priority was changed from P1 to P3?
Is there any workaround for this issue?
This issue is severe for us as it prevents us to use native date picker control. Can you please give me estimated time to fix this or any workaround for it?
(In reply to Parthiv Shah from comment #1)
> I would like to know why it's taking so long to confirm this bug? and why
> it's priority was changed from P1 to P3?
> Is there any workaround for this issue?

Basically because this is in the wrong component, we don't have anything to do with form validation in layout :)

Mike, I saw you made recent changes to the datetime bindings, would you be interested in looking into this or know someone who could?
Component: Layout: Form Controls → DOM: Core & HTML
Flags: needinfo?(mconley)
smaug has been stomping around in this area recently, and I suspect this is lower down in the datetime widgetry, and hasn't much to do with the panel / popup. smaug, any idea what's going on here?
Flags: needinfo?(mconley) → needinfo?(bugs)
Any update on this issue? As this issue forces us to use custom date picker control. Let me know if you have any idea on whether and when this will be fixed?
You need to log in before you can comment on or make changes to this bug.