Does this work on edge? They have a different prefix registered but can't test this myself.

Edge looks to be extension

And also for e-readers/android the url is kiwi-extension://

I'd recommend using a similar approach to this instead

Another option is to do something similar to the second half (after the &&) of this:

Which checks if the URL matches the protocol of import.meta.url (which will be chrome-extension or whatever is appropriate for the given browser). This seems a bit better than having a big list of protocols maybe?

@Kuuuube Do you have a preference?

That looks like a cleaner solution

@Kuuuube Do you have a preference?

Didn't know that existed. Your idea sounds better.

Should I add a test case for this? I'm not sure if it's possible since the expected results are in plain JSON while the window location URL is platform-dependent.

Taking a proper look at this, I feel like this is the wrong change to make. Why modify the url after it has been sent to handlebars?

Especially considering the replace (or slice) that needs to be done here (could also make an element and pull out the attribute but that seems bad too). And what if there's another handlebar in the future that needs to use the url? Checking for {url} isn't great either.

You could throw this in before commonData is set and it will handle this case before it even gets to the handlebars:

// Make URL field blank if URL source is Yomitan
if (URL.canParse(context.url) && new URL(import.meta.url).protocol === new URL(context.url).protocol) {
    context.url = '';
}

And if you really wanted to, stopping the empty anchor tag from being sent to anki is a simple handlebars change (it wouldn't display anything in anki regardless):

{{~#*inline "url"~}}
    {{~#if (op ">" definition.url.length 0)~}}
        <a href="{{definition.url}}">{{definition.url}}</a>
    {{~/if~}}
{{~/inline~}}

Thanks for the help! I'll fix that