summaryrefslogtreecommitdiffstats
path: root/modules
Commit message (Collapse)AuthorAgeLines
* 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`.
* 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 #1359 - Pointlessly rename greprefs.. again.Matt A. Tobin2020-01-18-9/+7
|
* 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
* No issue - Remove unused network.http.bypass-cachelock-threshold pref.wolfbeast2020-01-14-8/+0
|
* No issue - Don't define gamepad prefs when gamepad support isn't built.wolfbeast2020-01-14-4/+2
| | | | This also sets sane defaults when present. See also #1319.
* Bug 1322938 - Put <dialog> element behind preference.Gaming4JC2020-01-07-0/+3
| | | | Tag #1343
* Issue #1328 - Follow-up: Increase font size for changed monospace fonts.wolfbeast2019-12-18-6/+6
| | | | | | | 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).
* Issue #1328 - Part 1: Change default monospace font to Consolas for allwolfbeast2019-12-18-6/+6
| | | | localizations where this would be set to Courier New.
* Issue #1313 - Bump Firefox compatMode version to 68.9wolfbeast2019-12-04-1/+1
| | | | This resolves #1313.
* Issue #1291 - Part 4: Update patch fileswolfbeast2019-11-15-155/+562
|
* Issue #1291 - Part 3: Update fdlibm to Sept 2019 versionwolfbeast2019-11-15-102/+163
|
* Issue #1291 - Part 2: Stop using the lib's sqrt() functionwolfbeast2019-11-15-459/+17
| | | | | Use <cmath>'s functions over fdlibm's for performance reasons. No significant precision loss when doing this.
* Issue #1291 - Part 1: Ensure exp(1) returns e exactly (use a const)wolfbeast2019-11-15-0/+3
|
* Issue #80 - Stop building embedded xz lib unifiedwolfbeast2019-11-15-1/+1
|
* Issue #80 - Stop building woff2 lib unifiedwolfbeast2019-11-15-1/+1
|
* Issue #80 - Stop building brotli lib unifiedwolfbeast2019-11-15-2/+2
|
* Issue #1288 - Part 3: Update woff2 component to 1.0.2wolfbeast2019-11-14-583/+554
|
* Issue #1288 - Part 1a: Update brotli to 1.0.7wolfbeast2019-11-14-11582/+32333
| | | | | This also reorganizes the exports in the build system to use `brotli/` as include directory.
* Issue #618 - Flip on module type scripting.wolfbeast2019-11-10-1/+1
|
* Issue #618 - Misc fixes (merge conflicts)wolfbeast2019-11-10-0/+4
|
* Issue #1275 - Add pref to disable warning prompts for SuperfluousAuthwolfbeast2019-11-07-0/+6
| | | | | | and AutomaticAuth, and default to not prompting. This resolves #1275.
* MoonchildProductions#1251 - Part 27: Fix ifdef style.athenian2002019-10-21-1/+1
| | | | 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.
* MoonchildProductions#1251 - Part 15: fdlibm should provide definition for ↵athenian2002019-10-21-2/+6
| | | | | | | | | | | | | | | | 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.
* MoonchildProductions#1251 - Part 7: All the posix_m* memory-related stuff, ↵athenian2002019-10-21-1/+3
| | | | | | | | | | 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.
* Issue #1231 - Correct defines for Mac and keep universal prefs generic.wolfbeast2019-10-21-6/+6
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-20 10:30:48 +0000