Operating system:
I could verify this on Windows and Android.
Debug info:
SYSTEM INFO:
Obsidian version: v1.1.16
Installer version: v1.1.9
Operating system: Windows 10 Home 10.0.19045
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
Additional information
If the official answer to this bahaviour is âWorks as expectedâ, I recommend changing this expectation because this behaviour creates problems for users.
Trailing white-space relevant for syntax is asking for trouble.
âThe principle of least astonishment (POLA ), aka principle of least surprise (alternatively a law or rule ),[1][2] applies to user interface and software design.[3] It proposes that a component of a system should behave in a way that most users will expect it to behave, and therefore not astonish or surprise users.â Principle of least astonishment - Wikipedia
Yes, if you know about this you wonât be astonished, but most users will first not know about this.
And ---<space> is used in YAML for directive indicators, such as between log items.
In both cases they seem to pass POLA (for users who are used to the specs). Both are outside of Obsidianâs control, I think, but perhaps could be raised with the people responsible for YAML and Markdown specs.
As such I think that invisible trailing white space is not a great idea in any interface. Hope that Obsidian will one day add a core option to display white spaces and non-printing artefacts in edit mode.
EDIT: At least users can see by the onscreen formatting in edit mode that the text is being rendered as YAML (guess that might depend on the theme used) and so know that something needs changing, and when viewing in read mode Obsidian will give an âinvalid YAMLâ warning. Safety nets, of sorts? Writing aids?