Tabs · Autoplay

Tabs with an icon that move on by themselves; the open one fills a progress bar while its time runs, and a pause button with a countdown ring sits under the list. Beside them, a photo with a white card.

Full-page views: desktop, phone and dark mode

At 1440px wide.

At 390px wide.

With your site in dark mode.

See it live: Tabs · Autoplay on fancybricks.co — the live preview, and the button that copies it.

In the builder

Preview on the front end. Scripts don't run inside the builder, so here you only see the layout: the tabs don't change on their own, the progress bar and the ring stay empty and there is no accordion on phones here (that needs the scripts). Save and open the page to see the full result.

Structure

This is what the Bricks Structure panel shows after you paste the template. Component instances say which component they are.

Autoplay tabs
  Container
    Tabs
      Intro
        Intro   (FBK Intro)
      Tab menu
        Tab · A route drawn around you
          Tab · Icon
          Tab · Text
        Tab · Ferries and slow crossings
          Tab · Icon
          Tab · Text
        Tab · Walks with a local guide
          Tab · Icon
          Tab · Text
        Tab · Photo stops at the right hour
          Tab · Icon
          Tab · Text
      Pause
        Pause button
          Toggle · Pause icon
          Toggle · Play icon
      Tab content
        Pane · Every day, planned around how you travel
          Panel
            Panel · Photo (background)
            Card
              Card · Intro   (FBK Intro)
                Card · Button   (FBK Button)
        Pane · The best part is often in between
          Panel
            Panel · Photo (background)
            Card
              Card · Intro   (FBK Intro)
                Card · Button   (FBK Button)
        Pane · Walk it with someone who lives there
          Panel
            Panel · Photo (background)
            Card
              Card · Intro   (FBK Intro)
                Card · Button   (FBK Button)
        Pane · Be there when the light is right
          Panel
            Panel · Photo (background)
            Card
              Card · Intro   (FBK Intro)
                Card · Button   (FBK Button)
    Tabs · autoplay, pause and up/down keys
    Tabs → accordion below 767px (optional, deletable)

The template also pastes a dashed note above the section, with the short version of this page. It only shows inside the builder, never on the published page — see Builder notes.

How to adjust

Every step is the same move: pick the element in the Structure panel, change its Properties.

Where are those panels?

How to adjust a template shows every one of them in a screenshot of the real builder: the Structure and Properties panels, the classes on an element, a component's style families and the field where a CSS variable goes.

The classes this element carries, in the Bricks panel.

This template's own component, with its Style group open.

1. Paste the template in Bricks first — see Copy and paste.
2. Select Intro, Card · Intro ×4 (FBK Intro) › Properties: Eyebrow, Hide eyebrow, Title, Title level, Lead, Hide lead · Style group: Eyebrow style, Highlight, Title size, Accent line · Layout group: Alignment, Layout, Background, Spacing · Motion group: Reveal in slider.
3. Select Card · Button ×4 (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
4. Select Tabs › one tab = a title and its pane, in the same order: duplicate both to add one.
5. Spacing, sizes, color and timing with no property of their own: the CSS variables below.

CSS variables

These are the only values in the template meant to be changed by hand. Copy the block, paste it, edit the numbers.

The Custom CSS field of this template's own element, with one of its variables as a real example.

/* «Tabs» · class .fbk-tabsplay */
.fbk-tabsplay {
  /* Time each tab stays open before the next one (seconds) */
  --fbk-t-autoplay: 6s;
}

Paste the block in the element's Style → CSS field (the selector is already in it), or set the same variables on the class itself to change every copy at once. The values are your framework's variables, so they follow your site: Choosing a framework.

Requirements

• Code execution. Needs "Execute code" enabled for the role in Bricks → Settings → Custom code, or the JS block shows as plain text instead of running.

What each requirement is, and how to set it up once for the whole site: Requirements.

Finish by hand

• Change the icons, tab texts, photos and the title, text and button of each card.
• Time per tab: --fbk-t-autoplay on the Tabs element (class .fbk-tabsplay), in seconds. The autoplay never stops on hover; it holds while keyboard focus is inside, off screen and on phones (accordion), and starts paused for visitors who ask for reduced motion. Keep the pause button: it is required for anything that moves on its own.
• Each piece has its own class (intro, menu, tab, icon, text, content, pane, panel, photo, card): edit its styles in the panel.
• Active and hover styles are in the Custom CSS of the class .fbk-tabsplay__tab (Style > CSS): %root%.brx-open is the open tab (white) and %root%:hover the tab under the mouse; the progress bar is %root%::before (color, height). The open icon box is in .fbk-tabsplay__icon; the photo and card entrance in .fbk-tabsplay__panel.
• The autoplay and accordion scripts need "Execute code" enabled for the role; delete the accordion block if you do not want it on phones.

On phones

The template is designed desktop first, the Bricks default, and only changes at the two widths the library uses:

• 991px and below — .fbk-tabsplay, .fbk-tabsplay__content, .fbk-intro.
• 767px and below — .fbk-tabsplay__panel, .fbk-section.

Those changes live in Bricks' own breakpoint fields, so you edit them where you always do: pick the breakpoint in the toolbar and the same fields follow.

Careful with the classes shared by the whole library (fbk-section, fbk-intro, the component classes): a change there shows up in every template that uses them.

If your site's breakpoints are set up mobile first, copy the mobile-first variant of the template instead — see Copy and paste.

Accessibility

In this template, keyboard focus is visible on every interactive piece; movement is cut back when the visitor's system asks for less motion; the state screen readers need is already set (aria-hidden, aria-label).

What is checked on every template, and what depends on your own palette: Accessibility.

Dark mode

With your site in dark mode this section turns dark too — the class fbk-section--auto-dark on the section does it. Remove the class to keep it light.

Its background is a modifier on the section, so you can swap it for any of the ones the template is checked with: fbk-section--soft, fbk-section--light, fbk-section--dark.

How the library follows your site's color scheme: Dark mode and preview.

Replaces

• Tabs Auto Play from Fancy Bricks 2.0

What happened to the old libraries, and what to do with pages already built with them: Migrating from 1.0/2.0.