| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
| |
This resolves #1517
|
| |\
| |
| | |
Incremental shadowdom-merge
|
| | | |
|
| |/
|
|
|
| |
At the very least we should enable these short term, with the potential
removal of it pending.
|
| | |
|
| |
|
|
|
|
| |
This should be the last code backout for this. merging this branch
should get us back to the way we were (+ additional code changes for
later changes) as fasr as the unused unboxed code is concerned.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This stub is added because websites insist on considering this
very hardware-dependent and O.S.-variable low-level font-control
as a "critical feature" which it isn't as there is 0 guarantee
that font variation settings are supported or honored by any
operating system used by the client.
On top this is a WD status feature that sites shouldn't be using, and
the feature itself is strongly discouraged for use in favor of standard
CSS font manipulation keywords like `font-weight`.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This gets rid of platform-dependent hard-coded defaults, but keeps
build-time blocking if there is no GL provider (in which case layers
acceleration almost certainly won't work because it needs a GL
compositor and would likely crash without)
New prefs are
- layers.acceleration.enabled to enable HWA
- layers.acceleration.force to force it enabled (requires .enabled to be
set as well)
This is the platform part of this issue. The rest will be front-end work
(Preference UI integration and pref migration)
|
| |/
|
|
| |
Tag UXP Issue #1344
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The indicated BZ bug was resolved in Gecko 50, and could have already
been enabled before (since it returns a promise as-required).
With the rest of promise-based media implemented it makes no sense to
keep this disabled on production.
|
| | |
|
| |
|
|
|
| |
This sets some defaults for production builds that should be
self-explanatory.
|
| |
|
|
|
|
| |
Considering the one exception this was still enabled for on all versions
of Firefox since 45 until our fork point is no longer applicable.
This resolves #1353
|
| | |
|
| |
|
|
| |
This also sets sane defaults when present. See also #1319.
|
| |
|
|
| |
Tag #1343
|
| |
|
|
|
|
|
| |
Previously-used `Courier New` was purposefully used at a smaller font
size due to its width. With the font switch this forced downscaling is
no longer needed, although it should still remain somewhat smaller than
variable width for balance (variable width is inherently more compact).
|
| |
|
|
| |
localizations where this would be set to Courier New.
|
| |
|
|
| |
This resolves #1313.
|
| | |
|
| | |
|
| |
|
|
|
| |
Use <cmath>'s functions over fdlibm's for performance reasons.
No significant precision loss when doing this.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This also reorganizes the exports in the build system to use `brotli/`
as include directory.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
and AutomaticAuth, and default to not prompting.
This resolves #1275.
|
| |
|
|
| |
This should do it for all the commits to files I changed, but while I'm in here I could probably go ahead and turn ALL the singular if defined statements into ifdef statements by using grep/find on the tree. On the other hand, perhaps we should do that as a separate issue so that this doesn't become a case of scope creep.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
u_int32_t and u_int64_t.
https://bugzilla.mozilla.org/show_bug.cgi?id=1350355
u_int32_t is not an stdint.h type. Windows already requires this, Solaris needs it too. If someone has a nit with this approach, the alternatives include:
1. Just replacing every instance of u_int32_t with uint32_t.
2. Including <sys/types.h> for Solaris only, which does define this.
3. Changing the original ifdef to be WIN32 || XP_SOLARIS
But it really doesn't matter how you solve this problem, all of the approaches are functionally equivalent, and this one has been used in Firefox since version 55. As far as I can tell, all it does is apply a fix that was being done for Windows already to any platform that needs it.
|
| |
|
|
|
|
|
|
|
|
| |
gathered together.
https://bugzilla.mozilla.org/show_bug.cgi?id=1158445
https://bugzilla.mozilla.org/show_bug.cgi?id=963983
https://bugzilla.mozilla.org/show_bug.cgi?id=1542758
Solaris madvise and malign don't perfectly map to their POSIX counterparts, and some Linux versions (especially Android) don't define the POSIX counterparts at all, so options are limited. Ideally posix_madvise and posix_malign should be the safer and more portable options for all platforms.
|
| | |
|
| |
|
|
|
| |
General consensus seems to be that color management on Linux desktops
is not mature enough to enable by default.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This prevents cross-file access from files loaded into the browser from
the local file system, further restricting the origin policy of file:
URIs.
Added a pref to control this behavior for local file access if required
for certain applications, since this change might break using the
browser to run applications on the local file system that require
access to local files.
|
| |
|
|
|
|
| |
Still allow this to be bypassed with a pref for those really rare corner
cases where images are loaded cross-origin by design and the session
hasn't been/can't be authenticated ahead of time.
|
| | |
|
| |
|
|
|
| |
- Keep .wake as an alias until we're certain it can be removed.
- Enable SAB memory
|
| | |
|
| |
|
|
| |
Create a new pref 'dom.meta-set-cookie.enabled' which is set to 'false', disabling http-equiv meta cookies.
|
| | |
|
