From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shan Shaji <s.shaji@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve_flutter_frontend 0/2] fix #7045: regression: add extra padding around the body to avoid system intrusions
Date: Tue, 9 Dec 2025 11:28:27 +0100 [thread overview]
Message-ID: <176527609025.3125121.2376159537492867563.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251119125711.165181-1-s.shaji@proxmox.com>
On Wed, 19 Nov 2025 13:57:09 +0100, Shan Shaji wrote:
> 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
>
> [...]
Applied, thanks!
[1/2] fix #7045: regression: avoid system intrusion from navigation bar
commit: 674cd0e2b0d33a9d9abefb114225076750a21f46
[2/2] cleanup: run `dart format .` command to fix formatting
commit: 48b77b65186f328b3347173d4deb95491f4c6d36
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-09 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 12:57 [pve-devel] " Shan Shaji
2025-11-19 12:57 ` [pve-devel] [PATCH pve_flutter_frontend 1/2] fix #7045: regression: avoid system intrusion from navigation bar Shan Shaji
2025-11-19 12:57 ` [pve-devel] [PATCH pve_flutter_frontend 2/2] cleanup: run `dart format .` command to fix formatting Shan Shaji
2025-12-09 10:28 ` Thomas Lamprecht [this message]
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=176527609025.3125121.2376159537492867563.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@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