From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Gabriel Goller <g.goller@proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] fix: ui: spinner position
Date: Mon, 16 Oct 2023 12:04:12 +0200 [thread overview]
Message-ID: <1d8ff790-3e6c-435d-a58d-5a7ab32245fb@proxmox.com> (raw)
In-Reply-To: <5f00418c-adfe-4e4a-8f5c-8e0b80e1ff1c@proxmox.com>
Am 16/10/2023 um 11:51 schrieb Gabriel Goller:
> On 10/13/23 15:04, Dominik Csapak wrote:
>> we could also create our own class that uses the gif as a background image, or
>> simply embed the gif directly? then we'd keep the image and could still
>> add a translated text
> To be honest, I wouldn't add a text. We would have to separate between 'Running'
> and 'Loading', because that's not the same thing (e.g., in pbs we use the spinner
> on the snapshot size—where it would be 'Loading'
No, there it would be running to, as that indicates that there's no
size available due to a currently running job; or do you mean
something else?
> —and on the task log—where it would
> be 'Running'). Then we would also have to adjust some tables, because the 'Running'
> or 'Loading' text won't fit (As far as I know, they use a fixed width).
To clarify, I'd explicitly only left-align those spinners for when
used as job running spinners, not for loading – and IIRC we do not
have any per-cell or per-row loading indicators anyway, as we always
load all data of a grid at once (or at least fake doing so), but never
row or even cell-wise.
So moving this new alignment behavior into its own class, that derives
from the ExtJS one, seems more reasonable to avoid odd rendering issues
for the cases where the left-alignment isn't desired.
If we then add a text to that is an independent decision, but it surely
wouldn't hurt accessibility.
next prev parent reply other threads:[~2023-10-16 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 14:20 Gabriel Goller
2023-10-11 11:06 ` Gabriel Goller
2023-10-12 9:28 ` Dominik Csapak
2023-10-12 11:49 ` Gabriel Goller
2023-10-12 12:34 ` Dominik Csapak
2023-10-12 12:40 ` Gabriel Goller
2023-10-13 12:38 ` Thomas Lamprecht
2023-10-13 13:04 ` Dominik Csapak
2023-10-16 9:51 ` Gabriel Goller
2023-10-16 10:04 ` Thomas Lamprecht [this message]
2023-10-16 11:57 ` Gabriel Goller
2023-10-16 12:41 ` Gabriel Goller
2023-10-18 10:09 ` Gabriel Goller
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=1d8ff790-3e6c-435d-a58d-5a7ab32245fb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pbs-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox