| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
| |
This enables the DOM Animations API core functions with the exception of those
parts that are either unimplemented or not ready for use, which have been
preffed off in this issue's previous parts.
Also tag #1319 for enabling a previous RELEASE_OR_BETA shielded API.
|
|
|
|
|
| |
This is probably the last thing we will ship (if ever) since it needs the most
spec and implementation work for arbitrary use that is pretty far into a corner.
|
|
|
|
|
|
|
|
| |
This feature should not be shipped until the various definitions of addition for
each additive property are properly specified and then implemented accordingly.
Unlike other patches in this series, compositing is not frequently used
internally so there is no need to enable this by default for chrome callers.
|
|
|
|
|
|
|
|
|
| |
This preference controls whether authors are allowed to specify animations
without a 0% or 100% keyframe.
We intend to ship this but it isn't implemented yet (needs a follow-up) but this
preference acts as a safeguard in case we discover we need to disable it once
it's implemented.
|
|
|
|
| |
Default false, no intent to ship for web content. Always enabled for Chrome.
|
|\
| |
| |
| | |
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1707
|
| |
| |
| |
| |
| | |
This should be all parts needed to add a brand new enum keyword including
getting the computed style from it...
|
|/
|
|
| |
Also flips ion inlining pref back on
|
|
|
|
|
| |
This fully works for splitting gkmedias.dll back out from xul with one exception
which is Skia throwing undefined externals when linking gkmedias.
|
| |
|
|
|
|
|
|
|
| |
As of [da0c073a7] we no longer need this workaround because the issue is avoided
with proper sleep/wake logic restored.
This reverts commit 2fa993b5639e04c7e1d7403ecf9175a223ce50b4.
|
| |
|
|
|
|
| |
This reverts commit 45a976a5f1e83c3c2f7fcf85b1fa5315946f4c1a.
|
|
|
|
| |
The default is now set to the more stable but slower global setting.
|
|
|
|
| |
This also adds it to JS_SetGlobalJitCompilerOption()
|
|
|
|
|
|
| |
This is CVE-2020-15999.
* src/sfnt/pngshim.c (Load_SBit_Png): Test bitmap size earlier.
|
|
|
|
|
| |
Since several entities have started to ban .9 versions, even if they are valid
ESR versions.
|
| |
|
| |
|
|
|
|
|
| |
This has been broken for 11 years. About time it's fixed.
Tag #1683
|
|
|
|
| |
Resolves #1682
|
|
|
|
|
| |
There don't seem to be any drawbacks to this; tested for the past month disabled
and there have been no issues with any sites visited. Adoption seems very low.
|
| |
|
|
|
|
| |
Another S&R run with some smarter matching.
|
|
|
|
|
|
| |
Since these are just interpreted comments, there's 0 impact on actual code.
This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are
a few others scattered around which will be removed manually in a second part.
|
|
|
|
| |
Implements ResizeObserver, ResizeObserverEntry and ResizeObservation
|
|
|
|
| |
This is just a clean port of 1322191 and follow-up 1325970. It really seems to add create a new way to access existing code relating to block formatting and floating elements rather than implementing new functionality, and it is mercifully straightforwards.
|
| |
|
|
|
|
|
|
|
| |
Unless a user is debugging media errors, this detail is unnecessary to report
and could include sensitive data which could be abused by third-party
requesters. This aligns it with the standard success/error paradigms in normal
browsing situations.
|
|\
| |
| | |
Respond to disabled attribute set on <link> elements from HTML
|
| |
| |
| |
| |
| |
| | |
This is not very "clean," and is mostly done in the same sloppy way as Emilio did it because that's basically the only way you can do it. Note well that this does NOT actually turn off everything I've done in a clean fashion like ifdefs would. For instance, the Explicitly Enabled flag is still present, but is now always false because the only condition that can set it true is behind the pref and therefore inert when this pref is off. Also, because the arguments of SetDisabled have changed, my modifications to SetMozDisabled must be present regardless of whether the pref is on or off. What I have done is turn off the actual reflection of the disabled attribute in Disabled and SetDisabled, as well as in AfterSetAttr.
However, turning the pref off seems to restore more or less our old behavior, though there may be subtle differences unlike with an ifdef since this is, unfortunately, not an exact science and I can only turn off changes that happen within individual functions and not changes in how functions interact with each other.
|
|\ \
| | |
| | | |
[Image/CSS] Intrinsic Aspect Ratio
|
| | |
| | |
| | |
| | | |
A simpler name feels so much cleaner.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://bugzilla.mozilla.org/show_bug.cgi?id=1547231
https://bugzilla.mozilla.org/show_bug.cgi?id=1559094
https://bugzilla.mozilla.org/show_bug.cgi?id=1633434
https://bugzilla.mozilla.org/show_bug.cgi?id=1565690
https://bugzilla.mozilla.org/show_bug.cgi?id=1602047
Make use of Aspect Ratios in Image frames before Images are loaded.
- Check for width and height HTML properties and create a ratio with them.
- Overwrite HTML size values with actual image dimensions on load.
- Collapse any frames with srcless images.
Comments:
dom/html/nsGenericHTMLElement.cpp:1483
layout/generic/nsImageFrame.cpp:289
|
|/ /
| |
| |
| |
| |
| |
| | |
This is apparently used for fallback selection and if available it is "assumed"
Shadow DOM is also available, while this is a utility function.
Webcompat is a nightmare sometimes.
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
This removes the (default disabled) node.rootNode readonly attribute
and replaces it with a node.getRootNode() function per WhatWG
spec discussion.
Based on work by John Dai <jdai@mozilla.com>
|
| |
|
| |
|
|
|
|
| |
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`.
|
| |
|