mirror of
https://github.com/twbs/bootstrap.git
synced 2022-11-09 12:25:43 -05:00
Minor Markdown consistency changes.
This commit is contained in:
parent
71c06b75c6
commit
7e6374db92
11 changed files with 11 additions and 7 deletions
|
@ -2,8 +2,7 @@
|
|||
layout: docs
|
||||
title: History
|
||||
description: A brief overview of the history of Bootstrap.
|
||||
redirect_from:
|
||||
- /docs/4.0/about/
|
||||
redirect_from: "/docs/4.0/about/"
|
||||
group: about
|
||||
---
|
||||
|
||||
|
|
|
@ -4,6 +4,7 @@ title: Breadcrumb
|
|||
description: Indicate the current page's location within a navigational hierarchy that automatically adds separators via CSS.
|
||||
group: components
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Separators are automatically added in CSS through [`::before`](https://developer.mozilla.org/en-US/docs/Web/CSS/::before) and [`content`](https://developer.mozilla.org/en-US/docs/Web/CSS/content).
|
||||
|
|
|
@ -25,6 +25,7 @@ In order for assistive technologies (such as screen readers) to convey that a se
|
|||
|
||||
In addition, groups and toolbars should be given an explicit label, as most assistive technologies will otherwise not announce them, despite the presence of the correct role attribute. In the examples provided here, we use `aria-label`, but alternatives such as `aria-labelledby` can also be used.
|
||||
{% endcallout %}
|
||||
|
||||
## Button toolbar
|
||||
|
||||
Combine sets of button groups into button toolbars for more complex components. Use utility classes as needed to space out groups, buttons, and more.
|
||||
|
|
|
@ -151,7 +151,6 @@ $('.popover-dismiss').popover({
|
|||
{% endhighlight %}
|
||||
|
||||
|
||||
|
||||
## Usage
|
||||
|
||||
Enable popovers via JavaScript:
|
||||
|
@ -306,7 +305,6 @@ Toggles an element's popover. **Returns to the caller before the popover has act
|
|||
|
||||
Hides and destroys an element's popover. Popovers that use delegation (which are created using [the `selector` option](#options)) cannot be individually destroyed on descendant trigger elements.
|
||||
|
||||
|
||||
{% highlight js %}$('#element').popover('dispose'){% endhighlight %}
|
||||
|
||||
#### `.popover('enable')`
|
||||
|
|
|
@ -2,8 +2,7 @@
|
|||
layout: simple
|
||||
title: Examples
|
||||
description: Quickly get a project started with any of our examples ranging from using parts of the framework to custom components and layouts.
|
||||
redirect_from:
|
||||
- /examples/
|
||||
redirect_from: "/examples/"
|
||||
---
|
||||
|
||||
[Download the Bootstrap source code]({{ site.download.source }}) to snag these examples.
|
||||
|
|
|
@ -8,6 +8,7 @@ group: extend
|
|||
Bootstrap doesn't include an icon library by default, but we have a handful of recommendations for you to choose from. While most icon sets include multiple file formats, we prefer SVG implementations for their improved accessibility and vector support.
|
||||
|
||||
## Preferred
|
||||
|
||||
We've tested and used these icon sets ourselves.
|
||||
|
||||
- [Iconic](https://useiconic.com/open/)
|
||||
|
@ -15,6 +16,7 @@ We've tested and used these icon sets ourselves.
|
|||
- [Entypo](http://www.entypo.com/)
|
||||
|
||||
## More options
|
||||
|
||||
While we haven't tried these out, they do look promising and provide multiple formats—including SVG.
|
||||
|
||||
- [Bytesize](https://github.com/danklammer/bytesize-icons)
|
||||
|
|
|
@ -3,4 +3,4 @@ layout: docs
|
|||
title: Extend
|
||||
---
|
||||
|
||||
todo: this entire page
|
||||
todo: this entire page
|
||||
|
|
|
@ -12,6 +12,7 @@ We've designed and developed Bootstrap to work in a number of environments. Here
|
|||
{% endcallout %}
|
||||
|
||||
### General outline
|
||||
|
||||
- Working with CSS
|
||||
- Working with Sass files
|
||||
- Building new CSS components
|
||||
|
|
|
@ -125,6 +125,7 @@ The `.dropdown-backdrop` element isn't used on iOS in the nav because of the com
|
|||
Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.
|
||||
|
||||
## Sticky `:hover`/`:focus` on mobile
|
||||
|
||||
Even though real hovering isn't possible on most touchscreens, most mobile browsers emulate hovering support and make `:hover` "sticky". In other words, `:hover` styles start applying after tapping an element and only stop applying after the user taps some other element. On mobile-first sites, this behavior is normally undesirable.
|
||||
|
||||
Bootstrap includes a workaround for this, although it is disabled by default. By setting `$enable-hover-media-query` to `true` when compiling from Sass, Bootstrap will use [mq4-hover-shim](https://github.com/twbs/mq4-hover-shim) to disable `:hover` styles in browsers that emulate hovering, thus preventing sticky `:hover` styles. There are some caveats to this workaround; see the shim's documentation for details.
|
||||
|
|
|
@ -84,6 +84,7 @@ $('#myCarousel').carousel('2') // !! Will be ignored, as the transition to the s
|
|||
{% endhighlight %}
|
||||
|
||||
### Default settings
|
||||
|
||||
You can change the default settings for a plugin by modifying the plugin's `Constructor.Default` object:
|
||||
|
||||
{% highlight js %}
|
||||
|
|
|
@ -7,6 +7,7 @@ toc: true
|
|||
---
|
||||
|
||||
## Beta 2 changes
|
||||
|
||||
While in beta, we aim to have no breaking changes. However, things don't always go as planned. Below are the breaking changes to bear in mind when moving from Beta 1 to Beta 2.
|
||||
|
||||
### Breaking
|
||||
|
|
Loading…
Reference in a new issue