Timestamp column should have a calculated width

[alya]

At present, the timestamp column can have different width for different times, causing alignment problems for other components (discussed here). Note well that different locales have very different time representations, so any complete calculated solution must work regardless of locale, language, and 12/24-hour time.

Strategy for fixing this:

I think ideally we’d take some dummy time or collection of times that we expect to be widest, format it for the current locale, render it in a hidden div, ask the browser for its width, and put the width in a CSS variable.

CZO thread 1
CZO thread 2

[zulipbot]

Hello @zulip/design members, this issue was labeled with the "design" label, so you may want to check it out!

[TejasGoyal0]

@zulipbot claim

[aryan-bhokare]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @aryan-bhokare! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

[himanshuaggar]

@zulipbot claim

[zulipbot]

@himanshuaggar This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks!

[aryan-bhokare]

I think this issues has been already solved.
@zulipbot abandon

@alya maybe you can close this issue.

[alya]

@aryan-bhokare Why do you say that? I don't see any merged PRs linked to this issue.

[aryan-bhokare]

I am very sorry. Maybe I misunderstood something else.
I read this CZO and thought it is solved.
But the timestamp width issue is still not fixed.

[arnavchhokra]

@zulipbot claim

[arnavchhokra]

Hi, please review this PR #27098

[aryan-bhokare]

Hi @alya can you please review the PR #27166 !

[zulipbot]

@arnavchhokra You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!

[andre-foliveira256]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @andre-foliveira256! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

[zulipbot]

@andre-foliveira256 You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!