3 ms·

What kinds of forms do you have in mind? Another ask of mine would be standard page formats, such that there could be standard styles which could be consistent

What kinds of forms do you have in mind? Another ask of mine would be standard page formats, such that there could be standard styles which could be consistently applied to them. Article, index, search, gallery, discussion/thread, off the top of my head.

econ 4mo ago
Stop everyone from reinventing the registration form so that it can be filled out without all the fuzzy business. You specify the fields you need and where it should post. Then have no further control over it. Have the browser bar show it is a standard form for site: example.com which means no [3rd party] js listening in on personal information. Validate and format all countries adresses correctly. Get email addresses and names right https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... If you let me (or random Joe) design it it will no doubt be wrong in multiple ways. It will probably zoom annoyingly on iphones, I will ask for the state name outside the us and I should really ask for your mum's birthday and maiden name. I will disable right click, mess up tab index and ruin accessibility with a gray on gray font. Should I wrap table rows in labels? Why should everyone have to implement this if 100 million people already tried and mostly got it wrong?
- dredmorbius 4mo ago
  Now the hard part: Which fields are allowed? Which aren't?
  - econ 4mo ago
    It's not so hard but does require some debate and research. Only the sensitive info needs to be contained. For [say] a webshop you have at least the name, address info, email and phone number. Perhaps payment info or coupon codes could be included. Gradually make it more sophisticated. It's just an example. The point is for stuff used often enough to find its way into html and improve. The time date picker was a fun idea but needs work. Search suggestions was a good idea but the implementation is still horrific. Basic table sort doesn't seem very exotic but you could add many data types. Everyone is using toggles rather than checkboxes. I know how to doctor this with css and labels but its an ugly hack. https://www.w3schools.com/howto/howto_css_switch.asp https://www.w3schools.com/howto/howto_css_switch.asp
    - dredmorbius 4mo ago
      Thanks. Coming up with a standard form is of course the hard part, but the basics you suggest are probably in there. There is of course all the bit about falsehoods programmers believe about names, addresses, emails, and the rest: <https://ctemm.me/falsehoods/ https://ctemm.me/falsehoods/> <https://hn.algolia.com/?q=falsehoods%20programmers%20believe%20about https://hn.algolia.com/?q=falsehoods%20programmers%20believe...>

econ 4mo ago

Stop everyone from reinventing the registration form so that it can be filled out without all the fuzzy business. You specify the fields you need and where it should post. Then have no further control over it. Have the browser bar show it is a standard form for site: example.com which means no [3rd party] js listening in on personal information. Validate and format all countries adresses correctly. Get email addresses and names right https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... If you let me (or random Joe) design it it will no doubt be wrong in multiple ways. It will probably zoom annoyingly on iphones, I will ask for the state name outside the us and I should really ask for your mum's birthday and maiden name. I will disable right click, mess up tab index and ruin accessibility with a gray on gray font. Should I wrap table rows in labels? Why should everyone have to implement this if 100 million people already tried and mostly got it wrong?

dredmorbius 4mo ago
Now the hard part: Which fields are allowed? Which aren't?
- econ 4mo ago
  It's not so hard but does require some debate and research. Only the sensitive info needs to be contained. For [say] a webshop you have at least the name, address info, email and phone number. Perhaps payment info or coupon codes could be included. Gradually make it more sophisticated. It's just an example. The point is for stuff used often enough to find its way into html and improve. The time date picker was a fun idea but needs work. Search suggestions was a good idea but the implementation is still horrific. Basic table sort doesn't seem very exotic but you could add many data types. Everyone is using toggles rather than checkboxes. I know how to doctor this with css and labels but its an ugly hack. https://www.w3schools.com/howto/howto_css_switch.asp https://www.w3schools.com/howto/howto_css_switch.asp
  - dredmorbius 4mo ago
    Thanks. Coming up with a standard form is of course the hard part, but the basics you suggest are probably in there. There is of course all the bit about falsehoods programmers believe about names, addresses, emails, and the rest: <https://ctemm.me/falsehoods/ https://ctemm.me/falsehoods/> <https://hn.algolia.com/?q=falsehoods%20programmers%20believe%20about https://hn.algolia.com/?q=falsehoods%20programmers%20believe...>