Skip to content
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

Improve UX expectations for contentEditable #261

Open
fregante opened this issue Mar 14, 2023 · 0 comments
Open

Improve UX expectations for contentEditable #261

fregante opened this issue Mar 14, 2023 · 0 comments

Comments

@fregante
Copy link
Owner

fregante commented Mar 14, 2023

contentEditable is sent as raw HTML. This is usually expected (judging by the wording used in feature requests and bug reports)

At a minimum, there should be a (permanent?) notification explaining what's happening. I don't want to introduce a confirmation popup, even if it only appears once (because then that information would be lost)

Maybe this information should just be part of the connection popup:

  • Connected to plain text field
  • Connected to raw HTML field. More info
  • Connected to CodeMirror field

The link would point to: https://ghosttext.fregante.com/troubleshooting/

Often contentEditable appears for unrecognized editors, so the help page should include this, perhaps suggesting to switch to the plain text field if one is available (#249, #219)

Also:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant