From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ui: fix zero-sized panels on fresh chrome start
Date: Mon, 20 Nov 2023 09:26:52 +0100 [thread overview]
Message-ID: <bbf94fa0-8319-42d5-9a36-0cd255252c32@proxmox.com> (raw)
In-Reply-To: <8fdda233-2e59-442a-b1db-390730307da1@proxmox.com>
On 11/20/23 09:26, Thomas Lamprecht wrote:
> Am 20/11/2023 um 09:07 schrieb Dominik Csapak:
>> On 11/20/23 09:02, Dominik Csapak wrote:
>>> it seems in new versions of chrome , this triggers too early on a fresh
>>> start (when autostarting a pve tab), resulting in the
>>> 'viewWidth'/'viewHeight' being zero pixels. This means we set the width
>>> of the left and the height of the bottom panel to zero pixels, making
>>> them functionally invisible.
>>>
>>> To prevent that, check that the 'viewWidth'/'viewHeight' is big enough
>>> so that the panels still have least 50 pixels left before setting their
>>> size.
>>>
>>> reported on the pve-user list:
>>> https://lists.proxmox.com/pipermail/pve-user/2023-November/017292.html
>>
>> this actually is a different issue, i misunderstood the message
>> from the user...
>>
>> anyway it's a problem i can reproduce here quite easily, so
>
> Is this related to:
> https://forum.proxmox.com/threads/web-portal-rendering-issues-vivaldi-brower.136636/#post-606233
> ?
yes it seems to be the same issue
next prev parent reply other threads:[~2023-11-20 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 8:02 Dominik Csapak
2023-11-20 8:07 ` Dominik Csapak
2023-11-20 8:26 ` Thomas Lamprecht
2023-11-20 8:26 ` Dominik Csapak [this message]
2023-11-20 9:15 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbf94fa0-8319-42d5-9a36-0cd255252c32@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox