Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tooltip Timezones #7564

Open
bdowling opened this issue Dec 20, 2022 · 3 comments · May be fixed by #9635
Open

Tooltip Timezones #7564

bdowling opened this issue Dec 20, 2022 · 3 comments · May be fixed by #9635
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@bdowling
Copy link

bdowling commented Dec 20, 2022

What would you like to be added?

Relative datetime columns such as Created show up with a tool-tip that has no timezone. On relatively recent events, one can infer that this is actually the browser's host timezone, but there is no indication of that. Any thoughts to adjusting format (currently is medium) this to include a timezone attribute?

[matTooltip]="date | date: format">

https://angular.io/api/common/DatePipe

image

Why is this needed?

Sometimes it's important to know exactly when things happened and without a timezone the user could guess thinking everything was in UTC or system time for example.

@bdowling bdowling added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 20, 2022
@floreks
Copy link
Member

floreks commented Dec 21, 2022

This tooltip always shows the UTC time of the server AFAIR. This is just a plain creationTimestamp field of the resource. We can add UTC information there for clarity.

@bdowling
Copy link
Author

I originally thought they'd be UTC as well, based on historical issues noted in this repo, but in practice I found it was localtime. It uses the angular DatePipe mentioned above without defining a TZ, so it defaults to host/browser timezone. From a user standpoint, this is more intuitive IMHO in a browser context even though DevOps folks often work with systems in UTC timezone. I just think it should display a timezone regardless.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 21, 2023
@maciaszczykm maciaszczykm added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 22, 2023
@lsq645599166 lsq645599166 linked a pull request Nov 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants