@webapp-suite/elements.popover
v0.10.0
Published
<h1 align="center"> <a href=""> <img alt="webapp-suite" src="https://webapp-suite.com/wp-content/themes/webapp-suite/img/brand/logo-black.png"/> </a> </h1>
Downloads
11
Readme
➤ Properties
| Property | Attribute | Type | Default | Description | | --- | --- | --- | --- | --- | | opened | opened | Boolean | false | Is the popover visible or not | | placement | placement | String | | Placement, relative to the anchor. Could be 'topLeft', 'topRight', 'bottomLeft', 'bottomRight' | | header | header | String | | Text in the title | | anchor | anchor | String | | Anchor element for relative positioning. If you need to position absolutely, leave this empty | | positionLeft | position-left | String | | Left offset when popover is positioned absolutely. Use any valid css syntax for the 'left' property | | positionTop | position-top | String | | Top offset when popover is positioned absolutely. Use any valid css syntax for the 'top' property |
➤ Slots
| Name | Description | | ------- | ---------------------------------------------------------------------------------- | | content | Content in the main section of the popover | | footer | Content in the footer section of the popover, most of the time `ts-button-group` |
➤ Events
| Name | Description | Payload | | ------------- | --------------------------------------------------- | ------- | | popover-close | Emitted when user press the close button in popover | |
➤ How to use it
- Install the package of popover
$ npm i @webapp-suite/elements.popover --save- Import the component
import '@webapp-suite/elements.popover';or
<script src="node_modules/@webapp-suite/elements.popover/lib/popover.umd.js"></script>Use it like demo
Our components rely on having the
Open Sansavailable, You can see thefont-weightandfont-styleyou need to load here, or you can just load it from our package (for now)
<link rel="stylesheet" href="node_modules/@webapp-suite/elements/src/fonts.css" />➤ Polyfills
For supporting IE11 you need to add couple of things
- Don't shim CSS Custom Properties in IE11
<!-- Place this in the <head>, before the Web Component polyfills are loaded -->
<script>
if (!window.Promise) {
window.ShadyCSS = { nativeCss: true };
}
</script>You have two options for polyfills library:
- Installation
$ npm i @open-wc/polyfills-loader- Load it
import loadPolyfills from '@open-wc/polyfills-loader';
loadPolyfills().then(() => import('./my-app.js'));- Installation
$ npm i @webcomponents/webcomponentsjs --save- Enable ES5 class-less Custom Elements
<script src="/node_modules/@webcomponents/webcomponentsjs/custom-elements-es5-adapter.js"></script>- Load appropriate polyfills and shims with
@webcomponents/webcomponentsjs
<script src="/node_modules/@webcomponents/webcomponentsjs/webcomponents-loader.js" defer></script>➤ How to contribute
Thanks for your interest and help!
- First thing you need to do is read this [Component Checklist] which contains lots of important information about what you need to consider when you are creating/changing components
General info
You can find some links to useful materials about what we are using and some tutorials and articles that can help you get started.
➤ Polyfill Limitations
You can see a list of limitations that we should watch out for, here
➤ License
- You can always create forks on GitHub, submit Issues and Pull Requests.
- You can only use webapp-suite Elements to make apps on a webapp-suite platform, e.g. webapp-suite.com.
- You can fix a bug until the bugfix is deployed by webapp-suite.
- You can host webapp-suite Elements yourself.
- If you want to make a bigger change or just want to talk with us, reach out to our team here on GitHub.
You can read the full license agreement in the LICENSE.md.