Replies: 9 comments 6 replies
-
|
The new website is now available at https://pwasforfirefox.filips.si/. Please check it out and share any feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome. The site looks neat. |
Beta Was this translation helpful? Give feedback.
-
|
I've built Mercury on mac. It's a fork of Firefox with several enhancements https://github.com/Alex313031/Mercury/releases and I want to use it for handling PWA installations, I followed the instructions but the extension keeps wanting Firefox.app instead. Sorry if I'm writing in the wrong place. |
Beta Was this translation helpful? Give feedback.
-
|
Do you want to use Mercury as your main/default browser, or as browser where PWAs will be running? |
Beta Was this translation helpful? Give feedback.
-
|
The only thing keeping me from using it as my main browser is that I have my PWA’s with Thorium and I can not use Mercury to create my PWA’s, I tried and ended up with Firefox.app inside the folder where it downloads the copy for the PWA’s, I tried changing that around to make it use the copy of Mercury I have in my Apps system folder but then it made the wizard go back to the step where you have to make the setup for it, so I assume it didn’t like it or it checks on the version and does as if there was no usable version. I tried putting Mercury.app there, I tried doing the ln -sf, I tried putting the executable, nothing worked. So I guess it doesn’t likes Mercury and also I’m using tip-of-tree v.124, I build myself with the help of Alex313031. You should give his great project a chance to be able to use your great extension.
… On Jan 26, 2024, at 6:37 AM, Filip Š ***@***.***> wrote:
Do you want to use Mercury as your main/default browser, or as browser where PWAs will be running?
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXKDRXHQP26P2BVVIEDYQOBQDAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DENJVGU2DA>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
These are a few things you need to make sure are set up correctly:
This is what the program checks to see if the runtime is installed. If you already have everything set up according to this, something else might be the problem, but I don't know what exactly. |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate your time and consideration. You’re being very kind. Got a couple questions:
Runtime , is it just the Mercury.app, symlinked?
App bundle, are we talking about two different things? Isn’t the same as the runtime? Also symlinked to the Mercury.app I’ve got in /Applications?
The information is very insightful, I’m very exited about being able to get Mercury PWA’s working!!!
… On Jan 29, 2024, at 5:09 PM, Filip Š ***@***.***> wrote:
These are a few things you need to make sure are set up correctly:
The runtime should be installed in $HOME/Library/Application Support/firefoxpwa/runtime/.
The app bundle should be named Firefox.app, so $HOME/Library/Application Support/firefoxpwa/runtime/Firefox.app/.
Inside the app bundle, there should be executable file Contents/MacOS/firefox (you should symlink it to the Mercury executable if it's different).
Inside the app bundle, there should be Contents/Resources/application.ini INI file. If it doesn't exist, you can put something like this inside it:
[App]
Vendor=Mozilla
Name=Firefox
RemotingName=firefox
Version=121.0
This is what the program checks to see if the runtime is installed. If you already have everything set up according to this, something else might be the problem, but I don't know what exactly.
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXJD3EGOTA6W2R7ZM3DYRAF2PAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DEOJQHE4TC>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
It’s running! But I get the following error at trying to install zoho workplace.
Thanks for your hard work!

… On Jan 29, 2024, at 5:09 PM, Filip Š ***@***.***> wrote:
These are a few things you need to make sure are set up correctly:
The runtime should be installed in $HOME/Library/Application Support/firefoxpwa/runtime/.
The app bundle should be named Firefox.app, so $HOME/Library/Application Support/firefoxpwa/runtime/Firefox.app/.
Inside the app bundle, there should be executable file Contents/MacOS/firefox (you should symlink it to the Mercury executable if it's different).
Inside the app bundle, there should be Contents/Resources/application.ini INI file. If it doesn't exist, you can put something like this inside it:
[App]
Vendor=Mozilla
Name=Firefox
RemotingName=firefox
Version=121.0
This is what the program checks to see if the runtime is installed. If you already have everything set up according to this, something else might be the problem, but I don't know what exactly.
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXJD3EGOTA6W2R7ZM3DYRAF2PAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DEOJQHE4TC>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
I think symlinks don't work correctly, so it's probably better if you just copy it.
The app bundle is specifically the The directory structure should then be something like:
Did you try to attach some screenshot? Because unfortunetely it seems it didn't work. You will probably need to attach it directly from GitHub website. |
Beta Was this translation helpful? Give feedback.
-
|
It’s working!!!

Thank you. Great project.
I’ll let Alex313031 know about the wonders of using Mercury with PWAs.
… On Jan 29, 2024, at 5:09 PM, Filip Š ***@***.***> wrote:
These are a few things you need to make sure are set up correctly:
The runtime should be installed in $HOME/Library/Application Support/firefoxpwa/runtime/.
The app bundle should be named Firefox.app, so $HOME/Library/Application Support/firefoxpwa/runtime/Firefox.app/.
Inside the app bundle, there should be executable file Contents/MacOS/firefox (you should symlink it to the Mercury executable if it's different).
Inside the app bundle, there should be Contents/Resources/application.ini INI file. If it doesn't exist, you can put something like this inside it:
[App]
Vendor=Mozilla
Name=Firefox
RemotingName=firefox
Version=121.0
This is what the program checks to see if the runtime is installed. If you already have everything set up according to this, something else might be the problem, but I don't know what exactly.
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXJD3EGOTA6W2R7ZM3DYRAF2PAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DEOJQHE4TC>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
There is a rather funny thing going on, now, instead of Mercury on the menu bar, it says WhatsApp, or Zoho Mail.
… On Feb 1, 2024, at 7:37 AM, Filip Š ***@***.***> wrote:
Runtime , is it just the Mercury.app, symlinked?
I think symlinks don't work correctly, so it's probably better if you just copy it.
App bundle, are we talking about two different things? Isn’t the same as the runtime?
The app bundle is specifically the Mercury.app directory (that appears as a Mercury app on macOS). So, this directory/bundle/app should be named Firefox.app and copied into $HOME/Library/Application Support/firefoxpwa/runtime/.
The directory structure should then be something like:
/Users/user/Library/Application Support/firefoxpwa/runtime <--- The base runtime directory
/Users/user/Library/Application Support/firefoxpwa/runtime/Firefox.app <--- The app bundle that you copy and rename from Mercury
...
/Users/user/Library/Application Support/firefoxpwa/runtime/Firefox.app/Contents <--- Other stuff inside the app bundle
...
/Users/user/Library/Application Support/firefoxpwa/runtime/Firefox.app/Contents/MacOS/firefox <--- Make sure it's named firefox
/Users/user/Library/Application Support/firefoxpwa/runtime/Firefox.app/Contents/Resources/application.ini <-- Make sure this one exists and has a valid version key
...
But I get the following error at trying to install zoho workplace.
Did you try to attach some screenshot? Because unfortunetely it seems it didn't work. You will probably need to attach it directly from GitHub website.
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXLX2LBDVFVSQD2GG3DYRN46NAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMZTHE3TO>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Does it say that in the PWA or in the main browser? If it's in PWA, it's intentional, but if it's in the main browser, it might be because you were using symlinks, so the app name was overwritten. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, oh, yes, when it’s the app is great to have its name changed to the intended app I’m on, I know that, but whenever I’m on the main app, it reads the last I used I guess? So it might be what you said, since I’m using symlinks as suggested in your extension, “ln -sf…” so… the only way around is to put a full app and modify it as described, correct?
… On Feb 4, 2024, at 6:09 AM, Filip Š ***@***.***> wrote:
Does it say that in the PWA or in the main browser? If it's in PWA, it's intentional, but if it's in the main browser, it might be because you were using symlinks, so the app name was overwritten.
—
Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXJD4UK7CR2SMXTBRVDYR5M6BAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGNJZGY4DE>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, on macOS symlinks won't work properly, because PWAsForFirefox changes the app name (and a few other properties) inside You could probably get around this by symlinking just specific files and directories that are not affected by this, but unfortunately, I don't know which exactly are these files, so it's probably the easiest if you just fully copy the runtime. In the future, there might be a more automated way to do these symlinks, but I'm not sure yet. |
Beta Was this translation helpful? Give feedback.
-
|
I made a video and although it was only 17mb it didn’t allow to go saying it was too long, well… I’ll just leave it as it is and when I compile it again I will then make the change and put a full copy in there because since I compiled it myself I don’t have the DMG anymore, I cleaned up everything, no biggie, I love your extension, I use it every day now and won’t go back to Thorium anymore since I like my copy of Mercury compiled with LTO so much, it is one of the best mods I’have ever used, and that along your extension gave me limitless possibilities. Hope I can collaborate more than just words in the future though. I’m trying now to build with also PGO but it seems almost imposible just yet.
… Begin forwarded message:
From: Néstor Espinoza ***@***.***>
Subject: Re: [filips123/PWAsForFirefox] A new documentation website is in progress, help us improve it (Discussion #335)
Date: February 4, 2024 at 11:37:59 AM GMT-4
To: filips123/PWAsForFirefox ***@***.***>
Yes ! It’s exactly what you’re saying. It’s not annoying since the functionality doesn’t seem to be affected, it’s only cosmetic. Nevertheless, it would be nice to be able to have it actually display correctly, if not possible and the only solution is to not use shortcusts and instead put a full copy of Mercury in the resources folder then I think I will just leave it like that and just laugh at it really loud. Hehe...
> On Feb 4, 2024, at 6:09 AM, Filip Š ***@***.***> wrote:
>
>
> Does it say that in the PWA or in the main browser? If it's in PWA, it's intentional, but if it's in the main browser, it might be because you were using symlinks, so the app name was overwritten.
>
> —
> Reply to this email directly, view it on GitHub <#335 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZABHXJD4UK7CR2SMXTBRVDYR5M6BAVCNFSM6AAAAAAX3RNZZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGNJZGY4DE>.
> You are receiving this because you commented.
>
|
Beta Was this translation helpful? Give feedback.
-
After more than a year since originally mentioned in #116, I finally have a work-in-progress documentation website. Once it becomes ready, it will replace the wiki and serve as a main documentation source for this project.
About the new documentation
The website source is currently available in the
wip-documentationbranch in thedocsdirectory. It's built with Material for MkDocs and will be deployed to GitHub Pages or ReadTheDocs (I haven't decided yet) once ready. The reason for using the website over existing wiki is because this will allow better search, additional Markdown features, and enable PR for improvements from the community.Unfortunately, I won't have much time for around two months, so I can't promise when it will be ready. Most things are finished, but there are still some things that I would like to add. You can search for "TODO" to find them.
How can you help
You can preview the documentation yourself by cloning the
wip-documentationbranch, installing dependencies (pip install -r requirements.txt) and building the website (mkdocs serve).Please check the documentation, share what you think about it and what should still be improved. Do you like the new documentation structure? What do you think is still missing?
Please use this discussion thread for your suggestions and other discussions. You can also submit PRs to the correct branch for direct improvements.
Notes
Things to mention in frequently asked questions or troubleshooting guides:
If chrome modifications are not loaded, temporarily enable "always patch runtime and profile". This might happen if profile patches are applied but runtime patches aren't, for example after runtime reinstallation. I will also check if there is any good way to fix this.
When creating a new profile template, make sure the source browser is closed before copying the directory to a template. This is related to the next thing on this list.
If the profile template cannot be copied, make sure it has the correct permissions and remove any lock files ([Issue fixed, patch needed] Can't create a new PWA using template #337). I don't think I can remove those files automatically if they can't even be copied, so users have to remove them manually. However, this should not happen often.
Explain problems related to sandboxed browsers in more detail. For example, Extension cannot detect the native connector on Ubuntu 23.04 #325 (comment).
Beta Was this translation helpful? Give feedback.
All reactions