all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve_flutter_frontend 0/2] fix #7045: regression: add extra padding around the body to avoid system intrusions
Date: Wed, 19 Nov 2025 13:57:09 +0100	[thread overview]
Message-ID: <20251119125711.165181-1-s.shaji@proxmox.com> (raw)

We had two reports [0][1] where the bottom system navigation bar were obscuring
with the app UI. Inorder to fix the issue wraped the qemu and lxc
overview pages inside `SafeArea`. The options config sheet UI were also
getting obscured due to the navigation bar. Fixed the same by wrapping
the content of the sheet inside a `SafeArea`. 

- [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7034
- [1] https://bugzilla.proxmox.com/show_bug.cgi?id=7045

Shan Shaji (2):
  fix #7045: regression: avoid system intrusion from navigation bar
  cleanup: run `dart format .` command to fix formatting

 lib/widgets/pve_cd_selector_widget.dart  |  96 +--
 lib/widgets/pve_config_list_tile.dart    |  64 +-
 lib/widgets/pve_lxc_options_widget.dart  | 179 +++---
 lib/widgets/pve_lxc_overview.dart        | 344 +++++------
 lib/widgets/pve_node_overview.dart       | 724 ++++++++++++-----------
 lib/widgets/pve_qemu_options_widget.dart | 334 ++++++-----
 lib/widgets/pve_qemu_overview.dart       | 303 +++++-----
 7 files changed, 1041 insertions(+), 1003 deletions(-)

-- 
2.47.3



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


             reply	other threads:[~2025-11-19 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 12:57 Shan Shaji [this message]
2025-11-19 12:57 ` [pve-devel] [PATCH pve_flutter_frontend 1/2] fix #7045: regression: avoid system intrusion from navigation bar Shan Shaji

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=20251119125711.165181-1-s.shaji@proxmox.com \
    --to=s.shaji@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