Multi widget glance containers overlapping

[smalls89]

Description

Only opening this here as opening a bug said it would be closed without a discussion.

When a service contains multiple widgets including glance, the first non-glance widget is overlapped by a following glance widget.

possible fix in css is changing .chart+.chart to .chart+.chart, .service-container+.chart
this was changed in the browser and was unable to locate in source

non-glance/glance issue

glance/glance widgets are fine

non-glance/glance widget modded css result

homepage version

latest 0.10.9

Installation method

Docker

Configuration

- test:
  widgets:
    - type: glances
      version: 4
      url: -----
      metric: cpu
      username: -----
      password: -----
      refreshInterval: 1000
      pointsLimit: 25
    - type: glances
      version: 4
      url: -----
      metric: network:enp6s18
      username: -----
      password: -----
      refreshInterval: 1000
      pointsLimit: 25        
- Proxmox:
  icon: proxmox.webp
  href: -----
  description:
  ping: -----
  siteMonitor: -----
  widgets:
    - type: proxmox
      url: -----
      username: -----
      password: -----
      fields: ["vms", "lxc", "resources.cpu", "resources.mem"]
    - type: glances
      version: 4
      url: -----
      metric: sensor:CPUTIN
      username: -----
      password: -----
      refreshIntercal: 1000
      pointsLimit: 25
    - type: glances
      version: 4
      url: -----
      metric: cpu
      username: -----
      password: -----
      refreshIntercal: 1000
      pointsLimit: 25

Container Logs

No response

Browser Logs

No response

Troubleshooting

none

[smalls89]

additional custom.css kludge so glances stop overlapping each other

.service-container+.chart {
  margin-top: 2.1em !important;
}
.chart+.chart {
  margin-top: 2.5em !important;
}

[shamoon]

Nevermind about the issue, just took a second.

Closed by #4652

Thanks

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.