This would help Pale Moon users to instantly launch non-Pale Moon-friendly websites, in a user-set browser. Features:
1. User-specified list of hosts/domains. Pale Moon would directly launch these in a new external browser tab, no questions asked. External links, Pale Moon bookmarks, address bar entries etc. Everything that goes through Pale Moon, really.
2. User-set list of installed browsers: specify either one external browser (the "Open With" default) or more than one. Browsers no.2, 3 etc. could be launched via context-menu and keyboard shortcut. The "default" browser is always launched in all cases with no user interaction.
Why not use currently available extensions that already do this?
a) Tighter Pale Moon integration - no 3rd-party abandoned extensions required.
b) Increased functionality: User website list, leads to further automation and customisation.
c) Optional, extended functionality: assign specific hosts to specific browsers.
example 1: youtube.com/vimeo.com to MPC-HC (not a browser, but plays online videos the best way possible).
example 2: google.com to Brave etc.
Heck, we could even make an official "Open In Pale Moon" WebExtension as a "companion feature" to further promote PM. Actually there is one, but it's limited to sending a single tab to Pale Moon (no multiple tabs). And it's not official.
"Open in another browser" as a core feature may sound bizarre (or worse), but we all know that in these times, use of a second or even third browser is almost unavoidable for many (most?) of us.
(inspired by linuxrocks123's Wide-Ranging Web Compatibility Workaround thread)
"Open In/With" functionality integration
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
- back2themoon
- Moon Magic practitioner
- Posts: 2641
- Joined: 2012-08-19, 20:32
Re: "Open In/With" functionality integration
No.
This is exactly what extensions are for.
You can't just foist this work on to the Pale Moon developers because boo-hoo extensions take work and potentially get abandoned.
This is exactly what extensions are for.
You can't just foist this work on to the Pale Moon developers because boo-hoo extensions take work and potentially get abandoned.
- back2themoon
- Moon Magic practitioner
- Posts: 2641
- Joined: 2012-08-19, 20:32
Re: "Open In/With" functionality integration
As mentioned, extensions already exist. Abandoned or otherwise.
Consider this an advanced user-agent override alternative or dare I say, replacement.
A more drastic, in-built way to deal with web compatibility issues. Not a solution of course, but in the long run users may complain less, leaving more time (and peace of mind) to the developers to deal with the actual web compatibility issues.
Consider this an advanced user-agent override alternative or dare I say, replacement.
A more drastic, in-built way to deal with web compatibility issues. Not a solution of course, but in the long run users may complain less, leaving more time (and peace of mind) to the developers to deal with the actual web compatibility issues.
Re: "Open In/With" functionality integration
I don't really see how building in a workaround for web compatibility issues by hard baking in an extension (which one if there are multiple...?) or writing something entirely new is not exactly the wrong direction of quick hacks being preferred over actual solutions.
"The world will not be destroyed by those who do evil, but by those who watch them without doing anything." - Albert Einstein
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: "Open In/With" functionality integration
Not automatic, but convenient and quick to use (being a dedicated mouse pusher and clicker who loves using pop-op menus a lot) I am having success using Open With Edge, IE, Chrome, and More from:
https://addons.palemoon.org/addon/openwithieedge/
It works on websites and in the Pale Moon bookmarks and gives me a lot of flexibility with how a link is opened.
https://addons.palemoon.org/addon/openwithieedge/
It works on websites and in the Pale Moon bookmarks and gives me a lot of flexibility with how a link is opened.
Laptop 1: Windows 10 64-bit, i7 @ 2.80GHz, 16GB, NVIDIA GeForce MX450.
Laptop 2: Windows 10 32-bit, Atom Z3735F @ 1.33GHz, 2GB, Intel HD Graphics.
Laptop 3: Linux Mint 20.3 64-bit, i5 @ 2.5GHz, 8GB, Intel HD Graphics 620.
Laptop 2: Windows 10 32-bit, Atom Z3735F @ 1.33GHz, 2GB, Intel HD Graphics.
Laptop 3: Linux Mint 20.3 64-bit, i5 @ 2.5GHz, 8GB, Intel HD Graphics 620.
- back2themoon
- Moon Magic practitioner
- Posts: 2641
- Joined: 2012-08-19, 20:32
Re: "Open In/With" functionality integration
Some clarifications: I think you know I know this requires work and time you don't have. Consider it an idea, or food for thought. Certainly not a request, demand etc.
This is not about hard baking in a particular extension. Actually, I have not found the main intended functionality in any extension: user-set list to automatically open in specific, external browser(s). They usually offer the ability to right-click a link, or click a button to open current page in another application. Not bad at all, as described by suzyne and I use it myself.
This new feature is indeed a "hack". You could say it is the ultimate, 100% working hack. Aimed at users that:
a) Still want things handled and configured by Pale Moon.
b) Often click on widespread links, accidentally or not (Facebook, YouTube etc.) that they'd rather have directly opened on another browser instead. In an OS that has Pale Moon set as default browser, links found on external applications would be taken care of, too (Email clients, messengers and many more).
c) Spot a website that does not work as they want, and do not wish to fight with the various workarounds like user-agent overrides, Modify HTTP Response filters, userscripts or other hacks which may or may not work, or may only partially work until they break again.
They'll add the website to the list instead, and it'll automagically open to their designated application. A twisted, but still valid Your Browser, Your Way™ if you will. Advanced users would still be able to tackle issues on Pale Moon alone, with the help of the forum.
Now, I understand the implications of "officially" directing users to other browsers. It is a problem. But it's a well-known one, and spotlighting it could be an opportunity to turn it around, overly optimistic or ambitious as it may sound:
a) Still prompt the user the describe the issue to the forum, before adding a website to the "blacklist".
b) Keep educating users about Net neutrality problems that affect Pale Moon and the Internet in general, with additional links to specific articles etc.
c) Counter-attack with a WebExtension: "Open websites in your favourite, real browser" etc. (I know, who's going to create this - it actually requires a workaround/external application itself to launch another browser
- WebExtensions alone are not up to this task)
Actually, I'm getting myself some coding skills and hope to be able to contribute something more than thoughts. But this will take months, or more. This is about a different approach to web compatibility issues, fuelled by the incredibly complex workaround of the thread mentioned in the first post.
Not easy to find online any more. Not sure if it's ok to attach it here, but it's available in the Classic Add-ons Archive (screenshot below):
This is not about hard baking in a particular extension. Actually, I have not found the main intended functionality in any extension: user-set list to automatically open in specific, external browser(s). They usually offer the ability to right-click a link, or click a button to open current page in another application. Not bad at all, as described by suzyne and I use it myself.
This new feature is indeed a "hack". You could say it is the ultimate, 100% working hack. Aimed at users that:
a) Still want things handled and configured by Pale Moon.
b) Often click on widespread links, accidentally or not (Facebook, YouTube etc.) that they'd rather have directly opened on another browser instead. In an OS that has Pale Moon set as default browser, links found on external applications would be taken care of, too (Email clients, messengers and many more).
c) Spot a website that does not work as they want, and do not wish to fight with the various workarounds like user-agent overrides, Modify HTTP Response filters, userscripts or other hacks which may or may not work, or may only partially work until they break again.
They'll add the website to the list instead, and it'll automagically open to their designated application. A twisted, but still valid Your Browser, Your Way™ if you will. Advanced users would still be able to tackle issues on Pale Moon alone, with the help of the forum.
Now, I understand the implications of "officially" directing users to other browsers. It is a problem. But it's a well-known one, and spotlighting it could be an opportunity to turn it around, overly optimistic or ambitious as it may sound:
a) Still prompt the user the describe the issue to the forum, before adding a website to the "blacklist".
b) Keep educating users about Net neutrality problems that affect Pale Moon and the Internet in general, with additional links to specific articles etc.
c) Counter-attack with a WebExtension: "Open websites in your favourite, real browser" etc. (I know, who's going to create this - it actually requires a workaround/external application itself to launch another browser

Actually, I'm getting myself some coding skills and hope to be able to contribute something more than thoughts. But this will take months, or more. This is about a different approach to web compatibility issues, fuelled by the incredibly complex workaround of the thread mentioned in the first post.
Thanks. I've tried it but remember preferring "Open With". It is more customisable than the one we have in the Pale Moon Add-ons Site.
Not easy to find online any more. Not sure if it's ok to attach it here, but it's available in the Classic Add-ons Archive (screenshot below):