All topics

Guide

Breakdance Tabs: Two related views of the same topic

Two related views of the same topic. Learn when to use Tabs, follow a practical setup, and diagnose common problems.

3 min read · Updated 4 October 2026

Partial configuration check on a separate test installation; see the checked controls and limits below.

What it does and when to use it

Organizes content into switchable panels. Use it for the specific job described below. If a simpler native element can deliver the same outcome, prefer the simpler structure and fewer competing styles.

Before you start

This is a Breakdance catalogue recipe for use with a compatible Breakdance Elements for Oxygen extension. It is not a guarantee of availability in your version. Check the installed element list and official reference before following the steps. Exact control labels can differ; this recipe has not been executed on this site.

Worked example: Two related views of the same topic

Scenario: Two related views of the same topic. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Choose short tab labels such as Setup and Example.
  2. Put a concise, self-contained explanation in each panel.
  3. Test selected state, keyboard operation and mobile labels.

Checked controls and test limits

Checked on 4 October 2026 with Oxygen 6.2.0-beta.9, Breakdance Elements 1.1.0-beta.5 and Forms 1.1.0.beta.1 on a separate test installation.

In the Content tab, open Content → Tabs. Each item has Title and Content. The test used “Setup” and “Example”, with the first tab active and Open On Hover off. Right Arrow moved selection and displayed the matching panel. Both labels fitted a 390px viewport.

This is a partial configuration and frontend check, not verification of every setting, integration or accessibility requirement. Use Oxygen’s interface for these settings.

Expected result

You should have two related views of the same topic. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.

Troubleshooting

If panels represent unrelated pages, use navigation links instead. Important instructions should not depend on visitors discovering an unlabeled tab.

Checks before publishing

Use real text and assets rather than a perfect placeholder. Check a long label, narrow screen and empty-data state before publishing.

  • Compare desktop and narrow-screen layouts using actual content.
  • Follow every destination and operate interactive controls with a keyboard where applicable.
  • Check an empty or unavailable-data state when the element depends on a provider.

Official reference and version notes

Official Tabs reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.

Check extension element visibility in Oxygen. An element may be hidden where a native equivalent exists.

Need more help with this guide? Contact Benjamin →

Explore more topics