Let’s imagine the following scenario: User edits a document that’s written in a specific syntax That syntax supports a specific feature, that cannot be disabled in the editor (because of lack of configuration) User inserts a content with the provided feature For instance, let’s say we can’t disab…

[image] ClementEXWiki: I’m aware of that, but I’m specifically talking about cases where a feature cannot be disabled in the editor for any reason (lack of programmability, etc.) The short answer is that it needs to be fixed so that it can be disabled (ie a PR should be sent to BlockNote to f…

What we’ve tried to do in the past (at least in the wiki editor and I think also in CKEditor), is to customize the editor’s features based on the syntax capability. In your example if the target syntax doesn’t support nested list, then the editor shouldn’t allow you to enter a nested list. That’s b…

[image] vmassol: What we’ve tried to do in the past (at least in the wiki editor and I think also in CKEditor), is to customize the editor’s features based on the syntax capability. In your example if the target syntax doesn’t support nested list, then the editor shouldn’t allow you to enter a n…

I’m aware of that, but I’m specifically talking about cases where a feature cannot be disabled in the editor for any reason (lack of programmability, etc.)

I think it’s useful to distinguish between two case: the editor generates content that can’t be saved with the backend syntax the backend syntax supports content that the editor can’t edit For the first case the best solution, as Vincent and Manuel mentioned, is to disable the editor features tha…

Handling unsupported syntax features in documents

Development

mleduc March 20, 2026, 2:37pm 3

+1 for this approach, this is what I was also saying in New package for syntax-specific features - #7 by mleduc

+1 as well