Clicked links in Gmail, other apps don't work

[neilio]

I've got an issue where clicking on a link in Gmail causes an error message to appear about popups being blocked. Is there a workaround or setting to whitelist or enable links like this to work?

Love the app, and love the fact that I managed to compile it for Apple Silicon with zero issues. It's crazy fast!

[kofigumbs]

Ah yes, Gmail isn't quite honest with the way it presents links, so I documented a workaround using Custom JS:

• The fix
• More specifics about the root cause

I'm also glad to hear that the project builds on Apple Silicon! I'm a bit behind with maintenance on this project, but it's good to know folks can build from source until I get to repackage/distribute.

[neilio]

Thanks for the quick reply! Unfortunately, the code doesn't seem to work - I still get the same error.

This is my config: https://gist.github.com/neilio/c6825f1a120e54586a8d73cf9b5b2a36

[kofigumbs]

Oh sorry, I should have verified! It looks like the issue is that the hashchange event doesn't reliably fire after new links are inserted into the page. If you make the following change to your script, it should work:

-  window.addEventListener('hashchange', query);
+  setInterval(query, 400); // wait time between DOM queries, in milliseconds

I'll re-open this issue to remind myself to update the example and research whether there's a smarter approach.

[kofigumbs]

Oh also, you'll want the script in all of the GSuite apps. Not sure about the other sites in your config--are you having issues with those as well?

[neilio]

Hm! I made that change but still can't seem to get links to work - I get the same alert error. My config file

[kofigumbs]

Oh I just noticed that your object field is named customJS instead of customJs (note the lowercase "s"). Could you try lowercasing the "s"?

If that doesn't change anything, could you toss an alert("hello") at the top of the script, just to make certain the script is running?

[neilio]

Ah, that was it! Thanks.

[kofigumbs]

Nice! Sorry that there was no feedback for that kinda typo. Just made a separate issue to fix that: #48.