-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[BITV] 9.3.3.2/3.1 - Comment section: The input fields for creating and editing comments lack visual labels. (2) #41884
Comments
There was a suggestion to add the same label as in text fields: #37087 (comment) However, adding such a label to What about removing the user avatar here and "Add a comment" label outside here? |
I agree on this we should provide the same style of labels for all input elements, NcRichcontent... NcSelect..., like already did with NcTextarea, to have a consistent UI (from a design perspective). But that is out of scope of this issue.
Why would it be a breaking change? For me it would be a feature that is disabled by default..
This would be a breaking design change an make it inconsistent with any other activity. |
Currently
Adding a label is also a visible change. But what do you mean by other activity? Is it about activities listed in this tab? If that is, should it be consistent? A form is not an activity. |
Yes consider clicking edit on the comment, the expected behavior would be to change the comment to the editable version while keeping all other elements.
That depends on what you are doing with it using the ref directly is pretty dangerous anyways as you then depend on the implementation details. Meaning if we want any methods to be exposed we should use |
You are correct, I missed that. |
Waiting for release of nextcloud-libraries/nextcloud-vue#4907 |
https://report.bitvtest.de/default-en/cbedb5ef-4815-4cba-a83d-995599c178c3.html#checkpoint-9f92015c98-v3-n1
9.3.3.2/11.1 - https://report.bitvtest.de/default-en/cbedb5ef-4815-4cba-a83d-995599c178c3.html#checkpoint-9f92015c98-v11-n1
The text was updated successfully, but these errors were encountered: