If the responsiveWidth setting is used, the dragAndMove vertical should be disabled. As of now the responsiveWidth setting is ignored when dragAndMove is used.

Also it would be nice to set dragAndMove options per viewport (its just a suggestion and in no way is implemented in fullpage.js yet):

dragAndMove : [
  {
    setting: false
  },
  {
    breakpoint: 500
    setting: 'horizo

• [] bug

• [x ] enhancement

• feature-discussion (RFC)

• Swiper Version: 5.2.1

I ran into the same issue with lazy loading breaking srcset media conditions as: nolimits4web/swiper#2499

The solution for me was to use the data-sizes attribute instead of the regular sizes attribute. This isn't documented in the API however

.英文不是很好，用的是nuxt.js,在刷新引入插件的页面会报window is not defined

// nuxt.config.js
plugins: [ {src: '~plugins/swiper',ssr: false} ],

//plugins文件夹下

import Vue from 'vue';
if (process.BROWSER_BUILD) {
const VueAwesomeSwiper = require('vue-awesome-swiper/dist/ssr');
Vue.use(VueAwesomeSwiper);
}

.vue文件
import { swiper, swiperSlide } from 'vue-awesome-swiper';
compone

Which OS ?

Windows - Expo - Chrome

Version

Which versions are you using:

• react-native-swiper v1.6.0-rc.3
  "expo": "~37.0.3",
  "react": "~16.9.0",
  "react-native": "https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz",

Expected behaviour

Swipe right and dot active update

Actual behaviour

Swipe right and dot active not updated, the first dot i

• I have searched [#979](https://github.com/ptomasr

In my app I need to modify the drop position. If the item is hovering over position X, I need to say that the item will really drop in position Y, and have item Y open up so that it's visually clear to the user that this will happen.

iOS UITableView supports this with this delegate method.

Current behaviour

When I update routes with setState({routes: [...]}); the TabView does not update its tabs.

Expected behaviour

TabView should dynamically update its routes.

Code sample

          <TabView
            navigationState={{ index: pageIndex, routes }}
            renderScene={({ route }) => {
              switch (route.key) {
                case 'track

@alvarotrigo The ReadMe file says that,

But if you make navigation property to true then nothing happens, as in the screen shot there is nothing in the right side of browser window,
![screenshot_20180808_023519](https://user-images.githubusercontent.com/420700

• I have searched the [issues](https://github.com/oliviertassinari/react-swipeable-views/is

When we present a view controller using SPStorkController then turn on personal hotspot then go back to the app, it will look like this:

But if we turn on personal hotspot first, then present a view controller using SPStorkController it will look like this:

![IMG_0736](https:/

In navigation drawer when user click on any specific menu then that menu should be shown selected
How do we do this by using your library...??please help me to figure out this solution.

when the label in the link is not in the current frame no effect will be seen.

The frame that contains the label should be made active.

if there are more than one label with the same name we should scroll to all of them.

IMPORTANT: this issue doesn’t have high priority. If this is too complex to implement we should discuss if there is an easy solution.

Hi all.
I want to submit an issue.
When carousel is opened on a mobile, on android/chrome for example, vertical swiping on mobile screen causes carousel slide to be changed: swiped to next or prev.

why did you skip the onTap callback in version 5? Is there an easy way to create the onTap functionality, when dragging didn't take place?

just copied the example swiper provided by the repo and it throws an Warning: Invalid argument supplied to oneOf, expected an instance of array. but the swiper works fine

my package.json

{
  "name": "taxitul",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "android": "react-native run-android",
   

💅 Details

While implementing this slider at the office, I was navigating around the source files and saw three new props that weren't in the documentation & I was able to use ⚡️

I tried to open a branch for the pull request but it seems I wasn't allowed at this stage 😢

Would love to contribute! This would be my first contribution on Github Issues.

These props are:

• draggable