summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Clobber for NSS update.Moonchild2020-12-02-1/+1
|
* [NSS] Version and build bumpMoonchild2020-12-02-6/+6
|
* [NSS] Update root certificates.Moonchild2020-12-02-1527/+1082
|
* Issue #1684 - Move global user-agent override to networking component.Moonchild2020-12-02-13/+15
| | | | | Since this is a http protocol networking feature, it belongs in the networking branch of our preferences.
* [webrtc] Only init WebRtcAec callbacks onceMoonchild2020-11-19-17/+21
|
* [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.
* [dom] Remove attributes from descendants when setting sanitized style.Henri Sivonen2020-11-19-0/+19
| | | | This avoids a number of problems with incomplete sanitation.
* [http] Use a copy of nsHttpConnectionInfo.Moonchild2020-11-19-7/+8
| | | | | | | The root cause in this bug is that the connection info used by 'SpdyConnectTransaction' is the same instance as the connection info in 'nsHttpTransaction', so we should clone it and let 'SpdyConnectTransaction' use the cloned one.
* [xpcom] Don't use realloc for shrinking nsTArrays when allowRealloc is false.Moonchild2020-11-19-5/+21
| | | | | | | | | The original patch handled the grow case but not the shrink case. When the current and new allocation sizes are in different size classes, jemalloc's realloc will move the allocation when shrinking, not just truncate the existing one. Based on work by Jon Coppeard.
* [parser] Make the refcount of nsHtml5OwningUTF16Buffer atomic.Henri Sivonen2020-11-19-1/+1
|
* [xpcom] Fix GetWindowsFolder storageDavid Major2020-11-19-2/+2
|
* [gfx][Skia] Hold mutex while accessing shared SkImage data.Moonchild2020-11-19-17/+54
|
* Issue #1686 - Align a keybinding definition with the othersAlessio Vanni2020-11-19-1/+1
|
* Issue #1667 - Part 3: Fix OpenGL load and runtime issues on Big SurBrian Smith2020-11-19-7/+40
| | | | | This fix is included in NSPR 4.27 and Mozilla bug 1652330. Also put a main thread check in the cocoa draw callback.
* Issue #1667 - Part 2: Add MacOS 11.0 Big Sur widget compatibilityBrian Smith2020-11-19-609/+286
| | | | | | | This involves refactoring the vibrancy and OpenGL/Pixel rendering changes contained in the following Mozilla meta bugs: 1496823 and 1491445 Also add Big Sur to the features tests and update popup menu look and feel based on Mozilla bug 1656301.
* Issue #1667 - Part 1: Define _pthread_self if it is not already defined in ↵Brian Smith2020-11-19-0/+3
| | | | jemalloc
* [UA] Change default compatibility mode version to 68.0Moonchild2020-11-18-1/+1
| | | | | Since several entities have started to ban .9 versions, even if they are valid ESR versions.
* Issue #251 - Move chrome packaging options to ac configureMatt A. Tobin2020-11-18-34/+86
| | | | Also adds options for new functionality in #1683
* [packager] Optimize archive accesses.Moonchild2020-11-18-30/+107
|
* Issue #1683 - Update libjar module.Moonchild2020-11-18-13/+101
|
* Issue #1683 - Update Brotli lib to 1.0.9Moonchild2020-11-18-2404/+3966
|
* [libjar] Fix inflation logic.Moonchild2020-11-18-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-18-968/+4
|
* Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default.Moonchild2020-11-18-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 #1280 - Follow-up: Get rid of HPKP pinning mode.adesh2020-11-18-42/+14
| | | | | | This was a leftover from HPKP removal. Also remove a couple of unused variables from security/manager/ssl/nsSiteSecurityService.cpp.
* Bug 1466909 - Use AddLvalueReference for UniquePtr's operator*().Matt A. Tobin2020-11-18-1/+1
| | | | | | | | This is required for UniquePtr to accept <void>, which is required for PseudoHandle = mozilla::UniquePtr<T, JS::FreePolicy>; in turn for mozilla::SegmentedVector<PseudoHandle<void>> uniquePtrArena_; Tag #1679
* Bug 1328948 - Add is(), as() to Cell.Matt A. Tobin2020-11-18-0/+18
| | | | Tag #1679
* Issue #1673 - Part 5: Fix brace style and missed -moz-tab-size reference.athenian2002020-11-18-255/+212
|
* Issue #1673 - Part 4: Unprefix -moz-tab-size.athenian2002020-11-18-10/+38
| | | | While we do fail a couple of tests, the other mainstream browsers also fail them and I think our implementation of tab-size is good enough to be unprefixed at this point. Having this patch also makes testing easier.
* Issue #1673 - Part 3: Bring minimum tab advance up to spec.athenian2002020-11-18-11/+30
| | | | This provides a clearer rule for the minimum tab advance that brings us to alignment with the spec and both major browsers.
* Issue #1673 - Part 2: Make tab-size animatable and fix typos.athenian2002020-11-18-10/+7
| | | | There were a few typos in the previous patch and this patch also makes tab-size animatable which didn't really require much of a change at all.
* Issue #1673 - Part 1: Allow tab-size to accept <length>.athenian2002020-11-18-62/+124
| | | | Currently -moz-tab-size only accepts <number> values, and both Chrome and Firefox currently support <length> values and have for some time now. So with this you would be able to support sizes in px or em, for instance. This was implemented in Firefox 53 and was trivial to backport.
* [devtools] More gracefully (than a crash) handle stack capture failures.Moonchild2020-10-31-1/+3
|
* Update docs for change of repository host.Moonchild2020-10-24-1/+1
| | | | Rename MCP back to MoonchildProductions.
* Update docs for change of repository host.Moonchild2020-10-24-2/+2
|
* [layout] Re-order rowgroups if reflowing.Moonchild2020-10-24-2/+14
| | | | This logic was missing for tfoot. See existing code in second hunk.
* [layout] Avoid negative availSize.BSizes in paginated table reflow.Moonchild2020-10-24-9/+11
|
* Bump platform version for added features.Moonchild2020-10-24-1/+1
|
* [netwerk] Make nsIncrementalStreamLoader's GetNumBytesRead threadsafe.Moonchild2020-10-24-10/+14
| | | | | | | This prevents a potential race and simplifies the code a bit by keeping the bytes read separate instead of using mData, which is modified from another thread from OnDataAvailable. Relaxed atomics are fine for these, since they don't guard any memory.
* [DOM] When failing to create a channel and an image request, make sure to setMoonchild2020-10-24-1/+9
| | | | | | | the image blocking status appropriately. This is the same status as we do for known no-data protocols and ensures we treat these two cases the same.
* [DOM Fetch] Detect broken pipes and propagate that write error to the caller.Moonchild2020-10-24-0/+11
|
* [DOM Fetch] Improve stability of Fetch API.Moonchild2020-10-24-4/+9
|
* Issue #1671 - Unprefix ::-moz-selectionMoonchild2020-10-24-5/+17
| | | | | | | | This actually keeps both pseudo-elements for now, since the prefixed version is still used internally, but we need the unprefixed version for web compat. Note: while unprefixing a non-spec-compliant pseudo here, it's exactly in line with what other browsers do. Nobody is following the spec here and at least we'll be doing what everyone else is with our unprefixed version.
* Issue #1668 - Part 2: Visited color and auto support for caret-color property.athenian2002020-10-24-8/+27
| | | | Mozilla's original implementation of this failed a couple of tests, but this seems to solve all the problems. Basically, the caret-color wasn't able to be set differently based on whether a link was visited, and the auto value implementation was incomplete. The only test we fail now is the one where you have grey text on a grey background and the caret is supposed to be visible, but I think that may have been removed from the spec. Even if it wasn't, no other browser supports it anyway.
* Issue #1668 - Part 1: Implement support for caret-color property.athenian2002020-10-24-11/+118
| | | | | | This CSS property allows input carets (that blinking input cursor you see in text fields), to be given a custom color. This was implemented in Firefox 53, and it was such a minor feature that no one ever missed it, but I don't see any harm in implementing this. https://bugzilla.mozilla.org/show_bug.cgi?id=1063162
* Issue #1643 - Follow-up: Ensure we properly clear our pointers when theMoonchild2020-10-24-9/+24
| | | | Presentation of a document is destroyed.
* Issue #1606 - Add support for multi-monitor DPI awareness v2 (W10 1706+)Moonchild2020-10-06-11/+33
|
* [devtools] Teach devtools about overflow-wrap: anywhereMoonchild2020-10-06-0/+2
| | | | Tag #1666
* Issue #1666 - Implement overflow-wrap: anywhereMoonchild2020-10-06-4/+11
| | | | | | | This aligns with the current spec regarding overflow-wrap: break-word and overflow-wrap: anywhere in if it affects intrinsic sized due to considering soft-wrap opportunities or not. See CSS Text Module Level 3, Editor’s Draft, 1 October 2020, Section 5.5
* Issue #1665 - Take overflow-wrap into account when calculating min-content ↵Moonchild2020-10-06-0/+44
| | | | intrinsic size.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 22:46:21 +0000