-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Uneditable topic field should not be clickable #22565
Comments
Hello @zulip/server-message-view members, this issue was labeled with the "area: message-editing" label, so you may want to check it out! |
Hello there 😃, you could try using this cool bug reporting tool birdeatsbug to help you handle bug reports. Get steps to reproduce |
@alya I'm working on this issue. |
@zulipbot claim |
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior which is fixed in this commit. Fixes zulip#22565.
Currently when a user does not have the permission to edit the topic/content of a message, the edit UI/view source UI correctly shows a greyed out topic/message-content input field, however these fields incorrectly have a click behavior, so to fix this we now would want to use `disabled` prop instead of `readonly` attribute as `readonly` controls can still function and are still focusable whereas disabled controls can not receive focus and are unclickable. Fixes zulip#22565.
@jai2201 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! |
Currently when a user does not have the permission to edit the topic/content of a message, the edit UI/view source UI correctly shows a greyed out topic/message-content input field, however these fields incorrectly have a click behavior, so to fix this we now would want to use `disabled` prop instead of `readonly` attribute as `readonly` controls can still function and are still focusable whereas disabled controls can not receive focus and are unclickable. Fixes #22565.
Currently when a user does not have the permission to edit the topic/content of a message, the edit UI/view source UI correctly shows a greyed out topic/message-content input field, however these fields incorrectly have a click behavior, so to fix this we now would want to use `disabled` prop instead of `readonly` attribute as `readonly` controls can still function and are still focusable whereas disabled controls can not receive focus and are unclickable. Fixes zulip#22565.
Currently when a user does not have the permission to edit the topic of a message, the edit UI/view source UI correctly shows a greyed out topic input field, however this field incorrectly have a click behavior, so to fix this we now would want to use `disabled` prop instead of `readonly` attribute as `readonly` controls can still function and are still focusable whereas disabled controls can not receive focus and are unclickable. Fixes zulip#22565.
This issue has been fixed via #23139. |
When a user can't edit the topic of the message, the edit/view source message view correctly shows a greyed out topic field. However, this field incorrectly has a click behavior. We should fix this.
CZO discussion
The text was updated successfully, but these errors were encountered: