206 lines
9.5 KiB
Markdown
Executable File
206 lines
9.5 KiB
Markdown
Executable File
<h1 align="center">Popper.js</h1>
|
|
|
|
<p align="center">
|
|
<strong>A library used to position poppers in web applications.</strong>
|
|
</p>
|
|
|
|
<p align="center">
|
|
<a href="https://travis-ci.org/FezVrasta/popper.js/branches" target="_blank"><img src="https://travis-ci.org/FezVrasta/popper.js.svg?branch=master" alt="Build Status"/></a>
|
|
<img src="http://img.badgesize.io/https://unpkg.com/popper.js/dist/popper.min.js?compression=gzip" alt="Stable Release Size"/>
|
|
<a href="https://www.bithound.io/github/FezVrasta/popper.js"><img src="https://www.bithound.io/github/FezVrasta/popper.js/badges/score.svg" alt="bitHound Overall Score"></a>
|
|
<a href="https://codeclimate.com/github/FezVrasta/popper.js/coverage"><img src="https://codeclimate.com/github/FezVrasta/popper.js/badges/coverage.svg" alt="Istanbul Code Coverage"/></a>
|
|
<a href="https://gitter.im/FezVrasta/popper.js" target="_blank"><img src="https://img.shields.io/gitter/room/nwjs/nw.js.svg" alt="Get support or discuss"/></a>
|
|
<br />
|
|
<a href="https://saucelabs.com/u/popperjs" target="_blank"><img src="https://badges.herokuapp.com/browsers?labels=none&googlechrome=latest&firefox=latestµsoftedge=latest&iexplore=11,10&safari=latest&iphone=latest" alt="SauceLabs Reports"/></a>
|
|
</p>
|
|
|
|
<img src="https://raw.githubusercontent.com/FezVrasta/popper.js/master/popperjs.png" align="right" width=250 />
|
|
|
|
|
|
## Wut? Poppers?
|
|
|
|
A popper is an element on the screen which "pops out" from the natural flow of your application.
|
|
Common examples of poppers are tooltips, popovers and drop-downs.
|
|
|
|
|
|
## So, yet another tooltip library?
|
|
|
|
Well, basically, **no**.
|
|
Popper.js is a **positioning engine**, its purpose is to calculate the position of an element
|
|
to make it possible to position it near a given reference element.
|
|
|
|
The engine is completely modular and most of its features are implemented as **modifiers**
|
|
(similar to middlewares or plugins).
|
|
The whole code base is written in ES2015 and its features are automatically tested on real browsers thank to [SauceLabs](https://saucelabs.com/) and [TravisCI](https://travis-ci.org/).
|
|
|
|
Popper.js has zero dependencies. No jQuery, no LoDash, nothing.
|
|
It's used by big companies like [Twitter in Bootstrap v4](https://getbootstrap.com/), [Microsoft in WebClipper](https://github.com/OneNoteDev/WebClipper) and [Atlassian in AtlasKit](https://aui-cdn.atlassian.com/atlaskit/registry/).
|
|
|
|
### Popper.js
|
|
|
|
This is the engine, the library that computes and, optionally, applies the styles to
|
|
the poppers.
|
|
|
|
Some of the key points are:
|
|
|
|
- Position elements keeping them in their original DOM context (doesn't mess with your DOM!);
|
|
- Allows to export the computed informations to integrate with React and other view libraries;
|
|
- Supports Shadow DOM elements;
|
|
- Completely customizable thanks to the modifiers based structure;
|
|
|
|
Visit our [project page](https://fezvrasta.github.io/popper.js) to see a lot of examples of what you can do with Popper.js!
|
|
|
|
Find [the documentation here](docs/_includes/popper-documentation.md).
|
|
|
|
|
|
### Tooltip.js
|
|
|
|
Since lots of users just need a simple way to integrate powerful tooltips in their projects,
|
|
we created **Tooltip.js**.
|
|
It's a small library that makes it easy to automatically create tooltips using as engine Popper.js.
|
|
Its API is almost identical to the famous tooltip system of Bootstrap, in this way it will be
|
|
easy to integrate it in your projects.
|
|
The tooltips generated by Tooltip.js are accessible thanks to the `aria` tags.
|
|
|
|
Find [the documentation here](docs/_includes/tooltip-documentation.md).
|
|
|
|
|
|
## Installation
|
|
Popper.js is available on the following package managers and CDNs:
|
|
|
|
| Source | |
|
|
|:-------|:---------------------------------------------------------------------------------|
|
|
| npm | `npm install popper.js --save` |
|
|
| yarn | `yarn add popper.js` |
|
|
| NuGet | `PM> Install-Package popper.js` |
|
|
| Bower* | `bower install popper.js=https://unpkg.com/popper.js --save` |
|
|
| unpkg | [`https://unpkg.com/popper.js`](https://unpkg.com/popper.js) |
|
|
| cdnjs | [`https://cdnjs.com/libraries/popper.js`](https://cdnjs.com/libraries/popper.js) |
|
|
|
|
Tooltip.js as well:
|
|
|
|
| Source | |
|
|
|:-------|:---------------------------------------------------------------------------------|
|
|
| npm | `npm install tooltip.js --save` |
|
|
| yarn | `yarn add tooltip.js` |
|
|
| Bower* | `bower install tooltip.js=https://unpkg.com/tooltip.js --save` |
|
|
| unpkg | [`https://unpkg.com/tooltip.js`](https://unpkg.com/tooltip.js) |
|
|
| cdnjs | [`https://cdnjs.com/libraries/popper.js`](https://cdnjs.com/libraries/popper.js) |
|
|
|
|
\*: Bower isn't officially supported, it can be used to install both libraries only trough the unpkg.com CDN. This method has the limitation of not being able to define a specific version of the library. Bower and Popper.js suggests to use npm or Yarn for your projects.
|
|
|
|
## Usage
|
|
|
|
Given an existing popper DOM node, ask Popper.js to position it near its button
|
|
|
|
```js
|
|
var reference = document.querySelector('.my-button');
|
|
var popper = document.querySelector('.my-popper');
|
|
var anotherPopper = new Popper(
|
|
reference,
|
|
popper,
|
|
{
|
|
// popper options here
|
|
}
|
|
);
|
|
```
|
|
|
|
### Callbacks
|
|
|
|
Popper.js supports two kind of callbacks, the `onCreate` callback is called after
|
|
the popper has been initalized. The `onUpdate` one is called on any subsequent update.
|
|
|
|
```js
|
|
const reference = document.querySelector('.my-button');
|
|
const popper = document.querySelector('.my-popper');
|
|
new Popper(reference, popper, {
|
|
onCreate: (data) => {
|
|
// data is an object containing all the informations computed
|
|
// by Popper.js and used to style the popper and its arrow
|
|
// The complete description is available in Popper.js documentation
|
|
},
|
|
onUpdate: (data) => {
|
|
// same as `onCreate` but called on subsequent updates
|
|
}
|
|
});
|
|
```
|
|
|
|
### Writing your own modifiers
|
|
|
|
Popper.js is based on a "plugin-like" architecture, most of its features are fully encapsulated "modifiers".
|
|
A modifier is a function that is called each time Popper.js needs to compute the position of the popper. For this reason, modifiers should be very performant to avoid bottlenecks.
|
|
|
|
To learn how to create a modifier, [read the modifiers documentation](docs/_includes/popper-documentation.md#modifiers--object)
|
|
|
|
|
|
### React, Vue.js, Angular, AngularJS, Ember.js (etc...) integration
|
|
|
|
Integrating 3rd party libraries in React or other libraries can be a pain because
|
|
they usually alter the DOM and drive the libraries crazy.
|
|
Popper.js limits all its DOM modifications inside the `applyStyle` modifier,
|
|
you can simply disable it and manually apply the popper coordinates using
|
|
your library of choice.
|
|
|
|
For a comprehensive list of libraries that let you use Popper.js into existing
|
|
frameworks, visit the [MENTIONS](MENTIONS.md) page.
|
|
|
|
Alternatively, you may even override your own `applyStyles` with your custom one and
|
|
integrate Popper.js by yourself!
|
|
|
|
```js
|
|
function applyReactStyle(data) {
|
|
// export data in your framework and use its content to apply the style to your popper
|
|
};
|
|
|
|
const reference = document.querySelector('.my-button');
|
|
const popper = document.querySelector('.my-popper');
|
|
new Popper(reference, popper, {
|
|
modifiers: {
|
|
applyStyle: { enabled: false },
|
|
applyReactStyle: {
|
|
enabled: true,
|
|
fn: applyReactStyle,
|
|
order: 800,
|
|
},
|
|
},
|
|
});
|
|
|
|
```
|
|
|
|
### Migration from Popper.js v0
|
|
|
|
Since the API changed, we prepared some migration instructions to make it easy to upgrade to
|
|
Popper.js v1.
|
|
|
|
https://github.com/FezVrasta/popper.js/issues/62
|
|
|
|
Feel free to comment inside the issue if you have any questions.
|
|
|
|
### Performances
|
|
|
|
Popper.js is very performant. It usually takes 0.5ms to compute a popper's position (on an iMac with 3.5G GHz Intel Core i5).
|
|
This means that it will not cause any [jank](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/anatomy-of-jank), leading to a smooth user experience.
|
|
|
|
## Notes
|
|
|
|
### Libraries using Popper.js
|
|
|
|
The aim of Popper.js is to provide a stable and powerful positioning engine ready to
|
|
be used in 3rd party libraries.
|
|
|
|
Visit the [MENTIONS](MENTIONS.md) page for an updated list of projects.
|
|
|
|
|
|
### Credits
|
|
I want to thank some friends and projects for the work they did:
|
|
|
|
- [@AndreaScn](https://github.com/AndreaScn) for his work on the GitHub Page and the manual testing he did during the development;
|
|
- [@vampolo](https://github.com/vampolo) for the original idea and for the name of the library;
|
|
- [Sysdig](https://github.com/Draios) for all the awesome things I learned during these years that made it possible for me to write this library;
|
|
- [Tether.js](http://github.hubspot.com/tether/) for having inspired me in writing a positioning library ready for the real world;
|
|
- [The Contributors](https://github.com/FezVrasta/popper.js/graphs/contributors) for their much appreciated Pull Requests and bug reports;
|
|
- **you** for the star you'll give to this project and for being so awesome to give this project a try 🙂
|
|
|
|
### Copyright and license
|
|
Code and documentation copyright 2016 **Federico Zivolo**. Code released under the [MIT license](LICENSE.md). Docs released under Creative Commons.
|