3 ms·

it’s particularly aggravating that form fields have been largely stagnant over the past 20 years. so much repetitive development happens around forms (validatio

it’s particularly aggravating that form fields have been largely stagnant over the past 20 years. so much repetitive development happens around forms (validations or date/time pickers, for instance) and yet very little effort goes into improving them.

digianarchist 6y ago
Microsoft are actually doing good in this space. https://blogs.windows.com/msedgedev/2019/10/15/form-controls-microsoft-edge-chromium/ https://blogs.windows.com/msedgedev/2019/10/15/form-controls...
rablackburn 6y ago
I’ve noticed this too. I’ve found myself iterating on a nice extended form control library where I try to extend the native inputs and forms in the most minimal, yet complete, way I can. There are actually a lot of nice improvements being discussed in the CSS level 4 specs, but some of the issues are last tagged as updated in 2012... But basically we just need a consistent value interface (two-way data binding), and a more finely-grained validation/state lifecycle where we can plug in our own custom validation functions. Colleagues and I always joke that every web developer gets the idea to write a form library at some point, and suffering through trying to implement it is the only way to dissuade them of the idea. Now the joke is on me as I’ve come full circle back to writing one. I’ve spent so much time on it now I’ve been considering reaching out to help contribute to the spec. But I have no idea how receptive the working group is. This may just become my eternal project, there’s always more edge cases to find.
samus 6y ago
Every effort to change or improve them will wreck most forms on the internet. Most websites heavily style them and augment them with scripts, which will almost certainly conflict with whatever is change in the browsers. This ship has sailed decades ago.

3 ms·

it’s particularly aggravating that form fields have been largely stagnant over the past 20 years. so much repetitive development happens around forms (validatio

by clairity 6y ago

digianarchist 6y ago
Microsoft are actually doing good in this space. https://blogs.windows.com/msedgedev/2019/10/15/form-controls-microsoft-edge-chromium/ https://blogs.windows.com/msedgedev/2019/10/15/form-controls...
rablackburn 6y ago
I’ve noticed this too. I’ve found myself iterating on a nice extended form control library where I try to extend the native inputs and forms in the most minimal, yet complete, way I can. There are actually a lot of nice improvements being discussed in the CSS level 4 specs, but some of the issues are last tagged as updated in 2012... But basically we just need a consistent value interface (two-way data binding), and a more finely-grained validation/state lifecycle where we can plug in our own custom validation functions. Colleagues and I always joke that every web developer gets the idea to write a form library at some point, and suffering through trying to implement it is the only way to dissuade them of the idea. Now the joke is on me as I’ve come full circle back to writing one. I’ve spent so much time on it now I’ve been considering reaching out to help contribute to the spec. But I have no idea how receptive the working group is. This may just become my eternal project, there’s always more edge cases to find.
samus 6y ago
Every effort to change or improve them will wreck most forms on the internet. Most websites heavily style them and augment them with scripts, which will almost certainly conflict with whatever is change in the browsers. This ship has sailed decades ago.