Error handling about kotlinx.html HOT 2 CLOSED

Do you think, such approach is reasonable? I have no idea how does it work in JS target.

My original implementation was very simple:

interface TagConsumer<out R> {
     // ...

    // default implementation simply re-throws the exception after closing the tag
    fun onError(exception: Exception) : Unit = throw exception
}

fun <T : Tag> T.visit(block: T.() -> Unit) {
    consumer.onTagStart(this)
    try {
        this.block()
    } catch (err: Exception) {
        consumer.onError(err)
    } finally {
        // all tags are properly closed
        consumer.onTagEnd(this)
    }
}

from kotlinx.html.

The only problem I can see is that if we have a chain of consumers then the error handler in the middle of the chain can only write directly to the delegate rather than pass through the whole chain

pros: we can't get infinite error handling issue
cons: it's not clear what the state the outer consumer will have after writing directly inside of the error handler

from kotlinx.html.