Allow disabling large file optimizations to allow Markdown within HTML blocks

[anthonyv.be]

Use case or problem

Currently Markdown blocks within HTML blocks are not parsed, as an optimization to handle large files. However, this makes it cumbersome to use e.g. <details>/<summary> HTML tags.

Proposed solution

Obsidian should use a treshold file size for toggling its large file optimizations: only when a file’s size is above the treshold, would the large file optimizations be enabled. However, Obsidian should still allow the optimizations to be disabled.
Compare this with VS Code, for example: when opening a large file, it notifies that some features are unavailable due to the large file size. But the user is still able to forcefully enable the features:

Current workaround (optional)

Foldable callouts have been proposed as an alternative, but these are neither valid CommonMark nor recognized by VS Code’s parser. (And in a semantic sense “callouts” are kind of the opposite of “details”.)

Related feature requests (optional)

Parse markdown inside <details><summary> tags

Use case or problem I’m using Obsidian to write dairy, and today when I’m trying to create a folded part (<details>), I came across the problem where Markdown syntax isn’t being properly parsed & previewed; and Direct empty lines put everything below that line outside the <details>, even if </details> is after that. This empty line problem also exists in a lot of other tags, such as <font>, <center>, etc. I’ve also tried the same text on a lot of other markdown editors (randomly grabbe, al…

[smartguy1196]

Good reference to a competing markdown editor. Really a well-written feature request