in the case when content is simple text.NOTE: Setting options in the HTML-template in the way like This css-class is set explicitly in the View and reflected by OwlDOMData.isGrab This css-class is set explicitly in the View and reflected by OwlDOMData.isDragable This css-class is set explicitly in the View and reflected by OwlDOMData.isResponsive This css-class is set explicitly in the View and reflected by OwlDOMData.rtl This css-class is set explicitly in the View and reflected by OwlDOMData.isLoading This css-class is set explicitly in the View and reflected by OwlDOMData.isLoaded It's set explicitly in the View and reflected by OwlDOMData.isRefreshed This css-class is set explicitly in the View itemElement, itemClass, stageElement, stageOuterClass, stageClass, refreshClass, loadedClass, loadingClass, rtlClass, responsiveClass, dragClass and grabClass The option nestedItemSelector doesn't work. This css-class is set explicitly in the View of CarouselComponent This tag is set explicitly in the View of CarouselComponent navElement, navContainer, navContainerClass, navClass, dotContainer, dotClass and dotsClass The option fallbackEasing doesn't work because it's being used by $.animate() in Owl Carousel created by means of jQuery. Here they are corresponding to the width of the element which takes 100% of its parent element width.

In the original Owl Carousel, all responsive breakpoints are corresponding to window width. The option responsiveBaseElement doesn't work. if there must be 2 visible slides, the width of the item will be half of the carousel window. In other words, the width of the slide with unprovided width will be set according to how much space in visible carousel window the slide must take. carouselWidth=1200 and items=4, the width of the slide will be 1200/4=300). At the end it will be calculated as (width of carousel)/(items) (e.g. When the width isn't provided for a certain slide and is provided for other slides, firstly it will be 0 (this is the default value). In this lib data-merge is changed to dataMerge, which is the property of the directive. The original Owl Carousel requires setting data-merge to each slide besides setting merge=true. Options which require setting data- attributes are:

The usage of these options is explained below. Mostly this is about options which require setting data- attributes to DOM-elements and which set names of classes and tags in the HTML-markup. NOTE: ngx-owl-carousel-o has the different usage of some of them. Explanations of meanings and the usage of options are in Owl Carousel Documentation. Ngx-owl-carousel-o uses the same options as Owl Carousel.

Add a slugline to owl carousel