summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Issue #1719 - Make <menuitem> pref-controlled and disable by default.Moonchild2021-01-25-16/+32
| | | | Resolves #1719
* 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 #1715 - Handle errors when initializing print settings from the printerMoonchild2021-01-18-2/+12
| | | | | | fails due to a bad printer name or O.S. error. Resolves #1715
* Merge pull request 'Selectively enable and pref the DOM Web Animations API' ↵Moonchild2021-01-18-37/+86
|\ | | | | | | | | | | (#1714) from 1689 into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1714
| * 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-6/+16
| | | | | | | | | | 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-5/+8
| | | | | | | | | | | | | | | | 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-10/+35
| | | | | | | | | | | | | | | | | | 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-12/+27
| | | | | | | | Default false, no intent to ship for web content. Always enabled for Chrome.
* | Bump platform version for added features.Moonchild2021-01-16-1/+1
|/
* Merge pull request 'Add scrollbar-width CSS spec' (#1707) from 1705 into masterMoonchild2021-01-13-209/+394
|\ | | | | | | Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1707
| * Issue #1705 - Part 9b: Revert overzealous changes on Mac (cocoa).Moonchild2021-01-12-12/+2
| |
| * Issue #1705 - Part 9: Implement scrollbar-width:thin on Mac (cocoa).Moonchild2021-01-09-20/+47
| |
| * Issue #1705 - Part 8: Implement scrollbar-width:thin on GTK.Moonchild2021-01-09-24/+54
| |
| * Issue #1705 - Part 7: Implement scrollbar-width:thin on Windows.Moonchild2021-01-09-8/+33
| |
| * Issue #1705 - Part 6: Remove scrollbarbutton min-{width|height} rule from theme.Moonchild2021-01-08-2/+0
| | | | | | | | | | | | | | | | | | | | This would interfere with implementing thin scrollbars. Almost all widgets provide a non-overridable size for scrollbar buttons, so it makes no sense to specify min size for them. It is probably(?) a layout bug that min size properties can override the value returned by GetMinimumWidgetSize even if aIsOverridable is set to false, but removing this rule is simpler than locating and fixing the issue in layout code ;)
| * Issue #1705 - Part 5: Implement scrollbar-width:none for all target platforms.Moonchild2021-01-08-12/+27
| |
| * Issue #1705 - Part 4: Add scrollbar-width CSS keyword to CSS parser.Moonchild2021-01-06-0/+72
| | | | | | | | | | This should be all parts needed to add a brand new enum keyword including getting the computed style from it...
| * Issue #1705 - Part 3: Rename ScrollbarStyles to ScrollStyles.Moonchild2021-01-06-111/+111
| | | | | | | | | | | | | | | | | | | | | | ScrollbarStyles contains values of overflow, (over)scroll-behavior, etc. The only one which is marginally related to scroll _bars_ is overflow, which can be used to hide scrollbar (by making an element not scrollable) or enforce the scrollbar to display. It makes more sense to be called ScrollStyles as it's mainly concerning behavior of scrolling, not scrollbars. Also, with the addition of scrollbar width properties, the current name can be confusing.
| * Issue #1705 - Part 2: Add a ShowScrollbar enum to be used in ScrollReflowInput.Moonchild2021-01-06-29/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Overflow properties have two purposes: 1. controlling whether the scrollbar should be shown; 2. controlling whether the content is scrollable. However, with the scrollbar-width property being added, scrollability and presence of a scrollbar are no longer tied together. This patch makes a separation between the value of overflow and the presence of a scrollbar by making it clear that for ScrollReflowInput, we only care about whether scrollbar should be shown. This should make it easier to write the logic involving presence of the scrollbar based on webdev choice.
| * Issue #1705 - Part 1: Rename nsChangeHint_CSSOverflowChange to *ScrollbarChange.Moonchild2021-01-06-7/+7
| | | | | | | | Prepare for scrollbar-width which should trigger the same kind of change.
* | Issue #1624 - Fix slot access intrinsics for objects with > 16 reserved slotsMatt A. Tobin2021-01-11-1/+9
| | | | | | | | Also flips ion inlining pref back on
* | Issue #1710 - Check for triggering principal URI in FTP subresource check.Moonchild2021-01-09-0/+8
| | | | | | | | Resolves #1710
* | Merge pull request 'Add modern FreeBSD support' (#1706) from ↵Moonchild2021-01-07-82/+375
|\ \ | |/ |/| | | | | | | OlCe1/UXP:FreeBSD-support-reformatted into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1706
| * Revert "Issue #1699 - Part 3a: mozjemalloc: Memory barriers on ↵Olivier Certner2021-01-07-12/+2
| | | | | | | | | | | | | | | | | | 'malloc_initialized'" This reverts commit f76695c1ce032b634f3e0e2a593aebdd1d49703b. SUSv4 specifies that 'pthread_create' acts as a (full) memory barrier, so barriers here are not necessary.
| * Issue #1699 - Part 3c: mozjemalloc: FreeBSD: Ensure early initializationOlivier Certner2021-01-07-0/+5
| | | | | | | | This guarantees that initialization is done in a single-thread context.
| * Issue #1699 - Part 3b: mozjemalloc: Bootstrap allocator, early diversion for ↵Olivier Certner2021-01-07-42/+294
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FreeBSD Coded a simple memory allocator meant to be used during jemalloc bootstrap (malloc_init_hard()). Although protected by "#ifdef __FreeBSD__", it is not FreeBSD-specific: Any POSIX platform could use it. Hook it so that it is used in place of jemalloc's own routines while malloc_init_hard() is executing or memory for mutexes is being allocated. Currently, 'malloc', 'calloc', '*memalign' and 'free' are diverted during init or lock initializations. Details are quite complex, see the big comment block starting with "There are several problematic interactions between FreeBSD's libthr and this jemalloc." for more explanations. Also replaced ad-hoc BSD code to determine the number of CPUs with 'sysconf', which is POSIX-compliant (and supported on modern BSDs).
| * Issue #1699 - Part 3a: mozjemalloc: Memory barriers on 'malloc_initialized'Olivier Certner2021-01-07-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The barriers are here to make sure that setting 'malloc_initialized' at end of init must be noticed later by any thread running on a different core. They are in theory necessary in the absence of an explicit pthread lock. What could happen is that the thread doing the initialization later spawns other threads that could not have the updated 'malloc_initialized' value, leading to a second initialization. This is dependent on whether OSes force a full memory barrier before the new thread is run, which I don't know, and don't want to bother. This was done for FreeBSD only, for the sake of robustness. In theory, this would be needed on Windows too.
| * Issue #1699 - Part 2: libevent: Remove 'evutil_secure_rng_add_bytes'Olivier Certner2021-01-07-27/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In fact, this is a security threat. This function calls 'arc4random_addrandom', which was removed from the reference implementation 7 years go [1], on the ground that this was in fact an internal interface which is almost impossible to use correctly. This update has since then been propagated to other implementations (e.g., FreeBSD, IllumOS, Android). Do this for all platforms, since 'evutil_secure_rng_add_bytes' is not even used in the current tree, and for the reason stated above, should never be. Related bugs at Mozilla and libevent: Links [2] and [3] below. [1] http://marc.info/?l=openbsd-cvs&m=138238762705209&w=2 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=931354 [3] https://sourceforge.net/p/levent/bugs/320/
| * Issue #1699 - Part 1: python/psutil: Support recent FreeBSD versionsOlivier Certner2021-01-07-13/+76
|/ | | | | | 'sysctl' interface to currently opened connections changed in FreeBSD 12. Drop support for FreeBSD < 9, these are very old and unsupported versions.
* Merge branch '61'Moonchild2021-01-04-20/+834
|\
| * Issue #61 - Add missing external symbols for gkmedias when WebRTC is builtMatt A. Tobin2021-01-04-0/+16
| |
| * Issue #61 - Add missing external symbol cubeb_set_log_callback to gkmedias ↵Matt A. Tobin2021-01-03-0/+1
| | | | | | | | symbols.def
| * Issue #61 - Add configure option for non-windows platformsMatt A. Tobin2021-01-03-4/+17
| | | | | | | | Windows will ALWAYS have this enabled but we eventually want all target operating systems to use this as well but that will require more work
| * Issue #61 - Place Skia in libxulMoonchild2021-01-03-6/+2
| | | | | | | | | | | | | | | | | | | | Skia does some nasty things that break with DLL calls like having virtual dtors without a body definition (and it's honestly surprising that it even builds to begin with the way it's done, but apparently they use some linking symbol voodoo to work around that in dependent classes). Not wanting to have to pull Google code apart to try and fix that for something we're only using for canvas anyway, it's better to just let Skia reside in libxul instead.
| * Issue #61 - Add missing #endif in symbols fileMoonchild2021-01-03-1/+1
| |
| * Issue #61 - Reinstate buildability with shared gkmedias dllMoonchild2021-01-02-16/+804
| | | | | | | | | | This fully works for splitting gkmedias.dll back out from xul with one exception which is Skia throwing undefined externals when linking gkmedias.
* | [NSS hotpatch] Hard disable AVX2 in NSS Build SystemMatt A. Tobin2021-01-03-23/+5
| | | | | | | | This should be ported to the NSS repo
* | Redundant code path cleanup (#1702)Moonchild2021-01-02-297/+91
|/ | | | | | | | | Remove various obsolete configure options. Remove Adjust SDK install tracking filth. Remove redundant code paths in old-configure This also optimizes linker use Remove redundant conditional blocks. Rewrite span.h without constexpr use.
* Issue #1053 - Part 2b: Remove android from /layout reftestsMoonchild2020-12-31-18092/+511
| | | | Also cleans up some other obsolete checks and stylo reftest lists.
* Issue #1053 - Part 3b: Remove AndroidSurfaceTexture and Android media decoderMoonchild2020-12-27-2022/+0
| | | | interface.
* Issue #1053 - Part 3a: Remove Android conditionals from /gfxMoonchild2020-12-27-1708/+32
|
* Issue #1053 - Part 2a: Remove android from /layout (partial)Moonchild2020-12-26-540/+56
| | | | | This removes android code from base, build, forms, generic, inspector, style, printing, tools and xul.
* Issue #1053 - Part 1c: Remove references to mobile/android targets and pathsMoonchild2020-12-25-3636/+8
|
* Issue #1681 - Hard-code FLAC media type association for .flacMoonchild2020-12-24-0/+1
| | | | We don't support AAC outside of OMX at the moment, so oops.
* Revert "Issue #1681 - Hard-code FLAC and AAC media type associations for ↵Moonchild2020-12-24-2/+0
| | | | | | .flac and .aac" This reverts commit a8e90975d0b7fd481b03a862844c65778f402c5e.
* Issue #1681 - Hard-code FLAC and AAC media type associations for .flac and .aacMoonchild2020-12-24-0/+2
|
* Clobber for NSS update.Moonchild2020-12-23-0/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-27 11:59:10 +0000