summaryrefslogtreecommitdiffstats
path: root/modules
Commit message (Collapse)AuthorAgeLines
* [Media] Enable AV1 by default if builtMatt A. Tobin2021-01-18-1/+1
|
* Issue #1689 - Part 5: Enable DOM Animations API except the preffed-off parts.Moonchild2021-01-14-4/+0
| | | | | | | | 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.
* Issue #1689 - Part 4: Add a preference for {Document,Element}.getAnimations()Moonchild2021-01-14-3/+2
| | | | | 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.
* Issue #1689 - Part 3: Add a preference for animation composite modes.Moonchild2021-01-14-0/+1
| | | | | | | | 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.
* Issue #1689 - Part 2: Add a preference for implicit keyframesMoonchild2021-01-14-0/+1
| | | | | | | | | 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.
* Issue #1689 - Part 1: Add pref for DOM Animation timelines APIMoonchild2021-01-14-0/+1
| | | | Default false, no intent to ship for web content. Always enabled for Chrome.
* Merge pull request 'Add scrollbar-width CSS spec' (#1707) from 1705 into masterMoonchild2021-01-13-0/+3
|\ | | | | | | Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1707
| * Issue #1705 - Part 4: Add scrollbar-width CSS keyword to CSS parser.Moonchild2021-01-06-0/+3
| | | | | | | | | | This should be all parts needed to add a brand new enum keyword including getting the computed style from it...
* | Issue #1624 - Fix slot access intrinsics for objects with > 16 reserved slotsMatt A. Tobin2021-01-11-1/+1
|/ | | | Also flips ion inlining pref back on
* Issue #61 - Reinstate buildability with shared gkmedias dllMoonchild2021-01-02-0/+5
| | | | | This fully works for splitting gkmedias.dll back out from xul with one exception which is Skia throwing undefined externals when linking gkmedias.
* Issue #1053 - Part 1c: Remove references to mobile/android targets and pathsMoonchild2020-12-25-4/+0
|
* Revert "Issue #1695 - Add clamping to websocket polling timeouts."Moonchild2020-12-16-5/+0
| | | | | | | As of [da0c073a7] we no longer need this workaround because the issue is avoided with proper sleep/wake logic restored. This reverts commit 2fa993b5639e04c7e1d7403ecf9175a223ce50b4.
* Issue #1695 - Add clamping to websocket polling timeouts.Moonchild2020-12-12-0/+5
|
* Revert "Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default."Moonchild2020-12-08-2/+2
| | | | This reverts commit 45a976a5f1e83c3c2f7fcf85b1fa5315946f4c1a.
* Issue #1624 - flip the inlining pref.Moonchild2020-12-03-1/+1
| | | | The default is now set to the more stable but slower global setting.
* Issue #1624 - Make ion inlining optimizations a pref.Moonchild2020-12-03-0/+1
| | | | This also adds it to JS_SetGlobalJitCompilerOption()
* [sfnt] Fix heap buffer overflow.Werner Lemberg2020-11-19-7/+7
| | | | | | This is CVE-2020-15999. * src/sfnt/pngshim.c (Load_SBit_Png): Test bitmap size earlier.
* [UA] Change default compatibility mode version to 68.0Moonchild2020-11-16-1/+1
| | | | | Since several entities have started to ban .9 versions, even if they are valid ESR versions.
* Issue #1683 - Update libjar module.Moonchild2020-11-13-13/+101
|
* Issue #1683 - Update Brotli lib to 1.0.9Moonchild2020-11-13-2404/+3966
|
* [libjar] Fix inflation logic.Moonchild2020-11-13-1/+1
| | | | | This has been broken for 11 years. About time it's fixed. Tag #1683
* Issue #1682 - Remove vibrator DOM interface and support code.Moonchild2020-11-13-4/+0
| | | | Resolves #1682
* Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default.Moonchild2020-11-13-2/+2
| | | | | 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.
* Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23-18/+0
|
* Issue #1656 - Part 3: Nuke more vim config lines in the tree.Moonchild2020-09-23-1/+0
| | | | Another S&R run with some smarter matching.
* Issue #1656 - Part 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-3/+0
| | | | | | 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.
* Issue #1643 - Part 2: Implement ResizeObserver APIMoonchild2020-09-16-0/+3
| | | | Implements ResizeObserver, ResizeObserverEntry and ResizeObservation
* Issue #1641 - Implement CSS flow-root keywordathenian2002020-09-03-0/+3
| | | | 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.
* [misc/mar] Don't use a signed type for a length parameter.Moonchild2020-08-28-1/+1
|
* [media] Only include source error details in debugging scenarios.Moonchild2020-08-28-0/+8
| | | | | | | 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.
* Merge pull request #1632 from athenian200/link_element_disabledMoonchild2020-08-18-0/+8
|\ | | | | Respond to disabled attribute set on <link> elements from HTML
| * Issue #1629 - Part 3: Implement behind preference.athenian2002020-08-14-0/+8
| | | | | | | | | | | | 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.
* | Merge pull request #1613 from RealityRipple/AspectRatioMoonchild2020-08-08-0/+6
|\ \ | | | | | | [Image/CSS] Intrinsic Aspect Ratio
| * | Issue #1620 - Enable Intrinsic Ratio by DefaultAndy2020-08-07-1/+1
| | | | | | | | | | | | A simpler name feels so much cleaner.
| * | Issue #1620 - Use Intrinsic Aspect Ratio for ImagesAndy2020-08-04-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Pref and disable getRootNode()Moonchild2020-08-07-0/+2
|/ / | | | | | | | | | | | | 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.
* | Issue #1391 - Remove the DOM battery APIMoonchild2020-07-28-5/+0
| |
* | [css] Enable various arbitrarily-disabled CSS features in the platform.Moonchild2020-07-23-13/+1
| | | | | | | | | | | | 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.
* | Issue #1611 - Enable WASM by default but only enable jit when 64bitMatt A. Tobin2020-07-20-1/+7
|/
* Issue #1587 - Part 10: Expose controlling pref and enable by defaultMoonchild2020-06-12-0/+3
|
* Issue #1585 - Replace node.rootNode with node.getRootNode()Moonchild2020-06-10-7/+0
| | | | | | | 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>
* Issue MoonchildProductions/UXP#1578 - Add global menubar support for GTKLootyhoof2020-06-09-0/+4
|
* Prevent the existance of dangling pointers upon failure of FindDataStart.Bas Schouten2020-05-05-1/+2
|
* Issue #1517 - Remove dom.event.highrestimestamp.enabled prefMoonchild2020-05-04-1/+0
| | | | This resolves #1517
* Merge pull request #1518 from MoonchildProductions/shadowdom-mergeMoonchild2020-04-17-1/+0
|\ | | | | Incremental shadowdom-merge
| * Issue #1375 - Merge CustomElements pref with Webcomponents PrefMatt A. Tobin2020-04-17-1/+0
| |
* | Issue #1517 - Enable high-resolution DOM timestamps on trunkwolfbeast2020-04-16-2/+1
|/ | | | | At the very least we should enable these short term, with the potential removal of it pending.
* Issue #1498 - Part 6: Remove STS preloadlist pref.wolfbeast2020-03-27-2/+0
|
* Revert #1091 Remove unboxed object code phase 1 + extras.wolfbeast2020-02-23-0/+1
| | | | | | 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.
* [CSS] Add stub for font-variation-settingswolfbeast2020-02-11-0/+3
| | | | | | | | | | | | 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`.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-11 11:08:12 +0000