openbullet / openbullet/OpenBullet2

[Bug]: 2k and 4k screen bugged in openbullet

Open
#1,085 0 comments 0 reactions 1 assignee View on GitHub

@openbullet is already working on this.

Since Aug 1, 2024.

area:frontend bug client:web
Dominant language
C#
Stars
2.4k
Forks
602
PR merge metrics
No merged PRs in 30d

Description

This issue respects the following points:
  • This is a bug, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Description of the bug

On Openbullet2 when going on the main dashboard with a 2K/4K+ screen the metrics are not displayed well, but after going in the browser console and closing it back it re-arrange everything well see the screenshot below

Reproduction steps
  1. Go on the home dashboard
  2. Open the devtools menu
  3. Close the devtools menu and see the metrics become normal after it
What is the current bug behavior?

The metrics on the dashboard doesn't not render well

What is the expected correct behavior?

The metrics should be render inside the case not going outside of it

Version of the client

Version: [0.3.1]

Type of client

Web client

Environment
- OS: Proxmox
- Virtualization: LXC + Docker
- Browser: Chrome 127
OpenBullet2 logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

1920x1080 Screen :
chrome_JfKaKv4hXy
2560x1440 Screen:
chrome_vJelRY2iBL

After the manipulation:
chrome_j0SV5MHtXI
chrome_IqrWKeStY0

Relevant LoliCode if needed

No response

Additional information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.