Feature #88817
closed
- Private changed from Yes to No
- Related to Bug #91435: The 'form' Honeypot partial inserts invalid HTML added
- Sprint Focus set to Remote Sprint
- Status changed from New to Under Review
- Status changed from Under Review to Rejected
- Priority changed from Should have to Won't have this time
The discussion with Elias revealed some insights:
- A text input field will not help the average editor.
- Providing a drop down with all the entries is hard to maintain.
- Providing a drop down with all the entries is difficult to understand by the average editor.
- Providing a drop down with all the entries is hard to transport. We would need quite some documentation. There are tons of options which are very difficult to explain (see https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete).
Therefore, we are rejecting this issue. It is still possible to provide such a field with the help of your own extension etc.
I would like to reopen this ticket as a result of the accessibility code-sprint in June 2023 in Berlin.
The idea is that we supply the most common autocomplete purposes, expecially those needed for contact forms, by default in the forms extension. In case different purposes are needed these can then be supplied via YAML configuration by an extension or sitepackage
- Status changed from Rejected to Accepted
- Priority changed from Won't have this time to Should have
Lina wants to work on this and provide a subset of useful attributes.
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by