Bubble Card version: v3.2.5
Home Assistant: accessed via Nabu Casa remote UI
Installation method: HACS
Describe the bug
A standalone card_type: pop-up card, placed directly as a top-level card in a masonry view (not nested in a vertical-stack), mounts in the DOM with a valid config and receives hass, but never renders any visible content. Its shadow root only ever contains the host <style> block — no button, no icon, no name text. getBoundingClientRect().height is permanently 0.
To Reproduce
- Add a new view to a
masonry-type dashboard containing only this card:
-
- views:
-
-
-
- type: custom:bubble-card
-
-
-
-
-
-
-
-
- Load the view.
Expected behavior
A visible bubble button labeled "Isolation Test" that opens an empty pop-up when tapped.
Actual behavior
Nothing renders. The bubble-card custom element is present in the DOM with config set correctly, but its shadow root is limited to:
<style>:host{display:inline-block;width:100%;vertical-align:top;}</style>
Debugging done
- Confirmed via direct DOM inspection (deep shadow-root traversal) that the element mounts,
isConnected is true, and .config matches the YAML exactly.
-
- Manually calling
el.hass = hass and el.setConfig(el.config) on the live element completes without throwing, but shadow root content still doesn't update.
-
-
- Ruled out: entity references,
show_state, visibility conditions, nested cards: content (tested with cards: []), caching (reproduced in a fresh private window and after full service-worker/cache clear), and interference from other custom cards (reproduced in a brand-new view containing only this one card).
-
-
-
- No console errors or exceptions are thrown during mount or the failed render.
-
-
-
-
- Bubble Card is confirmed loaded and initializing correctly (version banner logs to console on every page load).
Suspected cause
This may be related to the "deferred shell creation for inactive standalone pop-ups" change mentioned in the v3.2.3–v3.2.5 release notes. It's possible the deferred-rendering logic is incorrectly gating the trigger button itself (which must always render) rather than only the pop-up's dialog content (which should legitimately be deferred until opened).
Bubble Card version: v3.2.5
Home Assistant: accessed via Nabu Casa remote UI
Installation method: HACS
Describe the bug
A standalone
card_type: pop-upcard, placed directly as a top-level card in amasonryview (not nested in a vertical-stack), mounts in the DOM with a validconfigand receiveshass, but never renders any visible content. Its shadow root only ever contains the host<style>block — no button, no icon, no name text.getBoundingClientRect().heightis permanently0.To Reproduce
masonry-type dashboard containing only this card:Expected behavior
A visible bubble button labeled "Isolation Test" that opens an empty pop-up when tapped.
Actual behavior
Nothing renders. The
bubble-cardcustom element is present in the DOM withconfigset correctly, but its shadow root is limited to:Debugging done
isConnectedistrue, and.configmatches the YAML exactly.el.hass = hassandel.setConfig(el.config)on the live element completes without throwing, but shadow root content still doesn't update.show_state,visibilityconditions, nestedcards:content (tested withcards: []), caching (reproduced in a fresh private window and after full service-worker/cache clear), and interference from other custom cards (reproduced in a brand-new view containing only this one card).Suspected cause
This may be related to the "deferred shell creation for inactive standalone pop-ups" change mentioned in the v3.2.3–v3.2.5 release notes. It's possible the deferred-rendering logic is incorrectly gating the trigger button itself (which must always render) rather than only the pop-up's dialog content (which should legitimately be deferred until opened).