Timeline for How to disable all div content
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14, 2023 at 19:34 | comment | added | LOST | Sadly this does not disable hyperlinks | |
| May 17, 2022 at 13:45 | comment | added | Henrik Erlandsson | Perfect! 654321 | |
| Aug 6, 2021 at 18:58 | comment | added | Matt Lo | best answer here ✅ | |
| Nov 17, 2020 at 11:31 | comment | added | Aleksei | I'd like to add more upvotes if I could. This is exactly what I needed! | |
| Apr 13, 2020 at 4:23 | comment | added | Saghachi | Great one, always the best solutions are the simplest one thanks. | |
| Nov 17, 2018 at 21:46 | comment | added | Stephen Watkins | This is the best answer. It's the most semantically correct, telling the browser that all inputs within this fieldset should be disabled. It honors the keyboard and doesn't need mouse handling JS unregistration. One note, though, as of the time of this comment, Edge won't inherit the disabled attribute value from parent fieldsets inside of another fieldset. | |
| Jan 12, 2017 at 8:42 | comment | added | salmonmoose | This is a great answer - it allows dynamic items to be spawned in a disabled state so long as they're within the block element rather than testing the disabled state on creation - and elements are truly disabled. | |
| Nov 25, 2016 at 8:32 | review | Late answers | |||
| Nov 25, 2016 at 8:33 | |||||
| Nov 25, 2016 at 8:15 | history | answered | Ortho | CC BY-SA 3.0 |