
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
vuejs-slider-component
Advanced tools
Can use the slider in vue1.x and vue2.x. (No longer update vue1.x, but still can be normal use)
npm install vue-slider-component --save
if the component initialization in a v-show="false" / display: none container or use transform / animation / margin to change the location of the component, there may be an exception ( The slider cannot be used, because the component can not initialize the size or slider position ).
The solution:
v-if instead of v-show or display: none.show to control display.refresh method.Example: https://jsfiddle.net/2xy72dod/254/
cd example/
# install dependencies
npm install
# serve with hot reload at localhost:9000
npm run dev
<template>
<div>
<vue-slider v-ref:slider :value.sync="value"></vue-slider>
</div>
</template>
<script>
// Used only in vue1.x version
import vueSlider from 'vue-slider-component/src/vue-slider.vue';
new Vue({
el: '#app',
components: {
vueSlider
},
data: {
value: 1
}
});
</script>
<template>
<div>
<vue-slider ref="slider" v-model="value"></vue-slider>
</div>
</template>
<script>
// Used only in vue2.x version
import vueSlider from 'vue-slider-component'
// or
// import vueSlider from 'vue-slider-component/src/vue2-slider.vue'
new Vue({
el: '#app',
components: {
vueSlider
},
data: {
value: 1
}
});
</script>
import vueSlider from 'vue-slider-component/src/vue2-slider.vue'
| Props | Type | Default | Description |
|---|---|---|---|
| direction | String | horizontal | set the direction of the component, optional value: ['horizontal', 'vertical'] |
| event-type | String | auto | the event type, optional value: ['auto', 'none'] |
| width | Number[,String(in horizontal)] | auto | width of the component |
| height | Number[,String(in vertical)] | 6 | height of the component |
| dot-size | Number | 16 | determines width and height of the sliders. to set different values of width & height use dot-width & dot-height props |
| dot-width | Number | value of dot-size prop | width of sliders. if specified, overrides value of dot-size |
| dot-height | Number | value of dot-size prop | height of sliders. if specified, overrides value of dot-size |
| min | Number | 0 | the minimum value |
| max | Number | 100 | the maximum value |
| interval | Number | 1 | the gap between the values |
| show | Boolean | true | display of the component |
| speed | Number | 0.5 | transition time |
| disabled | Boolean | false | whether to disable components |
| debug | Boolean | true | if you do not need to print errors in the production environment, can be set to process.env.NODE_ENV !== 'production' |
| piecewise | Boolean | false | whether to display the piecewise |
| piecewise-label* | Boolean | false | whether to display the label. example |
| tooltip | String, Boolean | always | control the tooltip, optional value: ['hover', 'always', false] |
| tooltip-dir | String[,Array(in range model) | top(in horizontal)or left(in vertical) | set the direction of the tooltip, optional value: ['top', 'bottom', 'left', 'right'] |
| reverse | Boolean | false | whether the component reverse (such as Right to left, Top to bottom) |
| value | Number, String, Array, Object | 0 | initial value (if the value for the array open range model) |
| data | Array | null | the custom data. |
| clickable | Boolean | true | Whether or not the slider is clickable as well as drag-able |
| stop-propagation* | Boolean | false | All events call stopPropagation |
| real-time* | Boolean | false | Whether the real-time computing the layout of the components |
| lazy* | Boolean | false | At the end of the drag and drop, to synchronization value (if each update to high consumption of operation (such as Ajax), it is more useful) example |
| fixed* | Boolean | false | Fixed distance between two values (valid only in range mode). [example] |
| process-dragable* | Boolean | false | Whether the process bar is draggable (valid only in range mode). example |
| formatter* | String,Function | null | Formatting a tooltip values, Example: formatter='¥{value}' or formatter: (v) => `¥${v}`. example |
| use-keyboard* | Boolnea | false | Whether to open the keyboard control (Only support the arrow keys). example |
| actions-keyboard* | Array | [(i) => i - 1, (i) => i + 1] | In the keyboard control mode, reduce(←, ↓) and increase(→, ↑) the calling method.(i is the index value) |
| bg-style* | Object | null | The style of the background. |
| slider-style* | Object[,Array(in range model), Function<Value, Index>] | null | The style of the slider. |
| process-style* | Object | null | The style of the process bar. |
| piecewise-style* | Object | null | The style of the piecewise dot. |
| piecewise-active-style* | Object | null | The style of the piecewise dot in the activated state. |
| tooltip-style* | Object[,Array(in range model), Function<Value, Index>] | null | The style of the tooltip. |
| label-style* | Object | null | The style of the label. |
| label-active-style* | Object | null | The style of the label in the activated state. |
| focus-style* | Object[,Array(in range model), Function<Value, Index>] | null | The style of the slider when it is focused. (Works only when use-keyboard is true) |
prop*: [only support vue2]
| Name | Type | Description |
|---|---|---|
| setValue | Params: value [, noCallback] | set value of the component |
| setIndex | Params: index* | set index of the component |
| getValue | Return: value | get value of the component |
| getIndex | Return: index* | get index of the component |
| refresh | null | Refresh the component |
| Name | Type | Description |
|---|---|---|
| callback | Params: value[Number] | values change when the callback function |
| drag-start | Params: context[Object] | Drag the start event |
| drag-end | Params: context[Object] | Drag the end event |
| Name | Description |
|---|---|
| tooltip | Customize the tooltip slot. optional value: [value, index(only range model)] |
| piecewise | Customize the piecewise slot. optional value: [label, index, active, first, last] |
| label | Customize the label slot. optional value: [label, index, active, first, last] |
# When using the template element as a slot, can add special properties scope or slot-scope to get the value.
e.g.
<vue-slider v-model="value">
<template slot="tooltip" scope="{ value }">
<div class="diy-tooltip">
{{ value }}
</div>
</template>
</vue-slider>
<!-- In vue2.5 above, please use slot-scope instead of scope -->
<vue-slider v-model="value">
<div class="diy-tooltip" slot="tooltip" slot-scope="{ value }">
{{ value }}
</div>
</vue-slider>
This hack is just to avoid the server side 'document' error when using it with Nuxt.js. Use it if you don't need to have this component rendered on the server side.
components. i.e.import NoSSR from 'vue-no-ssr'
let components = {
/**
* Add No Server Side Render component
* to make client DOM math the server DOM
*/
'no-ssr': NoSSR
}
<no-ssr>
<vue-slider ref="slider"></vue-slider>
</no-ssr>
if (process.browser) {
// in older versions of nuxt, it's process.BROWSER_BUILD
let VueSlider = require('vue-slider-component')
components['vue-slider'] = VueSlider
}
export default {
components
}
FAQs
Can use the Slider component in vue1.x and vue2.x
We found that vuejs-slider-component demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.