diff options
| author | Toby Zerner <[email protected]> | 2022-02-01 17:40:59 +1100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2022-02-01 08:40:59 +0200 |
| commit | 22bbff0b037de5e4cf9a44273c4383a27b9f274e (patch) | |
| tree | 7094d6ab32f4f360ed9363021d8dc4d00926ad77 /js/src/dropdown.js | |
| parent | 9d44b603d5bc4380eba162d6c1b0b7b763ec607b (diff) | |
| download | bootstrap-22bbff0b037de5e4cf9a44273c4383a27b9f274e.tar.xz bootstrap-22bbff0b037de5e4cf9a44273c4383a27b9f274e.zip | |
Remove incorrect statement about the disabled attribute on <form> (#35713)
> You can disable every form element within a form with the `disabled` attribute on the `<form>`.
I really want to be mistaken, because this would be a very useful feature! But I don't believe it's true. I can't find anything about this on MDN Web Docs, and adding the `disabled` attribute to a `<form>` does nothing on any browser in my testing.
The `disabled` attribute on a `<fieldset>` does disable all descendant form controls – perhaps that's where the mixup has come from.
Diffstat (limited to 'js/src/dropdown.js')
0 files changed, 0 insertions, 0 deletions