trotto / browser-extension Goto Github PK

I'm reaching out to kick off the process of upgrading our Chrome extension from Manifest V2 to the latest and greatest, V3. This upgrade comes with some fantastic perks: improved security, a performance boost for our users, and staying in step with Chrome's latest features. Our current manifest file sports V2, and it's time to seamlessly transition to the V3 era. If you've stumbled upon any glitches or quirks in the current setup, please share the details. Any additional information or related issues would be immensely helpful. Let's ensure our extension is at the forefront of Chrome's capabilities by embracing the Manifest V3 magic. Your collaboration on this upgrade is greatly appreciated!

As Apple does not allow webRequest on iOS, this is a hacky workaround using webNavigation.

Requires webNavigation and activeTab permissions in the manifest.

https://gist.github.com/juneoh/c027d06bf91a945364df317c34151d8b

For those who want to cook your own extension in the meantime, I found the below post to be helpful.

https://dev.to/ajones_codes/how-i-made-an-ios-15-safari-extension-to-get-rid-of-annoying-reddit-open-in-app-pop-ups-559p

Hi! I love Trotto, thanks for making it open source!

I noticed the extension supports an arbitrary domain other than trot.to, but in order to edit it one must go to the Chrome DevTools to edit the value of localStorage.trottoInstanceUrl.

I believe it'd be nice to have an options page for the extension to be able to edit that.

I would be happy to give that a shot :)

In the firefox extension, go/jira goes to a search for go jira, go/jira/ goes to the right place.

If I go to www.example.com and click on this extensions, it should tell me what go links my organisation has already created for this particular page. This would help is making sure that I can use an existing go link instead of creating a new go link for the same website.

Recently brought trotto links into our organization; and noticed an issue with users running Opera / Opera GX; the extension does not allow the user to login. Without the ability for the user to login at the extension level, links don't work for these users.

This isn't necessarily a bug, as the extension is meant for Chrome (Opera can use Chrome extensions most of the time unmodified); but nevertheless might just be a Agent check or something simple in the code.

Thank you!

Edit:

Just discovered that you can just modify your /etc/hosts file as noted in the documentation.

This ended up working just fine for me after logging in, and no need to use the extension! Leaving this 'issue' up though in case someone does get around to it; but my guess is if you're using Opera one of the options on the above linked page should be within your reach.

The Safari extension is not working for me. Clicking on the extension opens a grey box, and go links don't redirect but just open a Google Search.

This is on Safari 16.1 and macOS 13.0.