Support for the bookmarks pane uses a completely wrong approach.
It looks at the content of the HTML-notes, the displayed text. But that text is actually completely arbitrary, as users can alias their bookmarks. E.g. naming the bookmark that points to Note 1.md "Note 2" or literally anything else:
It currently "works", because most people do not choose aliases for their bookmarks and seldom have name collisions (/folder 1/Note.md and /folder 2/Note.md).
The DOM does not contain any information on where the bookmarks are pointing and thus to solve this issue there needs to be a completely different approach to identify the links and add required metadata to the DOM.
Example, the bookmark is for a note called Note 1.md, the alias is Fake Note. The DOM does not contain information on the path:
Support for the bookmarks pane uses a completely wrong approach.
It looks at the content of the HTML-notes, the displayed text. But that text is actually completely arbitrary, as users can alias their bookmarks. E.g. naming the bookmark that points to
Note 1.md"Note 2" or literally anything else:It currently "works", because most people do not choose aliases for their bookmarks and seldom have name collisions (
/folder 1/Note.mdand/folder 2/Note.md).The DOM does not contain any information on where the bookmarks are pointing and thus to solve this issue there needs to be a completely different approach to identify the links and add required metadata to the DOM.
Example, the bookmark is for a note called
Note 1.md, the alias isFake Note. The DOM does not contain information on the path: