| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
There is a lot of string compare when using CSS property name. We should use nsGkAtoms instead.
Ref: Bug 1323138
|
|
|
|
| |
Baby has his bottle, you ok now?
|
| |
|
| |
|
|
|
|
|
| |
Ensures aspect ratio numerator and denominator aren't swapped in vertical writing modes.
https://bugzilla.mozilla.org/show_bug.cgi?id=1548768
|
|
|
|
|
| |
This existed in Firefox before this bug.
I don't know if it came from a previous bug or was removed post-fork.
|
|
|
|
|
|
|
|
|
| |
https://bugzilla.mozilla.org/show_bug.cgi?id=1547792
Aspect Ratio handling simplified by using floating point integers:
- Multiplication of value (or inverse value) to a known side for Scaling
- No unequal equal values such as "4/3" vs "8/6" vs "20/15"
- Truly "Empty" aspect ratios, even if one dimension is not 0
|
| |
|
| |
|
|
|
|
|
|
| |
EditorBase parameter of GetTextNode is unnecessary because it uses static method only. Also, we should return nsINode to reduce QI.
Resolves #1617
|
|
|
|
| |
I meant to do this a long time ago, but basically it accounts for the new XP_SOLARIS build flag that never made it into the MailNews code. Additionally, it enables a compatibility flag for Solaris 11.4 that allows us to use the three-argument implementation of ctime_r still used by Solaris 11.3 and illumos (which also appears equivalent to the NSLDAPI_CTIME implementation used by libldap internally). Also, the ctime_r function has been added to the time.h header library for a while now, not sure why Mozilla thought we didn't have a ctime_r implementation.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When using AF_CONN addresses, don't put these in the COOKIE
chunk. For these addresses it is possible to reconstruct them
locally. Conceptually, addresses are something to be shared
with the peer, but in the case of AF_CONN this might not be
the case. Therefore, zero then out.
Thanks to Natalie Silvanovich of Google Project Zero for
finding and reporting the issue.
|
|
|
|
| |
This fixes a spec compliance issue with section 8.1.4.2 Fetching scripts.
|
|
|
|
|
|
| |
JIT optimizations involving the Javascript 'arguments' object could
potentially confuse later optimizations, so we simply disable these
optimizations as a DiD measure.
|
| |
|
| |
|
| |
|
|
|
|
| |
FINE! I'll go to bed already...
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
These should all be spec-compliant and were (for release-trickling of features)
arbitrarily disabled by Mozilla at our fork point. There's no real reason to
keep them disabled since they are used in the wild.
|
|
|
|
|
|
|
|
| |
considered "native" by the Add-ons Manager when using the Dual-GUID system
A version bump triggering add-on compatibility check will re-evaluate the "native" status (among other things) so no extra or special work is required to fix erroneous warnings.
tl;dr instafix!
|
| |
|
|
|
|
|
|
|
| |
The added debug assertion did not take into account microtask refactoring done in BZ 1405821.
Resulting in error: no member named 'IsInMicroTask' in 'nsContentUtils'.
This resolves the error.
|
| |
|
|
|
|
|
|
| |
This changes NativeObject::slotSpan() to get the class from the object group
rather than getting it from the base shape to avoid a race between
Shape::ensureOwnBaseShape and background sweeping.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The implementation is based on the work by Bernstein and Yang
(https://eprint.iacr.org/2019/266)
"Fast constant-time gcd computation and modular inversion".
It fixes the old mp_gcd and s_mp_invmod_odd_m functions. The patch also fixes
mpl_significant_bits s_mp_div_2d and s_mp_mul_2d by having less control flow to
reduce side-channel leaks.
Co-authored by : Billy Bob Brumley
|
| |
|
|
|
|
|
|
|
| |
Includes removing an error code for a function that never fails, and removing an
error return when the function successfully did what it said it would.
Ref: BZ 1644477
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Report source position information for module export resolution failures.
Ref: BZ 1362098
|
|
|
|
| |
Ref: BZ 1388728
|
|
|
|
| |
Ref: BZ 1388728
|
|
|
|
|
|
|
|
|
| |
For checking if a module is in an error state and what the error is, it
shouldn't matter if we are currently GC-ing or not. So we don't need to check
for it, which removes the requirement to pass in the JS context (needed for
AssertHeapIsIdle's runtime check); this unblocks progress where otherwise we'd
have to figure out what the context is at the module level just to satisfy this
check.
|
|
|
|
|
| |
This backs out the stuff added in Bug 1295978.
Ref: BZ 1295978, 1388728
|
| |
|
|
|
|
|
|
| |
9ca74147225eed305e28c7887f9b2251aeeb0f36
Ref: BZ 1388728
|
|
|
|
| |
Ref: BZ 1388728
|
| |
|
|
|
|
|
| |
Store and re-throw module instantiation and evaluation errors.
Ref: BZ 1374239, 1394492
|