Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #47595, comment 14


Ignore:
Timestamp:
02/05/2023 08:10:22 PM (18 months ago)
Author:
oglekler
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #47595, comment 14

    initial v1  
    1 This error message looks obsolete and needs to be avoided as mush as possible for not to spoil a good impression upon users. Let's make JS validation or remove "novalidate" attribute. Both solutions look not very complicated. If there are some concerns from the accessibility perspective, it's better to ask accessibility team how it can be done better. The third possibility is a hook to get developers an opportunity to decide for themselves, but from my perspective this is unnecessary complication to many developers when this can be solved in the root.
     1This error message looks obsolete and needs to be avoided as much as possible for not to spoil a good impression upon users. Let's make JS validation or remove "novalidate" attribute. Both solutions look not very complicated. If there are some concerns from the accessibility perspective, it's better to ask accessibility team how it can be done better. The third possibility is a hook to get developers an opportunity to decide for themselves, but from my perspective this is unnecessary complication to many developers when this can be solved in the root.