input[time] renders with milliseconds if the browser does not support time input

[chris-rock]

Whenever a browser does not support input[time] natively, angular falls back to text field. It renders nicely in Chrome (e.g. 07:15 AM), but in Firefox it will display 07:15:00.000 instead. There are some quick hacks out there: http://mark.zealey.org/2015/01/08/formatting-time-inputs-nicely-with-angularjs

It would be nice, if we could configure the date format whenever angular switches in fallback mode.

The problem is located in input.js where we set the format to 'HH:mm:ss.sss'

[mightydes]

+1 for this feature

[JeanMeche]

+1

[wilgert]

+1

[simonbuehler]

it would be great if the formatter of the input could be overridden, in one project i need the time(span) to be entered as 'mm:ss.sss' without hours which would be possible with a custom formatter

[ismarslomic]

+1

[heroInCommunity]

+1

[bsandrow]

Update to input.js link in the original bug report.

[SamMorrowDrums]

This isn't really a feature request, this is a regularly occurring bug. The fallback behaviour should surely mimic the behaviour of the standard HTML 5 time input, adding milliseconds doesn't really seem like a useful fallback, it's got to be the niche case!

[Nickproger]

+1

[hubo1016]

AngularJS should respect HTML5 "step" attributes on the input element. According to HTML5 standard, when step is set to "60", value of the input should only contains minutes "11:23", while when step is set to "1" or some number less than 60, value should contains seconds e.g. "11:23:34"

[Narretz]

@hubo1016 This is a different issue. You can open a new issue as a separate feature request.

[pgnjidic]

The problem can be solved by the directive on this link:

https://markandruth.co.uk/2015/01/08/formatting-time-inputs-nicely-with-angularjs

[waqasilyas]

Worked with v1.0.3 it seems... http://jsfiddle.net/yk29zeLz/1/

[roxolan]

+1 for this feature

[petebacondarwin]

Note that this issue has had the PRs plz label for almost a year. It is probably not that hard to fix. Does someone in the community - perhaps someone affected by the problem? - want to step up and provide a PR?