2 ms·

Would be great to add tampermonkey/greasemonkey support. Opened a ticket for it

• arkadiyt 7y ago
  The current implementation uses the WebExtension apis to perform an _internal_ redirect. When you navigate to a Zoom meeting, before the browser opens a connection or sends a single network packet, the extension rewrites the url to navigate to their web client. On the other hand tampermonkey/greasemonkey are content scripts that get injected into loaded pages. An implementation here would look like: the user navigates to a Zoom meeting, they load the entire page, and then a script gets injected to perform a `window.location` redirect. This will be slower and depending on the timing of events you may even still get the Zoom file download prompt. So I don't think tampermonkey/greasemonkey is a good fit here.
  • sjnair96 7y ago
    Tampermonkey, I believe, can also intercept HTTP requests. Maybe that's sufficient/necessary for redirecting to another client.
    • capableweb 7y ago
      I can't find any information around this except an open issue (https://github.com/Tampermonkey/tampermonkey/issues/397 https://github.com/Tampermonkey/tampermonkey/issues/397), you got any links? As I understand issue linked above, they want to support it but currently does not, in official releases. What's supported is catching all requests in a page, but that's after the contentscript has been applied to the page, which means what arkadiyt wrote would still be accurate.