ha-switch without text is causing unwanted scrollbar

[Misiu]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.

The problem

While working on view visibility editor I noticed that when shadow dom of ha-switch is empty I get an unwanted scrollbar.

As a quick fix I'm using  :

<ha-switch
  .userId="${user.id}"
  @change=${this.valChange}
  .checked=${this.checkUser(user.id)}
  >&nbsp;</ha-switch
>

This cause unwanted scrollbar to appear:

<ha-switch
  .userId="${user.id}"
  @change=${this.valChange}
  .checked=${this.checkUser(user.id)}
  ></ha-switch>

Affected PR: https://github.com/home-assistant/frontend/pulls

Expected behavior

ha-switch without text shouldn't cause unwanted scrollbars to appear.

Steps to reproduce

Environment

• Home Assistant release with the issue: 0.107.0.dev0
• Last working Home Assistant release (if known):
• Browser and browser version: Chrome 80.0.3987.132, Firefox 73.0.1
• Operating system: Windows 10

Problem-relevant configuration

Javascript errors shown in your browser console/inspector

Additional information

[bramkragten]

It is not the lack of text that causes this, but the margin (right) of the switch. The ripple probably gets too big. We have to wait for mwc to fix this.

[Misiu]

@bramkragten is this reported as a bug? If yes could you please link the issue.

[bramkragten]

I have not filled one, if there is none could you do that maybe?

[Misiu]

https://github.com/material-components/material-components-web-components is the correct repo?

[bramkragten]

Yes :-)

[Misiu]

@bramkragten it would be awesome if the demo site would show users in view visibility tab. This would help with presenting the bug to mwc team. Is this possible to add?

[bramkragten]

https://material-web-components-j7ezgp.stackblitz.io
https://stackblitz.com/edit/material-web-components-j7ezgp

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.