2dc6f15eca
The choice regarding which forms should or should not trigger a warning is subjective. I tried to be consistent and not warn about forms that: - run an action, rather than edit data: search, send an email. - delete data: a warning about losing data would be confusing Note that forms on sign-in pages were already ignored (using a selector, rather than an explicit class on the form element). Fixes #3698. |
||
|---|---|---|
| .. | ||
| account_link.tmpl | ||
| applications.tmpl | ||
| avatar.tmpl | ||
| delete.tmpl | ||
| email.tmpl | ||
| keys_gpg.tmpl | ||
| keys_ssh.tmpl | ||
| keys.tmpl | ||
| navbar.tmpl | ||
| openid.tmpl | ||
| organization.tmpl | ||
| profile.tmpl | ||
| repos.tmpl | ||
| security.tmpl | ||
| twofa_enroll.tmpl | ||
| twofa.tmpl | ||