Highlightr-Plugin: Highlightr not working in +Obsidian v.15.8 (last update) + other issues

For a workaround for the broken context menu (for the Desktop app), go to your .obsidian\plugins folder or Settings -> Community Plugins -> Installed Plugins and click the folder icon:

Go into the highlightr-plugin folder and open main.js. Search for menu.showAtPosition and replace the following:

        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });

with

        const orig=menu.__proto__.sort; // Save the original function
        menu.__proto__.sort = function() {}; // Replace the sort function with a no-op function
        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });
       menu.__proto__.sort=orig; // Reset the sort function

Basically, the menu.sort function relies on menu items which this plugin just ignores. So, when it hits menu.sort, the dropdown is rebuilt and the dom (which this plugin manipulates) is reset. This change just makes the sort function a no-op.

Hello friend @gabrielcarus ! Thank you for your notes!

• Highlightr stopped working in Obsidian v.15.6 (or superior), even the shortcuts.

  • 7/22/22 - Updated Obsidian to v.15.8, when using the “Ctrl+P” shortcut it works, but the Highlightr pop up don’t.

I just released an update for Highlightr that should be much more compatible with Obsidian API. Please let me know if there are any issues with it!

• An old problem with Highlightr, that I believe you already know, is the space after the marked text. (Remove extra whitespace #39)

This should be fixed in the update, though I’m still working on a function that is more intelligent.

• A small detail, that would be nice to analyze, is that cMenu is taking a lot to load.

I’ll have to completely redo cMenu at this point. Hoping to get this done soon.

• Snippets plugin didn’t stop, but is having some basic bugs in its structure (not making possible to create new CSS Snippets through the plugin and the “hovering” when using the mouse is also bugged).

I’ve also released an update for MySnippets. You should be able to create new snippets now.

And thank you everyone for being so patient 🙏🏽!

To be clear:

(1) Select text (2) Right click (3) Choose “Highlight” (4) Nadda, nothing, zippo

Control P works fine.

menu.showAtPosition

According to this method of modification, it works for me, but it needs to be closed once and restart obsidian

Another workaround for those who don’t want to make new hotkeys:

Highlight the word, open command palette, “Highlightr” - pick a color.

This takes longer, but I have enough hotkeys as it is, so this works for me as a temporary solution.

I am so happy I found this post, I thought I was the only one with this issue.

commenting out _menu.SetUseNativeMenu(false); and restarting worked for me.

I found the “other plugins location” issue, put the patched ‘main.js’ there, and now highlighting works! The patched version of ‘highlightr/main.js’ works well for both the desktop app and the iOS app. BUT - if your vault is in iCloud - the patch needs to be made to two instances of the ‘main.js’ file - thanks to an iCloud-specific (compatibility?) issue, described below…

Issue: Obsidian and iCloud (where I have put my vault) seem to have disagreements over where things should go, so those things (highlightr code) went to both locations. This “disagreement” is consistent with what I found yesterday setting up the iOS app to use the same (iCloud-based) vault as the mac desktop. More detail below…

From the mac’s Finder: The location where if I change the files this has an effect (e.g. patch works): ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/.obsidian/plugins/highlightr-plugin Presented by Finder as:

The location where (if I change the files) this has no effect: ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Obsidian iCloud Vault 001/.obsidian/plugins/highlightr-plugin Presented by Finder as:

Incidentally, as I found when setting up a shared vault for desktop and iOS apps yesterday… Desktop recognises the first one as “root”. iOS app only recognises the second one.

I guess Obsidian have handled that (in their code) by ensuring plugin downloads get copied to both locations. In each app/device’s case, renaming (only) its particularly-located ‘.highlightr’ files causes it (only) to pop up a “failure to load” message. Pretty conclusive then.

I imagine the best fix would be for clear and separate concepts of “Obsidian Root in iCloud” and "Obsidian Vault " (within Obsidian Root). There could be more than one Obsidian Vault in iCloud. I’m guessing that there might be confusion somewhere(s) “under the hood” about these.

I’ve just installed it yesterday and was struggling for hours. wish I noticed that its no longer available much earlier

For a workaround for the broken context menu (for the Desktop app), go to your .obsidian\plugins folder or Settings -> Community Plugins -> Installed Plugins and click the folder icon:

Go into the highlightr-plugin folder and open main.js. Search for menu.showAtPosition and replace the following:

        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });

with

        const orig=menu.__proto__.sort; // Save the original function
        menu.__proto__.sort = function() {}; // Replace the sort function with a no-op function
        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });
       menu.__proto__.sort=orig; // Reset the sort function

Basically, the menu.sort function relies on menu items which this plugin just ignores. So, when it hits menu.sort, the dropdown is rebuilt and the dom (which this plugin manipulates) is reset. This change just makes the sort function a no-op.

Bravo! It works! Thanks!

For a workaround for the broken context menu (for the Desktop app), go to your .obsidian\plugins folder or Settings -> Community Plugins -> Installed Plugins and click the folder icon:

Go into the highlightr-plugin folder and open main.js. Search for menu.showAtPosition and replace the following:

        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });

with

        const orig=menu.__proto__.sort; // Save the original function
        menu.__proto__.sort = function() {}; // Replace the sort function with a no-op function
        menu.showAtPosition({
            x: coords.right + 25,
            y: coords.top + 20,
        });
       menu.__proto__.sort=orig; // Reset the sort function

Basically, the menu.sort function relies on menu items which this plugin just ignores. So, when it hits menu.sort, the dropdown is rebuilt and the dom (which this plugin manipulates) is reset. This change just makes the sort function a no-op.

This worked for me! I installed right now the plugin.

@chetachiezikeuzor could we please get a fix? thanks

Its not working for me any more with obsidian 15.6

FYI, I found a partial work a round – by setting hotkeys for the various colors, I can now again add highlights. But setting a hot key to open the highlightr doesn’t work – it just doesn’t respond, and doesn’t display the choice of colors. Also, to unlighlight, right-clicking on the highlight doesn’t bring up the unhighlight menu, but raises a note that “focus must be in editor” (I’m using live preview). Clicking on the highlight puts it in edit mode, then right-clicking brings up unhighlight option, and clicking then unhighlights. Hope this may help in troubleshooting. Really like this plugin when it was working normally.

See my post #41