all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH widget-toolkit] fix #6312: limit consent window to viewport size
Date: Wed, 14 May 2025 14:37:22 +0200	[thread overview]
Message-ID: <1787e7dd-cd67-407f-9087-22623ffa234a@proxmox.com> (raw)
In-Reply-To: <20250411100127.3409617-1-d.csapak@proxmox.com>

Am 11.04.25 um 12:01 schrieb Dominik Csapak:
> The consent window will try to size itself according to the max/min
> constraints set, but those might be too large for some viewport sizes.
> 
> Since it's not possible to set those to relative viewport sizes (ExtJS
> does it's own layout, so we can't use CSS), we have to save the original
> size (while factoring in the constraints) and on resize of the viewport
> (or the window) limit ourselves to that (minus 10 px safety margin).

The window is now quite a bit shorter, requiring much more scrolling even
though my Browser Viewport has lots of (vertical) space left.

Without looking into this much it seems your original size calculation
might be off.

> 
> Even with that the window will adhere to the set constraint sizes,
> but it should be viewable with any sensible display/viewport size.
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> we could think about implementing such a limit for all of our windows
> in e.g. Toolkit.js, but I'm not sure if that's wise, since not all
> windows are as flexible with the size as the consent window.

With both ExtJS and our layouting on top this would probably indeed not
work out really well in practice, so I'd not do that for now.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-05-14 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 10:01 Dominik Csapak
2025-05-14 12:37 ` Thomas Lamprecht [this message]
2025-05-15  8:02 ` Dominik Csapak

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=1787e7dd-cd67-407f-9087-22623ffa234a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pve-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal