Joplin: UX provides "too easy" path to data loss

[hwine]

The UI makes it "too easy" to accidentally select "code view" and run into data loss. By "too easy" I mean:

• "code view" feature can not be disabled
• button is visually distinctive, drawing the eye (and pointer) to it

The resulting UX does not follow the "principle of least surprise" guideline for behaviors.

Environment

Joplin version:

Joplin 1.0.224 (prod, darwin)

Client ID: xxxxxxxxxxxxxxx
Sync Version: 1
Profile Version: 30
Keychain Supported: Yes

Revision: 1899d86 (master)

Platform: macOS, win10
OS specifics:

Steps to reproduce

1. Start a new note
2. Have document with non-wysiwig formatting
3. Try to click "layout", miss and click "code view" instead
4. edit
5. poof markdown lost
6. Try to view/restore prior version of note - find "no note history"

Describe what you expected to happen

As noted, "code view" is still a work in progress, and can lead to data loss. My expectation is that I can disable the feature, so it no longer appears in the "menu bar" and I can't accidentally activate it.

_(Even if wysiwyg worked perfectly, I would still prefer to treat it as any other plugin, and be able to disable it. I like markdown.)_

Logfile

n/a

[dpoulton-github]

@hwine

My expectation is that I can disable the feature, so it no longer appears in the "menu bar" and I can't accidentally activate it.

This has been discussed serveral times on the forum. userchrome.css can be used to remove the "Code View" button.

https://discourse.joplinapp.org/t/warning-if-you-switch-between-the-markdown-and-wysiwyg-editor-certain-kinds-of-data-washes-away/10013/3

[hwine]

imho, a not-documented-officially, need to poke under-the-hood, does not address the "principle of least surprise".

I understand if you don't want to take on the work. Are you open to a PR for this?

[dpoulton-github]

Are you open to a PR for this?

Not my call!
I just thought I'd bring to your attention a way of achieving what you were seeking.
@laurent22 is the project owner.

[laurent22]

The UI is going to change anyway (see in forum) and this issue will be less relevant afterwards.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[stale[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.