js
src
tab.js +82 -22
tests
unit
tab.js +234 -52
visual
tab.html +13 -88
site/content/docs/4.3/components
list-group.md +4 -4
navs.md +24 -22
+ 82
- 22
@@ -29,17 +29,22 @@ const VERSION = '4.3.1'
@@ -47,15 +52,16 @@ const ClassName = {
@@ -97,6 +103,7 @@ class Tab {
@@ -129,6 +136,7 @@ class Tab {
@@ -175,20 +183,16 @@ class Tab {
@@ -197,17 +201,6 @@ class Tab {
@@ -229,6 +222,48 @@ class Tab {
@@ -240,6 +275,31 @@ class Tab {
+ 234
- 52
@@ -180,35 +180,6 @@ $(function () {
@@ -265,6 +236,30 @@ $(function () {
@@ -291,9 +286,9 @@ $(function () {
@@ -327,26 +322,6 @@ $(function () {
@@ -523,6 +498,213 @@ $(function () {
+ 13
- 88
Files with large changes are collapsed by default.
@@ -205,7 +205,7 @@ Use the tab JavaScript plugin—include it individually or through the compiled
@@ -234,7 +234,7 @@ Use the tab JavaScript plugin—include it individually or through the compiled
@@ -259,7 +259,7 @@ You can activate a list group navigation without writing any JavaScript by simpl
@@ -316,7 +316,7 @@ To make tabs panel fade in, add `.fade` to each `.tab-pane`. The first tab pane
+ 24
- 22
@@ -307,17 +307,19 @@ Use the tab JavaScript plugin—include it individually or through the compiled
Dynamic tabbed interfaces, as described in the [<abbr title="Web Accessibility Initiative">WAI</abbr> <abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices](https://www.w3.org/TR/wai-aria-practices/#tabpanel), require `role="tablist"`, `role="tab"`, `role="tabpanel"`, and additional `aria-` attributes in order to convey their structure, functionality and current state to users of assistive technologies (such as screen readers).
Note that dynamic tabbed interfaces should <em>not</em> contain dropdown menus, as this causes both usability and accessibility issues. From a usability perspective, the fact that the currently displayed tab's trigger element is not immediately visible (as it's inside the closed dropdown menu) can cause confusion. From an accessibility point of view, there is currently no sensible way to map this sort of construct to a standard WAI ARIA pattern, meaning that it cannot be easily made understandable to users of assistive technologies.
Dynamic tabbed interfaces <em>can't</em> contain dropdown menus, as this causes both usability and accessibility issues. From a usability perspective, the fact that the currently displayed tab's trigger element is not immediately visible (as it's inside the closed dropdown menu) can cause confusion. From an accessibility point of view, there is currently no sensible way to map this sort of construct to a standard WAI ARIA pattern, meaning that it cannot be easily made understandable to users of assistive technologies.
@@ -336,13 +338,13 @@ Note that dynamic tabbed interfaces should <em>not</em> contain dropdown menus,
@@ -395,13 +397,13 @@ The tabs plugin also works with pills.
@@ -420,13 +422,13 @@ The tabs plugin also works with pills.
@@ -437,7 +439,7 @@ The tabs plugin also works with pills.
@@ -496,16 +498,16 @@ You can activate a tab or pill navigation without writing any JavaScript by simp
@@ -564,16 +566,16 @@ Activates a tab element and content container. Tab should have either a `data-ta