Nexus
Controls cannot be clicked or clicks pass through
Check that visible shapes, hit regions, and transparent areas agree.
Visibility and clickability are related but separate
Transparent pixels do not automatically define pixel-level click boundaries. The host uses declared geometry. Click-through outside the shape is expected; controls outside it indicate a layout/declaration mismatch.
Check the entire clickable region
- Mark the whole panel with data-nexus-window, not only the header. Declare separate shapes for disconnected panels.
- Use rect, rounded, circle, ellipse, or a valid path matching the actual appearance.
- Path points use normalized coordinates; invalid formats are ignored. Diagnose with a simple shape, then restore the intended outline.
- Without window markers, hit testing falls back to a full-page rectangle. Missing or mismatched snapshots may also use a conservative rectangle. Missing markers may block Blender behind the page rather than cause click-through.
Rule out overlays and coordinate mismatches
| Observation | Diagnosis and response |
|---|---|
| A control is drawn outside the shape | Move it inside the active region or extend the shape to its actual bounds. Do not use a transparent full-screen rectangle that blocks other controls. |
| Clicking starts window dragging | Check whether the control falls inside a drag handle. Mark custom interactive controls no-drag. |
| Offset only after scaling or moving monitors | Record display scale, editor layout, and actual click position. Layout and hit testing must use consistent CSS coordinates without applying device scale twice. |
| Visible but obstructed | Check DOM overlays, pointer-events, stacking, and higher host windows. Transparent overlays can still receive clicks. |
The press location determines input ownership
Input ownership is chosen when the button is pressed. A drag starting in Blender does not transfer to the page when crossing it, and leaving a control does not imply reassignment to the host. Release first, then start again in the intended region.
Click three places separately
- Control center: receives the intended click.
- Blank header: drags the window as intended.
- Transparent exterior: lets you operate Blender behind it without an invisible rectangle blocking input.
Check edges at the actual target display scale. Screenshots cannot prove hit testing. For details, see Input and shortcuts.
If unresolved, follow Provide useful diagnostic information to prepare a minimal reproduction and original messages for the add-on author.