Support Decimal Values for “Slides on Display”

[insawasd]

Describe the Problem

Currently, the “Slides on Display” setting in Elementor’s Carousel widgets uses a dropdown with predefined integer values only.

This limits the flexibility of the carousel layout. For example, if I want to display 3.5 slides at a time, there is no way to enter this value through the Elementor interface.

As a workaround, I currently have to use the browser’s Inspect/Developer Tools to manually modify the value in the select option to 3.5.

This makes a simple and common design requirement unnecessarily difficult to achieve, especially when creating layouts where part of the next slide should remain visible as a visual cue that more content is available.

Propose a Solution

I suggest changing the “Slides on Display” setting from a predefined dropdown to a number input field that allows decimal values.

For example, users should be able to enter values such as:

• 3
• 3.2
• 3.5
• 4.5

The input could still have reasonable minimum and maximum values and validation, but allowing decimal numbers would provide much greater control over the carousel layout.

This would make it possible to create partially visible slides directly through the Elementor UI, without requiring users to modify the value manually through browser Developer Tools.

Additional Context

A decimal value such as 3.5 is particularly useful for responsive carousel designs where you want to show three full slides plus half of the next slide.

This is a common UI pattern because the partially visible slide indicates to users that additional content is available and encourages them to swipe or scroll.

The carousel already appears to support decimal values technically, since manually changing the select value to 3.5 through Developer Tools works as expected. The limitation seems to be the Elementor UI, which currently only provides integer values.

Allowing users to enter decimal values directly would therefore provide more flexibility without requiring a workaround.

Agreement

• I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form.
• I agree that my discussion may be closed without further action if it doesn't meet all the requirements outlined in the Feature Request form.