This commit is contained in:
2020-11-28 00:24:27 +00:00
parent becb883eec
commit 8d1d881662
6 changed files with 341 additions and 322 deletions

View File

@@ -35,9 +35,27 @@ To REMOVE: apt-get remove dotnet-runtime-3.0 (replace 3.0 with whatever version
MISC ITEMS THAT CAME UP
todo: bugbug datetime control clear buttons don't trigger emit of empty date times
todo: DATE / TIME / DATE_TIME controls switch back to vuetify ones
Ensure can clear completely to null value
Test it out thoroughly there was a reason I quit using it the first time
i18n
smoke test (maybe some way to bypass the control for test purposes)
Is it possible to still keep the native ones in there somehow with a v-if template and a setting?
maybe get the nonnative one working then look into supporting this for edge cases or future proofing
Lots of warnings about using native ones on the MDN site, looks like I should use a component of some kind
so if I do I might as well use the vuetify ones since there are no substantially greater options out there
It would be very nice though if I could opt to have the user be able to choose alternatives like a native input for when
browser makers actually get around to implementing them properly, some have and some are good but some like apple just don't work
bugbug datetime control clear buttons don't trigger emit of empty date times
contractexpires on customer form clearing it and saving sends date to server as if it wasn't cleared at all
Better solution: one clear button that clears all and emits properly and disable the built in if possible
todo: gz-data-table make sure unbounded notes column is bounded by some length restriction
mobile format is ok, it cuts off at one line, but for desktop we should have a sane limit as right now it's completely unbounded
this should apply to any column that displays text but particularly just the plain text ones