summaryrefslogtreecommitdiffstats
path: root/modules/libpref/init
Commit message (Collapse)AuthorAgeLines
* Issue #1319 - Resolve RELEASE_OR_BETA questions in all.jsMoonchild2021-01-23-27/+11
| | | | | | | | | | | | | | | | | | | | | | - Enabled SVG transform-box property. I've tested this extensively including the bug that prevented Mozilla from shipping until 55 which does not seem to apply to us (most likely a stylo issue). Should be good to go. - Moved the getRootNode pref to a better place (no change) - Enabled inputmode property for forms. This is n/a for physical keyboards but should improve the experience for soft keyboards that can pop up various forms of input (e.g. numeric) depending on the mode indicated. According to BZ this is feature complete at our level but was problematic for Android which we don't have support for anyway. - Restricted crashing on insecure input of text to debug only. - Enabled shutting down the async OSFile worker if not used for 30 seconds to be more conscientious about resource use. - Enabled blocking of autoplay of media in the background by default, since it is a saner default to have for the OOBE and is commonly a desired setting by users (see forum). - Disabled the storage manager API by default. This fine-grained control over stored website data is already handled by various extensions and we don't have the front-end support for it. Assuming this was necessary for Mozilla due to limited access of WebExtensions to this kind of data.
* Issue #1630 - Enable W3C pointer events by default.Moonchild2021-01-19-1/+1
| | | | Resolves #1630
* [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
* 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()
* [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 #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 #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.
* [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
|
* 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`.
* Issue #1395 - Remove FlyWeb ServiceMatt A. Tobin2020-02-06-2/+0
|
* Merge branch '1360'wolfbeast2020-01-27-13/+10
|\
| * Issue #1360 - Part 1: Simplify layers acceleration prefs.wolfbeast2020-01-26-13/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Bug 1271549 - Remove details and summary preference.Gaming4JC2020-01-26-3/+0
|/ | | | Tag UXP Issue #1344
* Issue #1366 - Completely remove showModalDialogGaming4JC2020-01-21-1/+0
|
* Issue #1332 - Enable seeking to next frame by default.wolfbeast2020-01-14-6/+0
| | | | | | | 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.
* No issue - Remove some unused webextension sync preferences.wolfbeast2020-01-14-8/+0
|
* Issue #1319 - Set some obvious prefs for production builds.wolfbeast2020-01-14-22/+3
| | | | | This sets some defaults for production builds that should be self-explanatory.
* Issue #1353 - Disable remote jar: URIs by default.wolfbeast2020-01-14-5/+0
| | | | | | 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
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-29 00:43:50 +0000