Acy Watson

> (Although in the first case—deletion—would the normalization not get triggered, since neither list is dirty?) If we rely on node transforms (or the same logic) it seems that it...

@EgonBolton I think it's a bit clearer, but in implementation those two stages can possibly just be in the transformation stage of the lifecycle. Otherwise, AFAICT, this comment can mostly...

> There are many cases where blocking the operation is what you want. If I want each document to begin with a title, I could only do: root: {content: "heading{1}...

@Awjin > Interesting. Are the ergonomic benefits of a schema worth the added API surface? This is definitely something on my mind. I think the decision ultimately depends on to...

Interesting discussion around the original schema API design for ProseMirror: https://discuss.prosemirror.net/t/schema-api-design/47 Overall, I get the impression so far that ProseMirror schemas (in the latest versions) are centralizing configuration of editor...

Thanks @zurfyx - good insights. I have started work on this, but my API design looks quite a bit different. I think we can try to reconcile this offline. Specifically,...

> But they all need to focus on editor Why do you think this? I don't think this should be the case.

This still repros in 0.11.1

> If my suggestion is accepted, I would be more than happy to contribute to the code. Awesome, thank you! I think one thing we'd need to think about here...

> There are valid use cases for less common protocols and they should be easy to enable for use cases where that is necessary and not foolish from a security...