Slider (Nestable) Progress Bar

Display a progress indicator for a native Bricks Slider (Nestable). It is tied to slide position, not page scroll, reading progress, or a WooCommerce spending target.

Setup and First Use


Before starting, enable the relevant element or feature family under Bricks → BricksUltimate → General Elements, save, and reopen the Bricks editor. Integrations also require their corresponding plugin to be active.

  1. Configure a native Slider (Nestable) and publish enough slides to test movement.
  2. Identify the slider's actual Script ID.
  3. Add (BU)Slider Progress Bar and enter that ID in Script ID.
  4. Set the track Color, Progress bar color, and Bar width.
  5. Place the bar near the slider and use Bricks layout controls for surrounding spacing.
  6. Test it while navigating with arrows, dragging, and autoplay if enabled.

Controls and Settings


ControlPurpose and usage
Script IDMust match the native slider instance, without a CSS-selector prefix.
ColorControls the track appearance.
Progress bar colorControls the completed/active fill presentation.
Bar widthSets the visible bar width. Use a responsive value that fits the surrounding wrapper.

Responsive Slider Position


The indicator follows the slider's own position and configuration. Changing slides per view can change how progress looks. Verify first, middle, and final positions at every important breakpoint, and expect looping sliders to wrap rather than remain permanently full.

Pair with Custom Arrows


Slider Arrows and Slider Progress Bar can target the same instance. Keep each Script ID consistent. Neither element supplies slider content or replaces the slider's navigation, autoplay, rewind, or responsive settings. AJAX-loaded and repeated sliders require extra attention to runtime IDs and initialization.

Practical Example


Add a full-width progress track below a project slider and custom arrows next to the heading. Point both BU controls to the same slider ID and verify their behavior with autoplay disabled first.

Troubleshooting


  • Static fill: check target ID and slider initialization.
  • Unexpected progress at mobile size: inspect slides-per-page and the actual available positions.
  • Wrong target: confirm the rendered data-script-id rather than reusing an ID from a different slider.

Related Documentation