mirror of
https://github.com/twbs/bootstrap.git
synced 2024-12-10 22:24:19 +01:00
4c7a3e8adf
* WIP: Mention variables, mixins, and loops in docs * Add Sass sections to component pages * add sass docs for forms and content * Update buttons.md * Remove empty mixins sections * Massive update to utilities and some consistency changes Co-authored-by: XhmikosR <xhmikosr@gmail.com>
40 lines
2.1 KiB
Markdown
40 lines
2.1 KiB
Markdown
---
|
|
layout: docs
|
|
title: Interactions
|
|
description: Utility classes that change how users interact with contents of a website.
|
|
group: utilities
|
|
toc: false
|
|
---
|
|
|
|
## Text selection
|
|
|
|
Change the way in which the content is selected when the user interacts with it.
|
|
|
|
{{< example >}}
|
|
<p class="user-select-all">This paragraph will be entirely selected when clicked by the user.</p>
|
|
<p class="user-select-auto">This paragraph has default select behavior.</p>
|
|
<p class="user-select-none">This paragraph will not be selectable when clicked by the user.</p>
|
|
{{< /example >}}
|
|
|
|
## Pointer events
|
|
|
|
Bootstrap provides `.pe-none` and `.pe-auto` classes to prevent or add element interactions.
|
|
|
|
{{< example >}}
|
|
<p><a href="#" class="pe-none" tabindex="-1" aria-disabled="true">This link</a> can not be clicked.</p>
|
|
<p><a href="#" class="pe-auto">This link</a> can be clicked (this is default behavior).</p>
|
|
<p class="pe-none"><a href="#" tabindex="-1" aria-disabled="true">This link</a> can not be clicked because the <code>pointer-events</code> property is inherited from its parent. However, <a href="#" class="pe-auto">this link</a> has a <code>pe-auto</code> class and can be clicked.</p>
|
|
{{< /example >}}
|
|
|
|
{{< callout warning >}}
|
|
The `.pe-none` class (and the `pointer-events` CSS property it sets) only prevents interactions with a pointer (mouse, stylus, touch). Links and controls with `.pe-none` are, by default, still focusable and actionable for keyboard users. To ensure that they are completely neutralized even for keyboard users, you may need to add further attributes such as `tabindex="-1"` (to prevent them from receiving keyboard focus) and `aria-disabled="true"` (to convey the fact they are effectively disabled to assistive technologies), and possibly use JavaScript to completely prevent them from being actionable. For form controls, consider using the `disabled` HTML attribute instead.
|
|
{{< /callout >}}
|
|
|
|
## Sass
|
|
|
|
### Utilities API
|
|
|
|
Interaction utilities are declared in our utilities API in `scss/_utilities.scss`. [Learn how to use the utilities API.]({{< docsref "/utilities/api#using-the-api" >}})
|
|
|
|
{{< scss-docs name="utils-interaction" file="scss/_utilities.scss" >}}
|