- Where to find it
- Labelled Pointer Events in the "Entire Row" section of the Modify drawer.
- Per device
- Yes — you can set one value for every screen, or separate values for phone, tablet, and desktop.
- Underlying CSS
pointerEvents
In plain English
Pointer Events decides who receives a click or tap on the whole row. "auto" (the default) takes the click. "none" lets the click fall through the row as if it were not there, and land on whatever is behind it.
The usual reason to choose "none" is an overlay row sitting on top of something the visitor still needs to click. Because the setting is inherited, a column inside the row can take clicks back with "auto".
What each option does
| Option | What you will see |
|---|---|
auto | The default. Clicks and taps land on this row and its contents. |
none | Clicks and taps pass through this row to whatever is behind it. Descendants can take them back with "auto". |
When you would use it
- A decorative row — a tint, a caption band — should not block the content underneath.
- A row is covering another row and you want the one behind to stay clickable.
How to change it
- Open "Entire Row", then "Pointer Events".
- Choose "none" to let clicks through, or "auto" to take them.
- Open Preview to confirm — the editing canvas keeps the row clickable so you can still select it.
One value, or one per device? Every input in this setting sits under a “Same value for all resolutions” checkbox. Leave it checked for a single value everywhere, or uncheck it to give phones, tablets, and desktops their own. How per-device values work.
Watch out for
- This setting is left out on the editing canvas so you can still click the row to select it. Open Preview to see clicks actually pass through.
- "none" on a row that holds a form or a button will make those controls unusable, unless a child sets "auto" to take clicks back.
Related settings
- Pointer Events
- Widget Pointer Events
- Collection Pointer Events
- Using a CSS variable instead of a typed value
- Setting a different value per device
For developers
The technical reference for what this setting produces: MDN: pointer-events. You do not need any of it to use the setting — it is there for whoever is building the components or debugging the published page.
Where to go next
- Back to the full attribute reference
- The Composer — the editing surface these settings live in.
- Publishing — how a change like this reaches your live site.