Fix link bubble behaviour - #9156
Conversation
Signed-off-by: As3r1408 <chavezpalpanaaronsamuel@gmail.com>
|
Hi @As3r1408 |
|
I think we discussed this and the main reason for having the link bubble in read only mode was consistency with the edit mode. Briefly checked the linked issue but could not find anything about the discussion. @mejo- I think you looked into this more than I did. What's your take on it? |
I just checked the related issue, turns out I misread something in there, the issue was actually talking about link previews, not the link bubbles like I thought, that's my bad 😅 I understand the thing about consistency, I just thought it would be better UX-wise |
📝 Summary
This improves link interaction in read-only mode.
Previously, clicking a link in read-only mode could open the link bubble instead of directly navigating to the linked destination. This change makes links behave more naturally in read-only mode by opening the destination directly when clicked.
The existing link bubble behaviour in editing mode is preserved, including the ability to use the bubble for interacting with links without immediately navigating away.
While making this change, an issue was also encountered where toggling between the link display options could leave the context menu open and briefly show both options as selected. This was fixed as part of the same change so that the menu closes correctly after changing the link display option.
Related to nextcloud/collectives#1026.🖼️ Screenshots
🏁 Checklist
npm run lint/npm run stylelint/composer run cs:check)