- 14 May, 2017 4 commits
- 09 May, 2017 1 commit
-
-
Peter Blazejewicz authored
-
- 08 May, 2017 1 commit
-
-
Sebastiaan Nijland authored
-
- 05 May, 2017 3 commits
-
-
Patrick H. Lauke authored
For compatibility in IE10/IE11 which don't otherwise "know" this element's role/don't expose it to AT
-
Laussel Loïc authored
includes explicit `role="main"` for IE10/IE11 compatibility
-
Patrick H. Lauke authored
For IE10 (and any older browsers) support , so at least the layout doesn't fall apart if author is using them.
-
- 04 May, 2017 1 commit
-
-
Patrick H. Lauke authored
* Split out/expand mention that base navs lack active styles * Add accessibility notes for navigation bars vs dynamic tabbed interfaces
-
- 02 May, 2017 1 commit
-
-
Johann-S authored
-
- 01 May, 2017 1 commit
-
-
Peter Gerdes authored
The link to package.json in the v4 docs was linking to package.json in the v3 source. Fixed to point to the correct v4 location. A change like this will need to be made for all branches on version 4 if you want the docs to be linked correctly (github may be smart enough to follow the link to the current branch if you are on github but it was wrong from the main site).
-
- 29 Apr, 2017 3 commits
- 28 Apr, 2017 1 commit
-
-
Joyce Babu authored
Should remove `data` not `class` on dispose
-
- 27 Apr, 2017 3 commits
-
-
Patrick H. Lauke authored
* Fix incorrect code indentation * Remove unnecessary vendor prefix for `box-sizing` - all modern browsers now support this unprefixed * Remove incorrect `<label>` and change static controls to readonly inputs * Allow `<img>` elements without `src` to allow for `holder.js` images used in the docs, which lack `src` and use `data-src` instead
-
Johann-S authored
-
Johann-S authored
-
- 26 Apr, 2017 1 commit
-
-
Anna authored
-
- 25 Apr, 2017 1 commit
-
-
Pierre Vanduynslager authored
-
- 22 Apr, 2017 2 commits
-
-
Mark Otto authored
-
Zach Leatherman authored
-
- 21 Apr, 2017 1 commit
-
-
Bardi Harborow authored
-
- 20 Apr, 2017 4 commits
-
-
Patrick H. Lauke authored
(with apologies, this slipped through due to build system problems on my end)
-
Patrick H. Lauke authored
Tweak to https://github.com/twbs/bootstrap/pull/22426, where the wrong selector slipped through the net (selecting all of `<body>`s grand-children rather than children)
-
Patrick H. Lauke authored
Same hack as in https://github.com/twbs/bootstrap/pull/22426 (modulo the selector, which is wrong in that PR and will be updated in a separate PR) to get tooltips to work correctly on iOS. Dynamically adds/removes empty (`noop`) `touchstart` event handlers to all children of `<body>` in order to coax iOS into proper event delegation/bubbling
-
Bardi Harborow authored
-
- 19 Apr, 2017 2 commits
-
-
Johann-S authored -
Jesse Mandel authored
a bower search
-
- 18 Apr, 2017 3 commits
-
-
Patrick H. Lauke authored
-
Johann-S authored
-
Patrick H. Lauke authored
As the question often comes up about why Bootstrap does not do "true" ARIA menus (with their `role="menu"` etc), add an admittedly lengthy note (tl;dr because BS is generic, and ARIA menus are specific and quite limiting). Additionally, fixes up the `<a>` example for dropdown trigger, with the missing `role="button"` and neutering the `href` (which would be useless anyway since BS overrides the link-like nature of the `<a>` so it could never be triggered/followed anyway)
-
- 17 Apr, 2017 1 commit
-
-
Patrick H. Lauke authored
* Add carousel mouse listeners even if touch events enabled - touch events are enabled not just on "mobile", just also on touch-enabled desktop/laptop devices; additionally, it's possible to pair a mouse with traditionally touch-only devices (e.g. Android phones/tablets); currently, in these situations the carousel WON'T pause even when using a mouse * Restart cycle after touchend as `mouseenter` is fired as part of the touch compatibility events, the previous change results in carousels which cycle until the user tapped/interacted with them. after that they stop cycling (as `mouseleave` is not sent to the carousel after user scrolled/tapped away). this fix resets the cycling after `touchend` - essentially returning to the previous behavior, where on touch the carousel essentially never pauses, but now with the previous fix it at least pauses correctly for mouse users on touch-enabled devices. includes documentation for this new ...
-
- 16 Apr, 2017 5 commits
-
-
Patrick H. Lauke authored
A long overdue rewrite of the accessibility section - instead of the few snippets of strangely superficial and out-of-context advice (skip links, use correct heading levels), this tries to answer some of the fundamental questions about "is Bootstrap accessible", with emphasis on the fact that the final result will depend in large part on what BS is applied to/on (since BS relies on the markup etc authored by developers). This also sets out our ambition to have things work for keyboard and assistive tech users, and that we strive to make all our examples etc accessible and semantic. * Changes based on @mdo's feedback
-
Patrick Yeo authored
* Rename variable $input-border-focus to $input-border-color-focus * Rename variables $pagination-hover-border, $pagination-active-border, $pagination-disabled-border to $pagination-hover-border-color, $pagination-active-border-color, $pagination-disabled-border-color, respectively * Rename variables $state-*-border to $state-*-border-color, respectively * Rename variables $alert-*-border to $alert-*-border-color * Rename $list-group-active-border to $list-group-active-border-color * Rename $table-inverse-border to $table-inverse-border-color * Rename $btn-*-border to $btn-*-border-color * Rename $navbar-*-toggler-border to $navbar-*-toggler-border-color
-
Mark Otto authored
-
Patrick H. Lauke authored
This makes them keyboard-accessible. For mouse users, the only change here is that the focus outline will remain on the button once clicked (in future, this can be solved with :focus-ring, but for now this would require a polyfill). the tooltip is explicitly hidden on `mouseleave`, so even though the `<button>` retains focus after clicking, the tooltip won't stay visible once mouse user moves away. the mouse hover styles have explicitly not been make to also apply to :focus, so as to minimise the visual impact for mouse users (though the tooltip remains visible) - but due to the default outline and the custom tooltip, it should be fairly clear when keyboard users set focus to a copy button too.
-
Mark Otto authored
-
- 14 Apr, 2017 1 commit
-
-
Patrick H. Lauke authored
* Replace backdrop with simple noop mouse listener As discussed in https://github.com/twbs/bootstrap/pull/22422 the current approach of injecting a backdrop (to work around iOS' broken event delegation for the `click` event) has annoying consequences on touch-enabled laptop/desktop devices. Instead of a backdrop `<div>`, here we simply add extra empty/noop mouse listeners to the immediate children of `<body>` (and remove them when the dropdown is closed) in order to force iOS to properly bubble a `click` resulting from a tap (essentially, method 2 from https://www.quirksmode.org/blog/archives/2014/02/mouse_event_bub.html) This is sufficient (except in rare cases where the user does manage to tap on the body itself, rather than any child elements of body - which is not very likely in an iOS phone/tablet scenario for most layouts) to get iOS to get a grip and do the correct event bubbling/delegation, meaning the regular "click" event w...
-
