summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Call the relevant scope-data constructor when allocating it, and poison/mark ↵trav902018-09-02-31/+72
| | | | as undefined the memory for the trailing array of BindingNames, ratther than impermissibly PodZero-ing non-trivial classes.
* Convert the trailing array of BindingNames at the end of the various kinds ↵trav902018-09-02-64/+108
| | | | of scope data into raw unsigned chars into which those BindingNames are placement-new'd, rather than memcpy-ing non-trivial classes around and failing to comply with the C++ object model
* Make nsScannerIterator a trivial type in order to use memsettrav902018-09-02-9/+9
|
* [ffvpx] Update readmetrav902018-09-02-6/+1
| | | | | - Remove non-applicable comment about AVX2. - Update config documentation for 32-bit darwin.
* Remove FxA migrator.wolfbeast2018-09-02-275/+0
| | | | This resolves #637
* [PALEMOON] Update the taskbar preview per tab module for UXP.wolfbeast2018-09-02-239/+375
| | | | | | | | | - Use placesutils for favicons - Switch to the PageThumbs service for thumbnails (like QuickDial) - Make thumb requests asynchronous - Update canvas handling This resolves #731
* Remove support for TLS session caches in TLSServerSocket.wolfbeast2018-09-01-43/+15
| | | | This resolves #738
* Revert "Switch to using a single memory allocation arena"wolfbeast2018-09-01-1/+1
| | | | This reverts commit 4ceb21241eacac2911f2fed846359215870f121f.
* Revert "Bug 1388020. r=nical, a=RyanVM"wolfbeast2018-08-30-41/+6
| | | | This reverts commit e7189e33f533f9b974b22c2110b522a13bc4c7f6.
* Merge branch 'master' of https://github.com/MoonchildProductions/UXPwolfbeast2018-08-30-3/+7
|\
| * Merge pull request #741 from trav90/media-workMoonchild2018-08-30-3/+7
| |\ | | | | | | Don't build ffvpx on 32-bit platforms (except Windows)
| | * Don't build ffvpx on 32-bit platforms (except Windows)trav902018-08-26-3/+7
| | | | | | | | | | | | | | | | | | Our in-tree FFmpeg doesn't support optimized assembly code very well on 32-bit *nix systems, which causes performance issues during video playback. Essentially, this commit restores the behavior from Pale Moon 27 on 32-bit Linux builds (for video playback rely on the system-installed FFmpeg packages or libvpx if FFmpeg packages can't be found).
* | | Revert "Bug 1444668 - Avoid allocating large AssemblerBuffers. r=luke, ↵wolfbeast2018-08-30-49/+9
|/ / | | | | | | | | | | r=bbouvier, a=RyanVM" This reverts commit 9472136272f01b858412f2d9d7854d2daa82496f.
* | Fix incorrect code removal in ipc.wolfbeast2018-08-29-0/+27
| | | | | | | | Follow-up to a930db1c9e8444ed89754c5a79085d59c7295952
* | Sync disabled state of number control regardless of appearance.wolfbeast2018-08-29-2/+2
| |
* | Update HSTS preload listtrav902018-08-27-2462/+4464
| | | | | | | | Tag #447
* | Update installer strings for Pale Moon to match toolkit nsis installer.wolfbeast2018-08-27-7/+12
|/ | | | This resolves #735
* Merge pull request #733 from JustOff/PR_locale_changed_refreshMoonchild2018-08-26-15/+54
|\ | | | | Refresh nsStringBundleService and nsHttpHandler when the browser locale is changed
| * Refresh nsStringBundleService and nsHttpHandler when the browser locale is ↵JustOff2018-08-25-15/+54
| | | | | | | | changed
* | Add missing }wolfbeast2018-08-25-0/+1
| |
* | Switch to using a single memory allocation arenawolfbeast2018-08-25-1/+1
| |
* | Add a horizontal scroll action option for mouse wheel.wolfbeast2018-08-25-3/+10
|/ | | | Resolves #732
* Introduce ui.menu.allow_content_scrollwolfbeast2018-08-24-1/+13
| | | | | When true, overrides the OS convention to prevent scrolling of content when contextual menus are open. This resolves #730.
* Merge pull request #727 from JustOff/PR_VK_F6Moonchild2018-08-23-12/+2
|\ | | | | [PALEMOON] Fix document navigation using F6
| * [PALEMOON] Fix document navigation using F6JustOff2018-08-23-12/+2
|/
* Stop pointless recording of telemetry datawolfbeast2018-08-23-4/+4
| | | | Also clear the telemetry URLs and metas "just in case" so nothing can go anywhere even in the case of PEBCAK.
* Fix code of conduct version ref link.wolfbeast2018-08-22-1/+1
|
* 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
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-18 22:51:45 +0000