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

[UI] decouple date and time settings or add support for 24h using ISO 8601 standard #1667

Closed
enkaskal opened this issue Aug 24, 2024 · 3 comments
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements

Comments

@enkaskal
Copy link

First, if this is the wrong place to report please move to the correct place. I tried to use the links for report UI issues according to the wiki, but they're broken; see: safing/docs#108

What would you like to add or change?:

Either decouple the date and time settings (preferred) or add a 24H time that uses the ISO 8601 date standard (YYYY-MM-DD)

Why do you and others need this?:

Conflating the time format with the date format makes it painful for those of us that use 24h clocks and the MM-DD-YYYY calendar format.

@enkaskal enkaskal added the suggestion TYPE: idea for new feature or improvements label Aug 24, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@enkaskal enkaskal changed the title [UI] add support for 24h using ISO 8601 standard [UI] decouple date and time settings or add support for 24h using ISO 8601 standard Aug 24, 2024
Copy link

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Oct 28, 2024
Copy link

github-actions bot commented Nov 5, 2024

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

1 participant