From 27d9d35ffd2ec9787374247b373d0cf96cdad3e8 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 14 Nov 2014 01:15:54 +0000 Subject: [PATCH] Expand caveat for disabled fieldsets and links --- docs/_includes/css/forms.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_includes/css/forms.html b/docs/_includes/css/forms.html index 5df36e2820..c558de96a8 100644 --- a/docs/_includes/css/forms.html +++ b/docs/_includes/css/forms.html @@ -495,7 +495,7 @@

Caveat about link functionality of <a>

-

Our styles use pointer-events: none to try to disable the link functionality of <a class="btn btn-*"> buttons in this case, but that CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11. So to be safe, use custom JavaScript to disable such links.

+

By default, browsers will treat all native form controls (<input>, <select> and <button> elements) inside a <fieldset disabled> as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes <a ... class="btn btn-*"> elements, these will only be given a style of pointer-events: none. As noted in the section about disabled state for buttons (and specifically in the sub-section for anchor elements), this CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11, and won't prevent keyboard users from being able to focus or activate these links. So to be safe, use custom JavaScript to disable such links.