UIX (https://uix.lf.technology) has dialog support where dialogs can be styled using UIX theming. In you case you would start with something like the following which is light DOM styling but likely what you need to style the dialog vis CSS vars.
As this dialog uses ālargeā and UIX canāt change that, you can trick the width by styling --ha-dialog-width-lg. You also need to style --ha-dialog-width-full.
Height can be adjusted with --ha-dialog-min-height.
Border radius you be adjusted with --ha-dialog-border-radius
So the following will get the media play dialog pseudo āfullscreenā. There is further you could do like remove title, float close icon over the top etc. but this would need shadow root. If you wish to go further pick this up in UIX thread or UIX repo discussion.
# theme yaml assumed
uix-dialog: |
:host(.type-hui-dialog-web-browser-play-media) {
/* CSS for ha-dialog when it is in shadow root of hui-dialog-web-browser-play-media */
--ha-dialog-width-lg: 100vw;
--ha-dialog-width-full: 100vw;
--ha-dialog-min-height: var(--safe-height);
--ha-dialog-border-radius: 0;
}
This is not correct. wa-dialog has part dialog but not ha-dialog.
Put your media queries in style - all the string here is wrapped with :host { } so that will work fine and then style the size with --popup-width and perhaps min/max as well.
See pinned issue in repo. Specifically, dialog in wa-dialog shadow root styles border none so if you wish to style border either style fully on dialog with border full form or make sure to include border-style as well as other border parameters
Iāve read it, but I canāt seem to put the border back. Any advice? Thanks.
Recommend you migrate to UIX where you can use uix_path to find the path of what you need to style Even though am at ease looking in the DOM and working out what the path, uix_path() got me the theme boilerplate in one step.
Hi everyone,
Iāve been trying to do things on my own, but I canāt seem to accomplish what Iām trying to do, so I come here for help.
I have a popup displaying the changelog from each new HA release, so the size of this popup change (or should) depending if thereās a new release of HA or not.
Until 2026.2, it was changing no problem, but since 2026.3 and all the changes that came with it, I canāt achieve this anymore.
I use " --popup-max-width:" and āāpopup-min-width:ā to size my popup, but when I look at the CSS being used to scale my popup, I see that only āāpopup-min-width:ā is being used to calculate the size of my popup.
How can I set a min and a max value for my popup to dynamically scale for the content inside ?
The Home Assistant dialog now have fixed sizes. Default is medium and this is what Browser Mod uses. If you set --popup-width this overrides the medium dialog size. So you need to set a width with --popup-width. The max width then limits the width. So you could set width at a fixed pixel size and then max width as a percentage of view width.
Iām playing with checking if browser is registered or not⦠and it seems that i donāt quite understand ābrowser_entitiesāā¦
I created a badge where it says whether browser is registered or not. This badge
shows āBrowser not registeredā if itās not, or it shows registered name otherwise. This badge does all i want: shows status, and / or registers new browser. However, it seems that i canāt transfer this into a ānormalā card (say, my favorite custom button card), i keep getting entity not found (but in a badge it IS foundā¦).
Is there any way to do so?, or, should i ask: what am i missing?
Browser Mod tile and badge are special in that they convert the generic browser_entities.XXX into the local sensor before rendering a stock tile/badge. So browser_entities.browserID wonāt work in any card/badge except Browser Mod tile and badge.
You can try and fashion your own button card with JS templates. Look at window.browser_mod.registered and then you get the local sensor IDs by looking up window.browser_mod.browserEntities.
ahhhhā¦i totally missed browser mod tile card. It suits me just fine, as my goal is achieved: i have a card which is positioned anywhere on dashboard, not at the top ābadgesā section. I generally donāt use badges at the top, thatās why i searched for ānormalā card. This cardās behaviour is pretty interesting, though: if browser is not registered then clicking on the card shows window when i can enter and register browser, while if it IS registered it only shows āmore-infoā, but i canāt (donāt need to, too) change browserās ID).
Yes. All by design. Also if you have a device that often loses browser id, just add the user to privileged users (check doco) and that user can change browser id. Normally only admins get access to change form on click.
2.10.1 will not perform a script action from within a popup window itself, whereas prior versions would. For example, when a thumbnail is tapped, this card will successfully call a script to open a larger popup window showing mail delivery, as it has always done:
The prior behavior was that tapping within the popup picture-entity card would call a corresponding script showing mail collection, but no longer does so, instead simply closing the popup window:
Recent changes in dialogs in Home Assistant Frontend has meant there are different timings which mean that code that is resusing the standard popup tag (none) may have issues as code to show popup will close existing popup of same tag (none) if open, but the flag for open and whether the close sequence has completed is where the timing can be an issue and the new popup opened is then closed.
If you can make a real simple config with cards and script that would help me replicate the issue faster and update to cater for the issue.
In the meantime, an easy workaround is to give each popup its own tag.
Thanks for the immediate response. Iām not sure what you mean by āgive each popup its own tag.ā I have the popups embedded in scripts, each with unique names. (The issue seems unique to v2.10.1, not resulting from changes to HA, as I can revert to v2.10.0 and the new issue goes away.)
2.10.1 has fixes relating to popups and reuse of same tag, which has caused your issue. You may wait until I have time to review or try the tag workaround.
The workaround is to give different popups a tag tag: my-tag. See Multiple Popups