| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
| |
This reverts commit d868805a1082c2682379452314244bc02b425a32.
|
| |
|
|
| |
This reverts commit 756cfe85af63d4899182bc678af6d18d77a62351.
|
| |
|
|
|
|
| |
versions.""
This reverts commit fd6c4911ce4c23801c03118573db8193558d49b0.
|
| |
|
|
|
|
| |
version.""
This reverts commit 8eb559895d0cd5640c05903513c9c5f310fb5431.
|
| |
|
|
|
|
| |
GetNativePath"
This reverts commit 097fa969802f76530384926e8ef1f56777be3783.
|
| | |
|
| |
|
|
| |
Depending on context, various solutions were used.
|
| |
|
|
| |
This reverts commit 1510c3b1865125f65ff0087647323cc07b19631c.
|
| |
|
|
| |
This reverts commit f8adfe77e6fa5cfc34f5fcaa2acbc859b3f96a23.
|
| |
|
|
| |
See previous comment.
|
| |
|
|
|
| |
Instead of mapping lossily to a "native" codepage we now convert to UTF-8
on Windows, which should be fully supported on all supported (NT6+) versions.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
file paths on Linux.
OS.File already only supports UTF-8 paths on non-Windows systems, so this change
makes our different ways of accessing file paths consistent with each other.
This should prevent unexpected crashes in glibc that expect UTF-8.
This resolves %1772.
|
| |
|
|
| |
files from /xpcom
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Since these are just interpreted comments, there's 0 impact on actual code.
This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are
a few others scattered around which will be removed manually in a second part.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Compared with what Pale Moon had for Solaris originally, this is mostly the same zero point I started patching from, but I've made the following changes here after reviewing all this initial code I never looked at closely before.
1. In package-manifest.in for both Basilisk and Pale Moon, I've made the SPARC code for libfreebl not interefere with the x86 code, use the proper build flags, and also updated it to allow a SPARC64 build which is more likely to be used than the 32-bit SPARC code we had there.
2. See Mozilla bug %832272 and the old rules.mk patch from around Firefox 30 in oracle/solaris-userland. I believe they screwed up NSINSTALL on Solaris when they were trying to streamline the NSS buildsystem, because they started having unexplained issues with it around that time after Firefox 22 that they never properly resolved until Mozilla began building NSS with gyp files. I'm actually not even sure how relevant the thing they broke actually is to Solaris at this point, bug 665509 is so old it predates Firefox itself and goes back to the Mozilla suite days. I believe $(INSTALL) -t was wrong, and they meant $(NSINSTALL) -t because that makes more sense and is closer to what was there originally. It's what they have for WINNT, and it's possible a fix more like that could serve for Solaris as well. Alternatively, we could get rid of all these half-broken Makefiles and start building NSS with gyp files like Mozilla did.
3. I've completely cut out support for the Sun compiler and taken into account the reality that everyone builds Firefox (and therefore its forks) with GCC now on Solaris. This alone helped clean up a lot of the uglier parts of the code.
4. I've updated all remaining SOLARIS build flags to the newer XP_SOLARIS, because the SOLARIS flag is no longer set when building Solaris.
5. I've confirmed the workaround in gtxFontconfigFonts.cpp is no longer necessary. The Solaris people got impatient about implementing a half-baked patch for a fontconfig feature that wasn't ready yet back in 2009, and somehow convinced Mozilla to patch their software to work around it when really they should have just fixed or removed their broken fontconfig patch. The feature they wanted has since been implemented properly, and no version of Solaris still uses the broken patch that required this fix. If anyone had ever properly audited this code, it would have been removed a long time ago.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rationale: This was a Mozilla oversight and/or error.
This change has caused harm and is causing users to switch back to
Chrome, Safari or Edge for their WebStart needs.
JNLP is not an executable and should not be treated as such. JNLP should
be treated the same as any (e.g. Word) document and allowed to be opened
with the designated program.
A JNLP file will not cause execution on a system unless it has a valid
signature, and the user explicitly authorizes the launching based on
information provided by the signature. Moreover, there will even be a
check by the Java environment to see if the Java runtime (if there is
one) is current, and prompt the user to update if required.
This reverts commit 21495c58976e3cbbfe54d2e54d1fd67e36dff2a6 and
modifies ApplicationReputation.cpp to keep the list in sync (was a
discrepancy before).
|
| | |
|
| |
|
|
| |
Issue mcp-graveyard/UXP%186
|
| | |
|
| |
|
|
| |
This reverts commit 411919cca7a3795d08ec3cd24efa0167683a80fb.
|
| | |
|
| |
|
|
| |
extensions. r=Gijs, a=RyanVM
|
| | |
|
| | |
|
| |\
| |
| | |
Fix: no escape single quote in location.hash
|
| | | |
|
| | |
| |
| |
| | |
Tag mcp-graveyard/UXP%22.
|
| |/
|
|
|
| |
The SHGetKnownFolderPath function declaration is exposed since [85edb1c711f7816ed1a30edd07b37d314fac216a] so we no longer need to GetProcAddress("SHGetKnownFolderPath") and we can call it directly.
Also remove a redundant %include <shlobj.h>.
|
| |
|
