Button design layer “plus” button disappears

[StephenTheSavant]

Make sure you're on the latest stable or beta build

• I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I love the new button styling features, however if you delete all of the layers in a buttons style page, the plus sign to add new layer, disappears. You can still click the button, you just can’t see it for some reason.

Steps To Reproduce

Create a button.
Go to the style page in the button.
Delete all the layers on the right hand side of the screen by clicking on the mini trash can’s.

Expected Behavior

The plus sign (to add a layer) should stay visible at all times unless the user is on a separate page.
The “Name” column over the names of the layers should stay visible unless the user is on a separate page.

Environment (please complete the following information)

- Companion Version:5.0.1-stable
- OS:macOS Tahoe 26.5.2
- Browser:DuckDuckGo

Additional context

No response

[Julusian]

I'm not able to reproduce this

[DwayneSamuels]

The clickable area surviving while both the plus glyph and the “Name” header disappear makes a two-state DOM/style comparison especially useful here.

Could you capture the same button editor twice—once with one layer and once immediately after deleting the last layer—and record for the plus hit target:

• outerHTML, getBoundingClientRect(), and accessible name
• computed display, visibility, opacity, color, overflow, and pointer-events
• ::before / ::after computed content, display, and color
• the parent grid/flex template and whether the icon child still exists

Then repeat the zero-layer state once in Chrome or Safari on the same Mac. That gives three clean branches: an icon child removed while its button remains points to conditional rendering; unchanged DOM with changed pseudo-element/content/color points to empty-state CSS; DuckDuckGo-only behavior points to an engine-specific rendering path. A short recording that includes the final delete and first invisible click would also establish exactly when the visual state diverges.

The report’s Expected Behavior currently says the plus sign “will disappear”; I suspect that should say it should remain visible, so confirming that wording would prevent the fix from being tested against the inverse expectation.

This artifact shape may help keep the two states comparable: Browser Bug Test Artifact Checklist.

[StephenTheSavant]

I'm not able to reproduce this

Honestly I can’t explain this. I thought that if it worked for you, then it might be my uncommon browser, duckduckgo. However, I tried doing it in safari and it also didn’t work, so I don’t know what’s going on.