Responsive design and screen sizes
Edit inherited styles, configure breakpoints, and inspect the real page in the live device canvas.
Watch the video
Chapters and transcript Captions are included.
Screen sizes and inheritance#
Desktop is the base style. By default, Tablets covers widths up to 1024 pixels and Phones covers widths up to 767 pixels. Site screen settings can change these values and enable additional sizes.
| Screen | Default threshold | Availability |
|---|---|---|
| Wide | At least 2400px | Optional |
| Desktop | Base style | Always |
| Laptop | Up to 1366px | Optional |
| Tablet wide | Up to 1200px | Optional |
| Tablets | Up to 1024px | Always |
| Phone wide | Up to 880px | Optional |
| Phones | Up to 767px | Always |
Enabled maximum widths must descend strictly. Wide must be larger than all maximum widths. Accepted sizes range from 320 through 3840 pixels. A smaller screen inherits from the next larger enabled screen, then Desktop. Wide inherits Desktop. Disabling an optional screen retains its stored overrides but stops emitting its rules.
Change a responsive value#
- Select the element or its container.
- Choose the screen size above the inspector controls.
- Enter the setting for that size. A blank field removes that override and inherits.
- Compare neighboring sizes before saving.
Gray placeholders show inherited values. An empty value is not zero. Clear one property to restore inheritance, or clear the selected screen's settings as one undoable action. Theme Looks apply across sizes; they do not erase explicit responsive settings.
Live device canvas#
With the live device canvas enabled, choosing Tablets or Phones moves the actual page into a frame, initially 768 or 390 pixels wide. Adjust its width beside the inspector. Media queries, viewport units, and fixed positioning then follow the frame. A frame wider than the available workspace can scroll horizontally.
The device canvas is a user preference. With it disabled, the screen selector changes the scope you are editing without moving the page into a frame. Inspect the real visitor page at target widths as well.
The current live canvas is different from older script-free size-preview copies. It moves page nodes; it does not rerun arbitrary scripts. Integrations with document-level listeners can subscribe to kindly-edit:canvas on the main window and bind once to the event's detail.document and detail.window. The event also identifies the device.
Hover, focus, and visibility#
Style has Normal, Hover, and Focus. State values can differ at each screen size. Layout and Advanced controls change Normal. Forced interaction states in the editor are temporary and are not saved as permanent states.
Set visibility in Style → Responsive visibility. Since 0.9.15 it is one row of screen sizes: each size is a button (Shows on Desktop, Shows on Tablets, Shows on Phones); click one to hide the element on that size, and click it again to show it. A hidden size is crossed out. One line under it says where the element shows (Shows on …, Hidden on … or Hidden on every screen size).
Hidden-at-size content stays visible with an editing outline so you can select it. Preview and the visitor page apply the actual visibility rules. Screen ranges are exclusive for visibility, rather than cumulatively hiding every smaller size.
Storage and output#
Desktop Normal uses inline style. Other screens use data-ke-<screen>, with -hover and -focus variants. Desktop states use data-ke-hover and data-ke-focus. The server validates declarations and generates responsive CSS. Generated style nodes are removed from editable HTML before saving.
Screen configuration is stored in cantata_edit_screens. Built-in component layout defaults still use their own 1024px and 767px rules; changing site screen settings does not rewrite every theme or component media query.
Verify the result#
Check immediately below and above each active boundary, not just a named phone width. Test text wrapping, image crop, navigation, buttons, grid order, and horizontal overflow. Save and reload, then inspect the published page after publishing. Test keyboard focus separately from hover.