This is related to #1040.
I'm wondering if the UX would be better if instead of this:
- fill form in a rush, but fail to notice the tiny red asterisks in some fields
- click "save"
- page reloads
- see validation errors
- fix errors
- click save again
...we provided a better UI that guided people to this: 1. fill form in a rush, but still fill in required fields because "required" indicators are bigger and made more prominent -> get a "live" feedback/indication that you've done the right thing 2. save -> win! (at least less chances that you've done something "wrong")
Something like this:
Here's another set of screenshots to demonstrate do's and don't's with regards to accessibility:
Recent comments
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database
With JQuery, simple and fast. Or put all possible links in one menu, and hide unnecessary with CSS mediaquery.
Different primary menus depending on the viewport size?
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it. In settings.php or settings.local.php if that's where you put your...
Problem with utf8mb4 Format when importing database