parchment | Parchment is Quill 's document model

It is more related on how class work. I just take your class as example to avoid overwhelming you.

I was an idiot and missed an important step in the html decoding process. Leaving this question up with this answer (which solves the problem) incase anyone else stumbles upon a moment of mental ineptitude.

I was using the package quill-delta-to-html to convert my delta's back to usable html. Of course this package doesn't know how to register custom blots. You have to do that manually before converting.

I just put it inside a wrap, and it worked:

HTML:

Okay I found the issue while debugging something else that was related to Parchment as well.

The issue is updateUIViewController() gets called each time the encompassing SwiftUI state changes (and when coming back to the foreground), and the PageController wrapper provided by the library will call reloadData() since the data source data has already been set. So to resolve this just remove/comment out the reloadData() call since the PageController will be re-built if the relevant state changes. The same issue was the cause for the bug I was debugging.

Without expected results, this is a guess, but returns results and should be enough for you to fill in the gaps:

You will need to add that element in side of your Quill instance as well, using the Inline class.

Here is an example:

How about simply adding one more .insert(' ', {}) after last insert? This should add one normal span after the inserted class.

This is how it will be:

Your current code doesn't compile on my 2.4.0 version of Parchment, and SwiftUI so I've tried to infer various details - the code works fine in native SwiftUI components. I would consider re-architecting the code though so that the @Published property references a Model object - this is better SoC and allows to be shared better (given your EnvironmentObject I suspect you are passing this view model to multiple views).

Parchment is not ideal as mentioned by @Asperi. PageView wraps a UIViewController as the paging controller, and each page is nested inside another UIHostingController! A better approach is to make PagingController a wrapped UIPageViewController for the Scene conforming to UIViewControllerRepresentable, with UIViewControllers. I would just implement this from scratch than use Parchment - it may be overkill, and perhaps some aspects could be designed better.

I may be missing something, but it's hard to help without further code in context. Also, from your example, setting PageView in the parent view makes more sense and that your subviews in parent view controller should not capture touches (set userInteractionEnabled to false in UIKit or View modifier .disabled(true) in SwiftUI). This is if ParentView is overlaid on top of ChildView.