[shell] Init script affects the behavior of Anchor element

[hanaTsuk1]

I noticed in init.ts that there's a click event listener on anchor elements, triggering a shell open.

I'm using Tiptap (a text editor), and there's a scenario where clicking on anchor elements during editing doesn't trigger default behavior. But now tauri directly invokes shell open.

Perhaps it would be beneficial to add some checks, such as whether the parent element is contenteditable or something

[amrbashir]

How many levels of parent must we check for? because it seems like tiptap HTML structure is as follows:

<div contenteditable>
	<p>
		Some text <a href="url">url</a>
	</p>
</div>

so, if we check the parent, the issue will still persist, and we would need to check the parent of the parent and so on but how many levels must we check? I am not sure how to fix this yet but looks like we may need to add an option to disable this behavior.

[hanaTsuk1]

Yes, adding a disabled option would be optimal
In my idea, check whether the parent node has the contenteditable attribute step by step. When the check for the existence of this attribute ends, determine whether to open the link by judging contenteditable

let currentNode = target;
let contentEditable = false;

while (currentNode !== null) {
    if (typeof currentNode.getAttribute('contenteditable') == 'string') {
        contentEditable = currentNode.getAttribute('contenteditable') === 'true'
        break;
    }

    currentNode = currentNode.parentNode;
}
if (!contentEditable) {
    invoke("plugin:shell|open", {
        path: t.href,
    });
}
e.preventDefault();