• [] 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

I think a better "point of view" can be omitted for better reading because everyone knows what you are talking about, which the sample code might not compatible on their machines or browsers

In recent versions, if slidesToShow is set to a value greater than the number of slides, all of the slick-cloned slides will be visible.

To replicate:
in the PlayGround (https://codesandbox.io/s/ppwkk5l6xx) update the settings:

var settings = {
      dots: true,
      slidesToShow: 5
    };

Version 0.21.0 does not behave this way. With version 0.21.0 if the slidesToShow is gr

Bug description:

Accordion Custom header demo does not follow WAI-ARIA Authoring Practices for accordion.

The title of each accordion header is contained in an element with role button.
Each accordion header button is wrapped in

I used the same code as provided in the documentation but the text is out the image container. When I debug the code, then I get to know that there is not CSS for the title.

<Text style={styles.title} numberOfLines={2}> { item.name } </Text>
Can anyone please provide me the css so that I can get the look as mentioned in the example GIF ?

The documentation states that this is Glide's structure, but specifically mentions adding the track attribute. So if that's required, is the HTML class structure also required or is it just for example?

<div class="glide">
  <div class="glide__track" data-glide-el="track">
    <ul class="glide__slides">
      <li class="glide__slide">0</li>
      <li class="glide__slide">1</li>
  

Bug description

For a custom tab heading with an input element. It is not possible to insert a space in this input.
It seems that the space is not possible because of this code block:

https://github.com/valor-software/ngx-bootstrap/blob/161f419c67daed188ad7a936aad4875f2cbc4dd5/src/tabs/tabset.component.ts#L101-L107

Plunker/StackBlitz that reproduces the issue

https://stackblitz.c

When you pass the true argument to the destroy method it does not restore the markup on IE11.

Sorry for not providing a CodePen/JSFiddle example, they do no support IE.

When I use arrow key navigation on a slider, all Sliders on the current Page slide, too.

slider settings:
{
arrowKeys: true,
autoplay: false,
autoplayHoverPause: true,
container: "#cclt__events__event-list",
speed: 600
}
Tiny-slider version: 2.9.2
Chrome 78

 Swiper(
           loop: true,
           transformer:  BannerItemTransformer(),
           scale: 0.8,
           itemBuilder: (BuildContext context, int index) {
             return ImageView(
               url: (entity == null || entity.data == null) ? null : entity.data[index].img,
               width: screenWidth,
               height: ratio * screenWidth,
             );

Describe Your Environment

• What version of nuka-carousel are you using?
  4.5.8
• What version of React are you using?
  16.8.6
• What browser are you using?
  MS Edge
• What machine are you on?
  Windows

Describe the Problem

1. Create a slider with two slides. One of them must be video slide with HTML5 video tag;
2. Open slider in MS Edge browser;
3. Check video controls and try to

Steps to reproduce the behavior:
/

Expected behavior:
It would be nice to be able to change the footer text (currently hardcoded: {activeView} of {totalViews}) without replacing the whole Footer component.
https://github.com/jossmac/react-images/blob/89ba2786959e62fc91a639e09da4498bd79dd7c3/src/components/Footer.js#L112-L117

Actual behavior:
The only option to change the

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.

Hi everyone!

Because English is not my native language I will be very grateful for any help with vue-agile documentation. If you are an English native speaker or you know English very well, please take a moment to review the Readme file in dev branch. If you find a typo or any langauge mistake do a commit and a pull request o

Would appreciate a quick summary of browser support for each component in the Readme. A bit like what you did in this pen: http://codepen.io/LFeh/pen/oEula