- Where to find it
- Labelled Pointer Events in the "Selected Column" 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. "auto" (the default) means this column takes the click, the way every box on a page normally does. "none" means the click falls through the column as if it were not there, and lands on whatever is behind it.
The usual reason to choose "none" is an overlay: a badge, a tint, or a caption sitting on top of something the visitor still needs to click. Set Pointer Events to "none" on the overlay so the button or link underneath still works.
Because the setting is inherited, a child can take clicks back with "auto" even when its parent says "none". That is how a clickable button can sit on a pass-through overlay.
What each option does
| Option | What you will see |
|---|---|
auto | The default. Clicks and taps land on this column and its contents. |
none | Clicks and taps pass through this column to whatever is behind it. Descendants can take them back with "auto". |
When you would use it
- A decorative overlay — a gradient, a badge, a caption — should not block the button or link underneath.
- A column is covering another column and you want the one behind to stay clickable.
How to change it
- Select the column, open "Selected Column", then "Pointer Events".
- Choose "none" to let clicks through, or "auto" to take them.
- Open Preview to confirm — the editing canvas keeps the column clickable so you can still select it.
Watch out for
- This setting is left out on the editing canvas so you can still click the column to select it. Open Preview (or check the published page) to see clicks actually pass through.
- "none" on a column that holds a form or a button will make those controls unusable, unless a child sets "auto" to take clicks back.
- On an overlay layer the same setting lives in Layer Settings, and that is usually where you want it: one "none" on the layer frees the whole layer so the base stays clickable.
Related settings
- Overflow
- Widget Pointer Events
- Collection Pointer Events
- Row 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.