From 25ef6ad625d02ef8832edabeee1319ffde4537cf Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Sat, 15 Nov 2014 00:25:13 +0000 Subject: [PATCH] Move context-specific callout to general tag usage --- docs/_includes/css/buttons.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/_includes/css/buttons.html b/docs/_includes/css/buttons.html index db404dc69b..2fad8b0d41 100644 --- a/docs/_includes/css/buttons.html +++ b/docs/_includes/css/buttons.html @@ -154,11 +154,6 @@

Link functionality caveat

This class uses pointer-events: none to try to disable the link functionality of <a>s, but that CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11. In addition, even in browsers that do support pointer-events: none, keyboard navigation remains unaffected, meaning that sighted keyboard users and users of assistive technologies will still be able to activate these links. So to be safe, use custom JavaScript to disable such links.

-
-

Context-specific usage

-

While button classes can be used on <a> and <button> elements, only <button> elements are supported within our nav and navbar components.

-
-

Button tags

Use the button classes on an <a>, <button>, or <input> element.

@@ -175,6 +170,11 @@ {% endhighlight %} +
+

Context-specific usage

+

While button classes can be used on <a> and <button> elements, only <button> elements are supported within our nav and navbar components.

+
+

Links acting as buttons

If the <a> elements are used to act as buttons – triggering in-page functionality, rather than navigating to another document or section within the current page – they should also be given an appropriate role="button".