| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
| |
- Remove non-applicable comment about AVX2.
- Update config documentation for 32-bit darwin.
|
|
|
|
| |
This resolves #637
|
|
|
|
|
|
|
|
|
| |
- Use placesutils for favicons
- Switch to the PageThumbs service for thumbnails (like QuickDial)
- Make thumb requests asynchronous
- Update canvas handling
This resolves #731
|
|
|
|
| |
This resolves #738
|
|
|
|
| |
This reverts commit 4ceb21241eacac2911f2fed846359215870f121f.
|
|
|
|
| |
This reverts commit e7189e33f533f9b974b22c2110b522a13bc4c7f6.
|
|\ |
|
| |\
| | |
| | | |
Don't build ffvpx on 32-bit platforms (except Windows)
|
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
|/ /
| |
| |
| |
| |
| | |
r=bbouvier, a=RyanVM"
This reverts commit 9472136272f01b858412f2d9d7854d2daa82496f.
|
| |
| |
| |
| | |
Follow-up to a930db1c9e8444ed89754c5a79085d59c7295952
|
| | |
|
| |
| |
| |
| | |
Tag #447
|
|/
|
|
| |
This resolves #735
|
|\
| |
| | |
Refresh nsStringBundleService and nsHttpHandler when the browser locale is changed
|
| |
| |
| |
| | |
changed
|
| | |
|
| | |
|
|/
|
|
| |
Resolves #732
|
|
|
|
|
| |
When true, overrides the OS convention to prevent scrolling of content when contextual menus are open.
This resolves #730.
|
|\
| |
| | |
[PALEMOON] Fix document navigation using F6
|
|/ |
|
|
|
|
| |
Also clear the telemetry URLs and metas "just in case" so nothing can go anywhere even in the case of PEBCAK.
|
| |
|
|\
| |
| | |
Update ShouldAddToSessionHistory() rules for "about:newtab" and "about:logopage"
|
| |
| |
| |
| | |
ShouldAddToSessionHistory()
|
| |
| |
| |
| | |
"about:newtab" in the session history
|
| | |
|
|\ \
| |/
|/| |
Basilisk: Fix locale error on migration.xul on Linux
|
|/ |
|
| |
|
|
|
|
|
|
| |
Fix jar manifests.
This resolves #713
|
|
|
|
| |
This resolves #713
|
|\
| |
| | |
Remove unused variable
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
Tag #21
|
| |
| |
| |
| | |
Tag #21
|
| |
| |
| |
| | |
Tag #21
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
|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).
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
|/| |
Basilisk: Remove TelemetryStopwatch
|
|/ |
|
|\
| |
| | |
[PALEMOON] Align viewPartialSource with the UXP codebase
|
| | |
|