Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export / Share functionality does not work on Firefox #124

Open
jbunyadzade opened this issue Feb 27, 2024 · 3 comments
Open

Export / Share functionality does not work on Firefox #124

jbunyadzade opened this issue Feb 27, 2024 · 3 comments

Comments

@jbunyadzade
Copy link

jbunyadzade commented Feb 27, 2024

Describe the bug
"Export / Share" does not work when using Firefox

To Reproduce
Steps to reproduce the behavior:

  1. Using Firefox, open any request and press "Export / Share"
  2. A new tab opens with the URL https://www.graphdev.app/draft?sessionId=...
  3. It is permanently stuck on the "Exporting Request" screen

Expected behavior
The request is successfully exported

Screenshots
image

Desktop (please complete the following information):

  • OS: macOS Sonoma 14.0
  • Firefox 123.0 (64-bit)

Additional context
Exporting works just fine on Chrome, but it fails on Firefox with the message Could not establish connection. Receiving end does not exist. in console.

@warrenday
Copy link
Owner

Hey @Grulice thanks for raising this. I'll take a look at the Firefox integration. There must be some inconstancy between the browser APIs.

@warrenday
Copy link
Owner

warrenday commented May 26, 2024

Hey @jbunyadzade managed to get around to looking at this one.

The listener to pick up the message causing the error Could not establish connection. Receiving end does not exist. is not loaded as firefox is not loading background scripts in manifest v3.

We upgraded to v3 to support the latest changes in chrome. Google no longer support manifest v2.

Firefox do not support background scripts in manifest v3.

So we're stuck either supporting chrome or firefox, unless we maintain two seperate manifests, which I'd rather avoid. So I think it's probably best to wait for firefox to fully support manifest v3.

Here's a discussion on the topic:
https://stackoverflow.com/questions/75043889/manifest-v3-background-scripts-service-worker-on-firefox

mozilla/web-ext#2532

@jbunyadzade
Copy link
Author

Thank you for taking the time to research and explain, @warrenday.

I eventually decided to switch back to a Chromium-based browser for now due to issues with the developer experience, such as this one and the inability to zoom in on the extension tabs, which is a serious accessibility problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants