Vertical tabs

Four sets of vertical tabs with different things in their panes: the sidebar of a content edit form with the summaries core writes under each tab, one pane per family of element core has -- text, choices, dates and files, fieldsets and details, tables, buttons and dropbuttons, status messages and the progress bar -- the contrib widgets installed on the sites, and the states that change the markup: a description, a long title, a tab hidden and shown again, tabs nested in a pane, a set of one, and a required field in a pane that is not the first. The tabs are drawn only above the width breakpoint; below it the panes are a stack of details. Nothing is saved: the button at the foot of the page validates everything, which is how a pane is reached in its error state.

The sidebar of a content edit form

The group NodeForm calls "advanced", with the five panes core and the menu and path modules put in it, in the order their weights give them. The line under each tab is its summary: node.js and menu_ui.js write one per pane from the values in it, and the script of this page writes the same ones, so they change as the fields are filled in. The URL alias pane is the default tab, which is what #default_tab is for -- without one the first pane is shown.

Briefly describe the changes you have made.
Specify an alternative path by which this data can be accessed. For example, type "/about" when writing an about page.
Leave blank for Anonymous.

Authored on

The time that the node was created.

Every family of element in a pane

A pane is a details element with its border removed, so whatever spacing a form item gets from the details around it, it gets here too -- and anything that sets a width, a border or a background of its own meets the edge of the pane rather than a margin. The summary under each tab counts the fields of the pane that hold a value.

A description under the input.
€ per month
Format: Plain text

Plain text

  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
Radios
Checkboxes
With a description under it.

Date and time

Date list

Nothing is uploaded.
A fieldset
The wrapper radios and checkboxes are given, used on its own.
A details element, open
Bordered, inside a pane whose own border has been taken away.
A label and a value with no control, the way a read-only field is shown.
And a description.
Room Capacity Floor
Studio 12 Ground
Workshop 8 Ground
Library 20 First
Garden room 30 Outside
Booking Status Operations
Pottery evening Confirmed
Book club Pending

Status message

A status message, as a pane shows it.

Warning message

A warning message.
Importing
40%
Processed 4 of 10 items.
An item list
  • First item
  • Second item
  • Third item

Contrib widgets in a pane

The widgets that replace a select draw a drop of their own, positioned against the page, and a pane that is hidden until its tab is picked is where they are most likely to have measured themselves wrongly: their width is read while the pane is not displayed. Each pane is one module; a module this site does not have is a pane saying so. The selection widgets example has the full survey of each.

States and edge cases

What a set of tabs looks like away from the happy path. The third pane holds a required field: validate the page with it empty and core opens that pane on the way back, since the error is in it. The checkbox in the first pane hides and shows the last tab through tabHide() and tabShow(), the API the text format form hides the settings of a disabled filter with, and Search API those of a processor -- the tab is hidden, not removed, and the first visible tab is marked again. A pane with #access FALSE is never rendered at all, and is here to prove it: there are five tabs, not six.

The #description of the details element, which core prints at the top of the pane, before its children.
Leave empty and validate the page to see the pane opened on the error.

A set of one

A set with nothing visible in it, which renders as nothing below this heading