I would be happy to start without timezone support because currently we're not including that data either (we just assume local time). We do need a higher precision than just the date. Take for example https://commons.wikimedia.org/wiki/File:%22_Tomb_of_Sher_Shah_Suri_%22.jpg . Here it's relevant that it's taken at "16:52:56" because it's an indication of the time of the day. In the future I probably want to query for images of a certain location taken during the gold hour (https://en.wikipedia.org/wiki/Golden_hour_(photography)). If I recall correctly, the precision is in the configuration somewhere so could probably just be changed for Commons.

@Cparle to clean up Acceptance Criteria and add [L] to reflect estimation

Change 567125 had a related patch set uploaded (by Matthias Mullie; owner: Matthias Mullie):
[mediawiki/extensions/WikibaseMediaInfo@master] [WIP] Implement support for time datavalue

https://gerrit.wikimedia.org/r/567125

Patch is in code review.

Here are a few screenshots to confirm with design:

Initial (empty) input field:

Once user starts typing time. the thing will expand to display the formatted version & allow precision & calendar to be overwritten (pretty much exactly like currently on Wikidata)

Example of changing precision (which also affects the formatted version of the data, no longer showing the day)

After clicking "add", the time statement is rendered like all others.

And here's what things look like for qualifiers. Basically just the same thing:

Update after design feedback: checkboxes are gone & dropdowns always active. They'll automatically update with what's inferred from time input, until something else is manually selected.

Ah. This perhaps creates a new problem - no explanation of what the dropdowns are. 😸 Can we just have "precision" and "calendar" labels without checkboxes? [I know you sent some sample images of your intent to the Slack on Thursday, but I was out and just saw them now. Sorry. This is why I don't take breaks.]

In T231979#5880295, @matthiasmullie wrote:

Update after design feedback: checkboxes are gone & dropdowns always active. They'll automatically update with what's inferred from time input, until something else is manually selected.

Does this work?

Note: As shared in the design review a few weeks ago with @Ramsey-WMF, the primary progressive button representation is meant to only be used for one most important action per view.
“Add” should be a progressive button instead.

Looks good!

In T231979#5900602, @matthiasmullie wrote:

Does this work?

Thanks. We're planning to have that change ready in the next batch of updates.

In T231979#5900784, @Volker_E wrote:

Note: As shared in the design review a few weeks ago with @Ramsey-WMF, the primary progressive button representation is meant to only be used for one most important action per view.
“Add” should be a progressive button instead.

Change 574140 had a related patch set uploaded (by Eric Gardner; owner: Eric Gardner):
[mediawiki/extensions/WikibaseMediaInfo@master] Remove "primary" class from input widget "Add" buttons

https://gerrit.wikimedia.org/r/574140

Just submitted a patch that removes the "primary" class from the "Add" button in the String, Quantity, and GlobeCoordinate input widgets. Here's an example of how it looks just as a "progressive" button, in a QuantityInputWidget:

Interesting, that also uncovers an issue with this widget combination – double border. Will look if we have to tackle this in context or upstream.

Change 574140 merged by Eric Gardner:
[mediawiki/extensions/WikibaseMediaInfo@master] Remove "primary" class from input widget "Add" buttons

https://gerrit.wikimedia.org/r/574140

Change 567125 merged by jenkins-bot:
[mediawiki/extensions/WikibaseMediaInfo@master] Implement support for time datavalue

https://gerrit.wikimedia.org/r/567125