From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 21B961FF0E9 for ; Thu, 16 Jul 2026 15:52:00 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 619EB213B9; Thu, 16 Jul 2026 15:51:59 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 16 Jul 2026 15:51:25 +0200 Message-Id: Subject: Re: [PATCH cluster 2/2] fix #5475: configurable window title From: "Thomas Ellmenreich" To: "Thomas Lamprecht" , X-Mailer: aerc 0.20.0 References: <20260716084807.77400-1-t.ellmenreich@proxmox.com> <20260716084807.77400-3-t.ellmenreich@proxmox.com> <3f04e2b9-d39f-4604-b169-c3ae530256af@proxmox.com> In-Reply-To: <3f04e2b9-d39f-4604-b169-c3ae530256af@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784209866404 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.213 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: E6E6SW2RIZYJNCKRRS47Q2DZNWP4ALF6 X-Message-ID-Hash: E6E6SW2RIZYJNCKRRS47Q2DZNWP4ALF6 X-MailFrom: t.ellmenreich@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: That definitely sounds like the better solution. I'll use 'ui-settings' and then 'title' as the nested settings. On Thu Jul 16, 2026 at 2:50 PM CEST, Thomas Lamprecht wrote: [snip] > The window term is a bit opaque here in the backend, but can be fine.. > > Would favor using a format here from the start to make this easier to exp= and, e.g. > I could imagine adding support for passing a color that gets rendered in = the favicon > e.g. as circle or corner for some differentiating from that side, or a pr= efix/suffix > added to the title. Needs more thought, and we can expand such things la= ter true our > default-key schema support, but might be nicer to start out already with = a format > now already. > > we could do a more general "ui" or "ui-settings" one to see this from a g= lobal UI > settings POV? and then there simply "title" or as property. [snip]