rob pikeOne of the unremarked indignities of getting older is how long it takes to scroll back from today when using those odometer scrolly things in supposedly well-designed apps that need to know your date of birth.
Jack Rusher@robpike My favorite is when the scrolly thing starts at the current year, as if the median user were literally born yesterday
xyhhx π»
the roamerYeah, so true.
(And, "unremarked indignities of getting older" is a great heading.)
Cassandrich@robpike Any type of control but a textbox for numeric input is inexcusably bad UX.
Any good browser or UI toolkit should disallow them and silently replace them with textboxes.
Tim Ward βπͺπΊπΆ #FBPE@TimWardCam @robpike If so that's just sad and stupid. I always assumed they were something mindless UI devs believed they were supposed to use anywhere there was a "finite set of choices" and they didn't want to validate input..
@TimWardCam @robpike You need server side validation regardless. Client side is just a convenience for the user.
Scissors Cut Paper...You can totally check fields and turn their input boxen red for invalid data.
kolya@dalias @robpike
all modern browsers support a standard date picker with fine UX: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date
the problem are webdevs who only know their Javascript framework and have little idea about HTML/CSS and therefore needlessly build their own pretty but shitty datepickers
all modern browsers support a standard date picker with fine UX: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date
the problem are webdevs who only know their Javascript framework and have little idea about HTML/CSS and therefore needlessly build their own pretty but shitty datepickers
Daniel Terhorst-North@robpike youβre right, it should totally be a readonly number field with tiny up-down arrows.
Henrik Jernevad
coldclimate@robpike a most hateful user experience
Kees π§@robpike I always take the last option...
Tom Walker@robpike The sad thing is that we (the big web development we) have been subjecting older users to this for years but only just got old enough to notice it
γγ£γΌγΈγ§γΌγ°γ¬γ§/me is grateful not to be part of that "we" despite definitely being part of the big [web] development 'we' because he doesn't collect PII, because the best way to not risk users' data to unscrupulous 3rd parties, is to never ask for it in the first place.
CC: @[email protected]
CC: @[email protected]
Ronan@robpike and it gets worse every year
J. Peterson@robpike Similar to how the US is buried near Uganda and Uzbekistan in some "choose your country" lists.
Bracken@robpike every UI date picker is terrible.
My attempt is particularly bad: https://bracken.cc/webcal-proxy
Mike Gerdts@robpike once this is solved, please move all of the devs that write the state pickers from California to Wisconsin. It would be ok if some of them went to Wyoming or Washington.
Lockpick Extreme@robpike like spinning the giant price wheel on the price is right
noplasticshower@robpike irony: dying of old age while attempting to scroll all the way down to your birth year
MarkD@robpike Makes you feel sorry for all the Zimbabweans born on the 31st of December.
Bill Bennett@robpike Gives me Occupational Overuse Syndrome.
Isaac Freeman@robpike Seems like it would be a social good to have the scroller start at 125 and go down. Young people have more life left to waste, so it's fair that they scroll further than old people.
Also horrible for US states. Especially those farther down in the alphabet. When my work address was in Washington, it was much, much faster to type WA than do a dropdown or prizewheel.