customHTMLRenderer strangely broken in viewer (3.0.2)

[lborgman]

Describe the bug

In the editor customHTMLRenderer works as expected and gives this result for me:

<p>before <a href="mm4i-search:interesting" style="color:red">find</a> after</p>

But in the viewer I instead get this very strange result:

<p data-nodeid="7">before <a href="mm4i-search:interesting" style="color:red" data-nodeid="11"></a>find<a 
    href="mm4i-search:interesting" style="color:red" data-nodeid="11"></a> after</p>

The HTML code is copied directly from Developer tools in Google Chrome today (which I just updated).

To Reproduce

const mm4iRenderer = {
    link(node, context) {
        console.log({ node });
        const { origin } = context;
        const url = node.destination;
        const isAlfa = url.startsWith("mm4i-search:");
        console.warn("mm4iRenderer link", url, isAlfa);
        if (isAlfa) {
            const linkAttrs = { href: url };
            linkAttrs.style = "color:red";
            console.log("after red", linkAttrs);
            return [
                { type: 'openTag', tagName: 'a', attributes: linkAttrs },
                { type: 'closeTag', tagName: 'a' }
            ];
        }
        return origin();
    }
}

Expected behavior

See above.

Desktop (please complete the following information):

• OS: Windows 11
• Browser: chrome
• Version: 3.0.2

[lborgman]

For the moment I will use a workaround:

• use the editor instead
• hide irrelevant parts
• add a shield that takes care of pointerdown events

It looks like it is about 50 lines of code.

[lborgman]

While implementing this I just saw something that might be relevant for the bug.
Searching the ww mode element there are three :

2: <a href="mm4i-search:interesting" style="color:red" data-nodeid="5"></a>
1: <a href="mm4i-search:interesting" style="color:red">find</a>

Two of them are those empty <a>:s I mentioned before.

This suggests to me there is a bug either in Prose-mirror or in Chromes handling of "contenteditable".

[lborgman]

I decided not to use customHTMLRenderer. In my case I can get the same result with some CSS.