summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* [OTS] Backport some upstream OTS commits.Moonchild2021-02-24-22/+209
|
* [MFBT] Update lz4 to 1.9.3Moonchild2021-02-24-909/+2233
|
* Issue #457 - Remove duplicate PKCS11 definitionsMoonchild2021-02-24-4/+0
|
* [security] Hold mutex when accessing TSI fields.Moonchild2021-02-24-0/+6
|
* [DOM] Don't reveal error details for CORS-cross-origin decoding errors.Moonchild2021-02-24-1/+5
|
* [html parser] Check for integer overflow when computing new buffer sizes.Moonchild2021-02-24-13/+36
|
* [dom] Update noscript serialization to the changed spec.Moonchild2021-02-24-4/+4
| | | | Make <noscript> escaping conditional on whether scripting is enabled.
* Issue #1722 - Update about:licenseMoonchild2021-02-21-391/+128
| | | | | | | Mostly making parts conditional and removing blocks that are no longer applicable, and a few minor edits otherwise to update links and text. Resolves #1722
* [widget] Require user interaction when picking files or folders v2Moonchild2021-02-21-11/+36
| | | | | Now with extra sauce to make it work cross-platform and cross-versions and for HTML input elements only.
* Issue #1743 - Update CK_GCM_PARAMS use for PKCS11 v3.0 in WebCryptoTaskMoonchild2021-02-17-0/+1
|
* Issue #1688 - Add flood guard to state change logic.Moonchild2021-02-16-0/+56
|
* [widget] Require user interaction when picking files or folders.Moonchild2021-02-15-2/+2
|
* Issue #1741 - Follow-up: Remove superfluous prefobserverMoonchild2021-02-15-1/+0
| | | | This one is no longer necessary (and incorrect) after the changes made in #1684
* Issue #1741 - Add missing prefobserver for general.useragent.* prefsMoonchild2021-02-14-0/+1
| | | | Resolves #1741
* [js] Add XMMRegName for invalid_xmmMoonchild2021-02-14-0/+1
|
* Issue #1739 - Implement numeric separators.Moonchild2021-02-13-49/+194
| | | | Resolves #1739
* Issue #1738 - Follow-up: Update comment (no code changes)Moonchild2021-02-12-3/+3
|
* Issue #1738 - Part 2: Implement well-formed JSON stringifyMoonchild2021-02-11-14/+68
| | | | | This implements the ES2019 spec for JSON stringification, including lower-casing, properly escaping lone surrogates, etc.
* Issue #1738 - Part 1: Improve performance of JSON stringifyMoonchild2021-02-11-90/+111
| | | | | | - Use some pointer voodoo and instead of stringbuffer append() - Use a lookup table instead of char comparisons for chr < 256 - Stop using a Hashtable/MovableCellHasher for JSON CycleDetector
* Update tzdata to 2021aMoonchild2021-02-10-1283/+1324
| | | | Because people are apparently never satisfied with the time zones on the planet!
* Merge pull request 'Support for latest stable FreeBSD (12.2)' (#1736) from ↵Moonchild2021-02-08-2/+13
|\ | | | | | | | | | | OlCe1/UXP:FreeBSD-support-update into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1736
| * Issue #1699 - Follow-up: mozjemalloc: Fix build by excluding some irrelevant ↵Olivier Certner2021-02-05-1/+1
| | | | | | | | | | | | | | | | init_lock code This had been initially dealt with in issue #1699's commits, but one of them was in the end reverted, which caused this problem (this change should have been done there).
| * Issue #1730 - Part 2: harfbuzz: Remove some useless define causing a build errorOlivier Certner2021-02-05-0/+2
| | | | | | | | | | | | | | | | | | | | Defining _POSIX_C_SOURCE to 199309L on FreeBSD causes compile errors, because of an obscure interaction between system wrappers and libc++ headers. The source doesn't seem to need it at all, which tests confirm. I bet that this is not needed either on other modern systems (even those based on glibc), and that the define could probably be entirely removed. Not trying it because I can't test it myself.
| * Issue #1730 - Part 1: Interpose malloc even on RTLD_DEEPBIND presenceOlivier Certner2021-02-05-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New FreeBSD versions have introduced RTLD_DEEPBIND (see dlopen(3)), which triggers a provoked build error to be on the "safe" side. Indeed, improper use of RTLD_DEEPBIND could cause malloc interposing not to work on specific libraries. This would happen for libraries that provide their own malloc/free and exchange pointers with other libraries or the main program, one allocating an area and another one deallocating it. It seems it happened for glibc, which is not a concern on FreeBSD, and for the Flash Player (not a concern either, there is no native Flash Player). Moreover, there is only a single reference to RTLD_DEEPBIND in the whole platform currently, namely in the WebRTC code, but the corresponding code chunk is compiled-in only on Linux (and this library doesn't seem to redefine malloc functions anyway). So I don't see how a problem could happen. Additionally, Pale Moon, which is my focus, doesn't use WebRTC. Corresponding Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=493541
| * Issue #1729 - Support building/linking against libc++ 9+Olivier Certner2021-02-05-0/+8
| | | | | | | | | | | | | | | | | | | | | | Including <cstdlib> must never trigger inclusion of "mozalloc.h", because the first thing this one does is precisely to include <cstdlib>. It is now the case that, in libc++ 9 and beyond, <cstdlib> includes <math.h> which then tries to include <type_traits>, which the STL wrapper intercepts, trying to load "mozalloc.h". Same problem happens with <limits>. Fix pulled from: https://bugzilla.mozilla.org/show_bug.cgi?id=1594027.
* | Issue #1737 - Disable AV1 by default.Moonchild2021-02-07-1/+1
| | | | | | | | | | Our current implementation has consistent playback issues; this needs to be addressed before the codec can be enabled by default.
* | [angle] Cherry-pick compressed tex depth stride fix.Moonchild2021-02-05-3/+12
|/
* Issue #1732 - Implement JSON superset proposal.Moonchild2021-02-05-89/+44
| | | | | | | | This change makes unicode line and paragraph separators allowed in JS strings, removing the only quirk of the JS string definition that made JSON not a valid subset of JS. Resolves #1732
* Issue #1726 - Add verification test for string.replaceAll()Moonchild2021-02-04-0/+63
|
* Merge pull request 'Implement String.replaceAll()' (#1728) from ↵Moonchild2021-02-04-25/+478
|\ | | | | | | | | | | meatloaf/UXP:string_replaceAll into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1728
| * Issue #1726 - Implement String.replaceAll()meatloaf2021-02-04-25/+478
| | | | | | | | | | This also implements IsRegExp, as this demands it. Ported from https://bugzilla.mozilla.org/show_bug.cgi?id=1540021
* | Issue #439 - Remove web-platform tests from the tree.Moonchild2021-02-04-1479801/+0
|/ | | | | This removes a total of 23,936 files we would never use nor have the capacity to properly maintain or keep up-to-date.
* Issue #1515 - Add null check to nsCSSFrameConstructor::IsValidSiblingMoonchild2021-02-03-0/+5
| | | | | | With the changes to layout for WebComponents, it is now apparently possible to pass in null for frame tree items to this function, which would cause a null deref crash if not checked.
* Fix CRLF line endings in npapi.hMoonchild2021-01-30-6/+6
|
* Issue #1720 - Remove explicit header inclusion from npapi.hMoonchild2021-01-30-1/+0
| | | | | | This should allow the header to be used outside of the UXP tree for compiling plugins etc. Resolves #1720
* [js] Remove unused promise selfhosting functions.Moonchild2021-01-30-107/+0
| | | | | These are leftovers from when promises were fully self-hosted and could cause confusion if left in place.
* Merge pull request 'Issue #1723 - Fix Linux build bustage in ↵Moonchild2021-01-30-3/+2
|\ | | | | | | | | | | HTMLMenuItemElement.cpp' (#1724) from trav90/UXP:1723-fix into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1724
| * Issue #1723 - Fix Linux build bustage in HTMLMenuItemElement.cpptrav902021-01-29-3/+2
|/
* [network] Hold mutex when accessing mSecurityInfo.RC_20210128Moonchild2021-01-27-3/+12
|
* [DOM] Store weak pointer to next parents.Moonchild2021-01-26-4/+13
|
* [DOM] Try to avoid slow shrinking GC during sync callsMoonchild2021-01-26-2/+2
|
* [webaudio] Fix up ReverbInputBuffer's writeIndex.Moonchild2021-01-26-11/+13
|
* [WebRTC] Improve SDP parser error handling.Moonchild2021-01-26-3/+3
|
* [js] Add AutoEnterOOMUnsafeRegion to JS_TransplantObject.Moonchild2021-01-26-4/+10
| | | | | | Transplanting objects is inherently oom-unsafe, so add `AutoEnterOOMUnsafeRegion` to `JS_TransplantObject()` and annotate crashes accordingly if they do happen.
* Fix rooting hazard in ImageBitmap::CreateInternal by avoiding movable data.Moonchild2021-01-26-2/+6
|
* [layout, XUL] Avoid accessing invalidated frame.Moonchild2021-01-26-1/+6
|
* Merge branch 'presentation-cleanup'Matt A. Tobin2021-01-25-134/+6
|\
| * Issue #1390 - Clean up presentation api leftoversMatt A. Tobin2021-01-25-134/+6
| |
* | Issue #1719 - Make <menuitem> pref-controlled and disable by default.Moonchild2021-01-25-16/+32
|/ | | | Resolves #1719
* Issue #1319 - Resolve RELEASE_OR_BETA questions in all.jsMoonchild2021-01-23-27/+11
| | | | | | | | | | | | | | | | | | | | | | - Enabled SVG transform-box property. I've tested this extensively including the bug that prevented Mozilla from shipping until 55 which does not seem to apply to us (most likely a stylo issue). Should be good to go. - Moved the getRootNode pref to a better place (no change) - Enabled inputmode property for forms. This is n/a for physical keyboards but should improve the experience for soft keyboards that can pop up various forms of input (e.g. numeric) depending on the mode indicated. According to BZ this is feature complete at our level but was problematic for Android which we don't have support for anyway. - Restricted crashing on insecure input of text to debug only. - Enabled shutting down the async OSFile worker if not used for 30 seconds to be more conscientious about resource use. - Enabled blocking of autoplay of media in the background by default, since it is a saner default to have for the OOBE and is commonly a desired setting by users (see forum). - Disabled the storage manager API by default. This fine-grained control over stored website data is already handled by various extensions and we don't have the front-end support for it. Assuming this was necessary for Mozilla due to limited access of WebExtensions to this kind of data.