Skip to content

UX: rich editor [details] caret hover and padding #33057

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

Merged
merged 1 commit into from
Jun 3, 2025
Merged

Conversation

renato
Copy link
Contributor

@renato renato commented Jun 3, 2025

Improves the styles for the [details] caret pseudo-element on the rich editor.

Kapture 2025-06-03 at 14 50 33

Additionally, having summary have no pointer-events is important so Firefox doesn't mess with our caret positioning when clicking it.

@@ -6,7 +6,6 @@ const extension = {
attrs: { open: { default: true } },
content: "summary block+",
group: "block",
draggable: true,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if draggable, it's harder to drag-select a text within any part of the details/summary, so I think removing it is a better default

@jjaffeux
Copy link
Contributor

jjaffeux commented Jun 3, 2025

Looks better, thanks

@renato renato merged commit 25e8051 into main Jun 3, 2025
18 checks passed
@renato renato deleted the composer_details_ui branch June 3, 2025 18:23
megothss pushed a commit that referenced this pull request Jun 3, 2025
Improves the styles for the [details] caret pseudo-element on the rich
editor.

Additionally, having `summary` have no `pointer-events` is important so
Firefox doesn't mess with our caret positioning when clicking it.
martin-brennan pushed a commit that referenced this pull request Jun 10, 2025
Improves the styles for the [details] caret pseudo-element on the rich
editor.

Additionally, having `summary` have no `pointer-events` is important so
Firefox doesn't mess with our caret positioning when clicking it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants