New issue
Advanced search Search tips

Issue 786480 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-03-20
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Task



Sign in to add a comment

Gather data on synthesized click()s to input elements with type=color/date/datetime-local/month/time/week

Project Member Reported by smcgruer@chromium.org, Nov 17 2017

Issue description

There is an ongoing discussion on the correct behavior for synthesized click()s on input elements with type=date (https://github.com/whatwg/html/issues/3232#issuecomment-345111590) The tl;dr is that the spec says a synthesized click() in this case should do nothing, but browsers are inconsistent in their implementation.

We need to gather some data on which (and how many) sites synthesize click()s on input type=date elements, and why they are doing so. This should let us continue the spec conversation with more understanding of the impact involved.
 
A good start, I think, would be a UseCounter that is ticked when we show a datepicker pop-up on Android for a synthesized click() on the input element. It may also be useful to just add an OS-agnostic UseCounter, as long as we can filter the results by OS. (It would actually be very useful to know how many sites are synthesizing click()s for type=date on desktop Chrome, because that does nothing today!).

Dave - is this bug appropriate for someone from your team to tackle?
Additional note: as per https://github.com/whatwg/html/issues/3232#issuecomment-345337810, Chrome also shows a UI for synthesized clicks() on type=file, for both Desktop and Android. We should add a UseCounter for that too.
Owner: dtapu...@chromium.org
Status: Assigned (was: Available)
Assigning to dtapuska@ to determine if his team is a good fit for doing this investigation.
Cc: rbyers@chromium.org
Ping; Dave, any chance of deciding if this is a good fit for your team (maybe a small Q1 OKR?)
Cc: tkent@chromium.org
This probably should be done by the forms team which owns the input fields.

tkent@ WDYT?
Cc: hayato@chromium.org keishi@chromium.org
+ keishi@ as it appears it is a few more weeks until tkent@ is back.
Components: -Blink>Input Blink>Forms>Date
Owner: ----
Status: Untriaged (was: Assigned)

Comment 8 by tkent@chromium.org, Jan 9 2018

Cc: -tkent@chromium.org -rbyers@chromium.org -keishi@chromium.org -hayato@chromium.org
Status: Available (was: Untriaged)
Cc: tkent@chromium.org rbyers@chromium.org
tkent@ - I'm not clear why you un-cc'd a bunch of people here (including yourself) without comment? Dave and I are trying to determine who the correct owner for this data collection would be.

Comment 10 by tkent@chromium.org, Jan 11 2018

Labels: -Type-Bug M-65 Type-Task
smcgruer@, HTML/Forms team is responsible for <input type=date> implementation and specification. The team will handle this, probably before the next branch.

Comment 11 by tkent@chromium.org, Jan 11 2018

Labels: OS-Android

Comment 12 by tkent@chromium.org, Jan 11 2018

Cc: -tkent@chromium.org
Labels: OS-Chrome OS-Linux OS-Mac OS-Windows
Owner: tkent@chromium.org
Status: Started (was: Available)
Summary: Gather data on synthesized click()s to input elements with type=color/date/datetime-local/month/time/week (was: Gather data on synthesized click()s to input elements with type=date)
I found this issue affected type=color on desktop too.

Comment 14 by tkent@chromium.org, Jan 11 2018

NextAction: 2018-03-20
This is awesome! Thank you very much for adding the UseCounters so quickly tkent@ :)
I linked to the resulting use counter data here:
https://github.com/whatwg/html/issues/3232#issuecomment-371183100
Commented on https://github.com/whatwg/html/issues/3232#issuecomment-371184702 that I think that this should be fixed in Firefox.
The NextAction date has arrived: 2018-03-20
Status: Fixed (was: Started)

Sign in to add a comment