Ah yeah, I got them the wrong way around. I think it would help if you could use the side to specify where it falls for most use cases. Currently I’m working with decos that ‘belong’ to a mark - a bit ‘out there’ I know - with the potential of overlapping marks occuring. For this particular use case one might need some sort of priority system ultimately for predictable rendering around marks. Maybe that would be too fiddly but, as far as I know, there would be no way to render a widget inside like:
<mark1>
<widget />
<mark2>
text
</mark2>
</mark1>
I think that would be pretttty fiddly (although I’m not too familiar with the render logic) given that it would ask for a priority system that would, at the very least, be shared across both marks and decos at the very least.
I think using the side to infer the node context would be a good start and helpful for some cases, and as for if there were no node after the widget I’m not sure. Would that not be something that could be handled in “userland” so it would be ok just to throw?