Timeline for How to add a boolen attribute to a form?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 16, 2023 at 8:22 | comment | added | Inan |
Your browsers' dev consoles usually render it as <form novalidate=""> , but it is in fact still <form novalidate> . You can use the ancient method of viewing the source ("View Page Source" in Firefox and Google Chrome) to see the actual HTML markup.
|
|
Mar 1, 2022 at 20:44 | comment | added | Jaypan | Well, if someone comes along with that other answer, then it too can be an answer to the question. Both will be valid answers. | |
Mar 1, 2022 at 20:39 | answer | added | Clive♦ | timeline score: 4 | |
Mar 1, 2022 at 20:36 | comment | added | Clive♦ |
I was in two minds @Jaypan, maybe the "proper" answer to this is one which allows Twig/Drupal to output the bare novalidate , even though it doesn't technically matter? Probably over-thinking it, I'll add an answer
|
|
Mar 1, 2022 at 20:21 | comment | added | Jaypan | You should put that as an answer Clive - it's the correct answer to the question. | |
Mar 1, 2022 at 20:02 | comment | added | Clive♦ |
novalidate="" is fine for the HTML spec - boolean attributes can have a value as long as it's an empty string or the same (case-insensitive) string as the attribute name. So novalidate="novalidate" would also be fine. If you follow those rules, the attribute's existence is taken to mean true regardless of the value. See developer.mozilla.org/en-US/docs/Web/HTML/…
|
|
Mar 1, 2022 at 19:45 | history | asked | liquidcms | CC BY-SA 4.0 |