summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Merge pull request #720 from JustOff/PR_ShouldAddToSessionHistoryMoonchild2018-08-22-1/+7
|\ | | | | Update ShouldAddToSessionHistory() rules for "about:newtab" and "about:logopage"
| * Explicitly specify parentheses in a mixed boolean expression in ↵JustOff2018-08-22-2/+2
| | | | | | | | ShouldAddToSessionHistory()
| * Use "browser.newtabpage.add_to_session_history" to decide whether to store ↵JustOff2018-08-22-5/+7
| | | | | | | | "about:newtab" in the session history
| * Update ShouldAddToSessionHistory() rules for "about:newtab" and "about:logopage"JustOff2018-08-21-1/+5
| |
* | Merge pull request #722 from g4jc/importfromunixMoonchild2018-08-22-4/+2
|\ \ | |/ |/| Basilisk: Fix locale error on migration.xul on Linux
| * Basilisk: Fix locale error on migration.xul on LinuxGaming4JC2018-08-21-4/+2
|/
* Pale Moon blocklist updatewolfbeast2018-08-21-2/+12
|
* Fix toolbar styling in non-Australis toolkit themes part 2wolfbeast2018-08-21-3/+3
| | | | | | Fix jar manifests. This resolves #713
* Fix toolbar styling in non-Australis toolkit themeswolfbeast2018-08-21-1/+30
| | | | This resolves #713
* Merge pull request #718 from trav90/code-cleanupMoonchild2018-08-20-1/+0
|\ | | | | Remove unused variable
| * Remove unused variabletrav902018-08-19-1/+0
| |
* | Re-implement custom background color of standalone images.wolfbeast2018-08-20-0/+23
| | | | | | | | | | | | | | | | This resolves #717. Note: this does not affect other applications because the platform default is to use the "darknoise" background image for standalone image, which effectively overrides a bg color.
* | Remove TelemetryStopwatch module.wolfbeast2018-08-20-493/+0
| | | | | | | | Tag #21
* | Remove TelemetryStopwatch call sites from mobile components.wolfbeast2018-08-20-5/+0
| | | | | | | | Tag #21
* | Remove TelemetryStopwatch call sites from toolkit components.wolfbeast2018-08-20-51/+0
| | | | | | | | Tag #21
* | Merge pull request #714 from trav90/class-memaccess-errorsMoonchild2018-08-20-17/+56
|\ \ | | | | | | | | | | | | | | | | | | Fix more -Wclass-memaccess warnings: - Avoid using memset on a not-trivial types - Avoid doing memset on non-POD structures - Be more restrictive with memset on Array containers
| * | Avoid using memset on a not-trivial type like ServoSizestrav902018-08-18-1/+9
| | |
| * | Avoid using memset on a not-trivial type like TabSizestrav902018-08-18-1/+7
| | |
| * | Avoid doing a memset on a non-POD structuretrav902018-08-18-13/+33
| | | | | | | | | | | | | | | | | | |entryCount| tracks -- in fast-to-check manner -- the number of entries in the hashtable. But to actually enumerate entries, we have to loop through all of |table|, checking for entries that are actually live. A live entry is indicated by a zero |hash| in the entry. The |memset| would properly zero that; removing the memset will not. It's not entirely clear whether a memset that overwrites a lot of stuff but is maybe simpler, is faster than compiler-generated likely-SIMD code that zeroes out *just* |hash| fields in all the entries. But I am going to guess that SIMD is good enough. For now, we should just do the simple and thing: don't distinguish POD and non-POD, and know that the compiler is going to recognize that |mem.addr()->~T()| is a no-op when T is trivial. So with POD, the loop should degenerate to just zeroing |hash| at consistent offset, and SIMD will eat that up, and it can't be *that* different from the memset in performance (if it is at all).
| * | memset only the underlying vector from the Array containertrav902018-08-18-1/+1
| | |
| * | Avoid using memset on a not-trivial type like nsTabSizestrav902018-08-18-1/+6
| |/ | | | | | | | | | | nsTabSizes is non-trivial only because of the user-defined constructor. The idea desired here is certainly to zero all the members without listing them -- but the very act of doing so with a user-defined constructor, makes the idea impossible. Arguably this is something that is permissible in the language, and that the warning should be tailored to permit. I don't think this falls afoul of any of the issues flagged in https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html for example. In the meantime, just explicitly zeroing the three member fields is easy and fixes the warnings.
* | Merge pull request #716 from g4jc/remove_telemetry_stopwatchMoonchild2018-08-20-212/+8
|\ \ | |/ |/| Basilisk: Remove TelemetryStopwatch
| * Basilisk: Remove TelemetryStopwatchGaming4JC2018-08-19-212/+8
|/
* Merge pull request #712 from JustOff/PR_viewPartialSourceMoonchild2018-08-17-24/+2
|\ | | | | [PALEMOON] Align viewPartialSource with the UXP codebase
| * [PALEMOON] Align viewPartialSource with the UXP codebaseJustOff2018-08-17-24/+2
| |
* | Fix missed in32->int64 in df852120098dc7ba5df4a76126c6297c6d2d1b7bwolfbeast2018-08-17-1/+1
|/ | | | Tag #709.
* Reinstate RC4 and mark 3DES weak.wolfbeast2018-08-17-1/+9
| | | | Tag #709
* Extend {EnabledWeakCiphers} bit field to allow more cipher suites.wolfbeast2018-08-17-8/+8
| | | | Tag #709.
* Merge pull request #708 from wicknix/masterMoonchild2018-08-16-2/+2
|\ | | | | fix basilisk mac icons, executable name, and min os version
| * Add files via uploadwicknix2018-08-14-0/+0
| | | | | | remove old mac firefox icns files and replace with basilisk icns files
| * Update Info.plist.inwicknix2018-08-14-2/+2
| | | | | | fix exe name and min osx version
* | Update CODE_OF_CONDUCT.mdMoonchild2018-08-15-1/+2
| | | | | | Minor style improvement
* | Move Code of Conduct to where it belongs.wolfbeast2018-08-15-0/+0
| | | | | | | | (Damn you, github on-line editor!)
* | Add Code of Conduct for contributors.Moonchild2018-08-15-0/+47
| | | | | | As a recommended document for governance of our project and community.
* | Do not try and include devtools shared l10n when devtools is not builtMatt A. Tobin2018-08-15-0/+2
|/
* Enforce NSS 3.38 for people who still insist on using system NSS.wolfbeast2018-08-14-1/+1
|
* Update NSS to 3.38wolfbeast2018-08-14-7145/+4873
| | | | | | | | | | | | | - Added HACL*Poly1305 32-bit (INRIA/Microsoft) - Updated to final TLS 1.3 draft version (28) - Removed TLS 1.3 prerelease draft limit check - Removed NPN code - Enabled dev/urandom-only RNG on Linux with NSS_SEED_ONLY_DEV_URANDOM for non-standard environments - Fixed several bugs with TLS 1.3 negotiation - Updated internal certificate store - Added support for the TLS Record Size Limit Extension. - Fixed CVE-2018-0495 - Various security fixes in the ASN.1 code.
* Set version for normal unstable channel use.wolfbeast2018-08-13-1/+1
|
* Merge pull request #707 from trav90/class-memaccess-errorsMoonchild2018-08-13-28/+10
|\ | | | | Simplify HeapSlot to make it trivially copyable
| * Simplify HeapSlot to make it trivially copyabletrav902018-08-12-29/+8
| | | | | | | | This removes the constructors, which were never called since we allocate arrays of HeapSlot with pod_malloc. The destructor is only ever called explicitly since we free this memory with js_free so it has been renamed to destroy(). Also removed is an unused manual barrier.
| * Avoid using memcpy on HeapSlot that is not trivially copyable.trav902018-08-12-4/+7
| |
* | Merge pull request #706 from trav90/gcc8Moonchild2018-08-13-14/+17
|\ \ | | | | | | Fix/silence some warnings with GCC 8
| * | Remove the const to fix the -Wignored-qualifiers warning with GCC 8 (Part 2)trav902018-08-10-5/+5
| | |
| * | Fix a warning with GCC 8: unnecessary parentheses in declaration of 'type name'trav902018-08-10-2/+2
| | |
| * | Disable -Werror on -Wmultistatement-macrostrav902018-08-10-0/+3
| | | | | | | | | | | | Silences compiler warning spam with GCC 8.
| * | Remove the const to fix the -Wignored-qualifiers warning with GCC 8trav902018-08-10-5/+5
| | |
| * | Initialize mVersion to silence a warning with GCC 8trav902018-08-10-1/+1
| | |
| * | js::atomics_wait: Remove unnecessary parentheses in declaration of 'addr'trav902018-08-10-1/+1
| |/ | | | | | | Silences a warning with GCC 8.
* | Merge pull request #704 from trav90/buildsystem-workMoonchild2018-08-13-1/+7
|\ \ | |/ |/| Shell quote environment variable values when dumping them in dump_env.py
| * Shell quote environment variable values when dumping them in dump_env.pytrav902018-08-11-1/+7
|/ | | | The mozconfig output parsing code already (mostly) handles shell quoted strings, because that's what `set` outputs. By quoting environment variable values, we avoid a bunch of problems with "weird" values.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-26 01:32:25 +0000