-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add option to restore automatic status #29430
Conversation
2a062f6
to
b294de2
Compare
/compile amend / |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
70e7412
to
4e8141c
Compare
{{ $t('user_status', 'Reset to') }} | ||
<a | ||
href="#" | ||
role="button" | ||
@click.prevent.stop="revertCurrentStatus"> | ||
{{ message }} | ||
</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per https://docs.nextcloud.com/server/latest/developer_manual/basics/front-end/l10n.html#improving-your-translations please make the message a parameter in the translation, or use another line break and make the translated string "complete" e.g. Reset status:
and use a real button?
Not sure how I created this, it was random clicking around between status (online/away/...) and predefined statuses |
This note should show below the input field for the status message though, as it's related to the message. Right? |
@CarlSchwan was that fixed? Also it seems this needs rebasing, mind updating the screenshot afterwards? :) |
did we not fix this differently ? or have plans for it in a different context ? @CarlSchwan @nickvergessen |
This would still be highly appiciated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This note should show below the input field for the status message though, as it's related to the message.
cc @nickvergessen do we still need this? |
I implemented this already some time ago |
Fix #29339