062f02943785599a074e4b0fa4a9ed3a3d8c5d04: Bug 1660555 - Move traverse/unlink operations on |AbortFollower| and |AbortSignalImpl| into static member functions. r=smaug
Jeff Walden <jwalden@mit.edu> - Thu, 29 Oct 2020 08:02:58 +0000 - rev 555010
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1660555 - Move traverse/unlink operations on |AbortFollower| and |AbortSignalImpl| into static member functions. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D92322
29e0a26dc84a1d85a1554e62bce480ea7d2be4c1: Bug 1660555 - Make |AbortFollower| actually inherit from |nsISupports|. r=smaug
Jeff Walden <jwalden@mit.edu> - Thu, 29 Oct 2020 08:02:05 +0000 - rev 555009
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1660555 - Make |AbortFollower| actually inherit from |nsISupports|. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D92323
463a8e88c16a62e78f6e0396befec0c4101af688: Bug 1660555 - Add a |Signal()| accessor to |AbortFollower| rather than directly accessing an inherited, protected member. r=smaug
Jeff Walden <jwalden@mit.edu> - Thu, 29 Oct 2020 08:03:27 +0000 - rev 555008
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1660555 - Add a |Signal()| accessor to |AbortFollower| rather than directly accessing an inherited, protected member. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D93888
97d7b670f0999ffd4d4e6f62acd5b6a54a622753: Bug 1121822 - Remove NS_ENABLE_TSF r=m_kato,masayuki
Kagami Sascha Rosylight <krosylight@mozilla.com> - Thu, 29 Oct 2020 01:46:05 +0000 - rev 555007
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1121822 - Remove NS_ENABLE_TSF r=m_kato,masayuki Differential Revision: https://phabricator.services.mozilla.com/D95037
8f0fadc9e78b9d155e833f3b25d940e13cb7fed9: Backed out changeset 7c2ee39c8744 (bug 1673818) for causing sm build bustages in MacroAssembler-arm64. CLOSED TREE
smolnar <smolnar@mozilla.com> - Thu, 29 Oct 2020 09:26:35 +0200 - rev 555006
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Backed out changeset 7c2ee39c8744 (bug 1673818) for causing sm build bustages in MacroAssembler-arm64. CLOSED TREE
7c2ee39c8744463b3075270d4b0e1a922a96591f: Bug 1673818 - Decouple memory limit from buffer limit, clarify 32-bit memories. r=rhunt
Lars T Hansen <lhansen@mozilla.com> - Thu, 29 Oct 2020 06:53:36 +0000 - rev 555005
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1673818 - Decouple memory limit from buffer limit, clarify 32-bit memories. r=rhunt This patch does two intertwined things: - it clarifies throughout that the wasm memories we are currently using are 32-bit memories by adding '32' in a number of names and introducing a MemoryKind enum that is (for now) used to carry the type of memory we have. Some of this may be a little superflous at the moment but will matter once we start using size_t for the heap limit, and the clarity will be useful going forward. - it stops using the MaxBufferByteLength for anything to do with memory length checking, instead introducing checks against a limit derived from MaxMemory32Pages where that is appropriate. All remaining uses of MaxBufferByteLength are strictly about the buffer maximum, not the memory's maximum. There are two (mutually referencing) FIXMEs left in the patch, both pertaining to adaptations that should be made when the ArrayBuffer can grow beyond INT32_MAX. Differential Revision: https://phabricator.services.mozilla.com/D94938
0cb4b08cc6bfd4bf71414f4b8bd9dc64a4ca2af4: Bug 1672619 - Narrow ifdefs so as to allow OpenBSD compilation. r=rhunt
Lars T Hansen <lhansen@mozilla.com> - Thu, 29 Oct 2020 06:53:29 +0000 - rev 555004
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1672619 - Narrow ifdefs so as to allow OpenBSD compilation. r=rhunt Patch by Landry Breuil (landry@openbsd.org) The ifdefs in MozCpu-vixl.cpp need to be narrower to allow compilation on OpenBSD. I think the new problem is probably a regression resulting from work Benjamin did recently to deal with the simulator's icache flushing logic. Differential Revision: https://phabricator.services.mozilla.com/D95004
cc07e95f3b1492a7d29fa5cfe692468d91222a0f: Bug 1664397 - Improve simd constant loads. r=jseward
Lars T Hansen <lhansen@mozilla.com> - Thu, 29 Oct 2020 06:56:56 +0000 - rev 555003
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1664397 - Improve simd constant loads. r=jseward Improve VIXL simd constant generation by recognizing when the high 64 bits are the same as the low 64 bits and not generating extra code in that case; the setup of the low 64 bits always duplicates the value into the high 64 bits as well. Differential Revision: https://phabricator.services.mozilla.com/D94584
0da87b2cdba5fadd2691d7dda78f5ada91923f4d: Bug 1673391 - Translate swizzle-with-constant into shuffle. r=jseward
Lars T Hansen <lhansen@mozilla.com> - Thu, 29 Oct 2020 06:55:26 +0000 - rev 555002
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1673391 - Translate swizzle-with-constant into shuffle. r=jseward There's discussion on the SIMD tracker to the effect that producers prefer to emit a swizzle operation with a v128.const mask to express a permutation instead of a two-argument shuffle (both arguments being the same input) with an immediate mask. The stack nature of wasm and the lack of a DUP instruction reinforces this choice. Thus we should recognize a swizzle-with-const as an expression of shuffle-with-zero, with subsequent optimizations applied to the shuffle. Differential Revision: https://phabricator.services.mozilla.com/D94742
881ae1132d3b01e5b7b23fbdf0a89c8fcaef8a79: Bug 1664941: Connect style actor and stylesheet watcher. r=jdescottes
Daisuke Akatsuka <daisuke@birchill.co.jp> - Thu, 29 Oct 2020 06:26:20 +0000 - rev 555001
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1664941: Connect style actor and stylesheet watcher. r=jdescottes Differential Revision: https://phabricator.services.mozilla.com/D90651
41d5f76883953154d9a53e09f805e1ce15cb57c9: Bug 1673919: Make ParagraphBoundaryRule skip over OuterDocAccessibles. r=MarcoZ
James Teh <jteh@mozilla.com> - Thu, 29 Oct 2020 06:04:33 +0000 - rev 555000
Push 37902 by ccoroiu@mozilla.com at Thu, 29 Oct 2020 15:52:12 +0000
Bug 1673919: Make ParagraphBoundaryRule skip over OuterDocAccessibles. r=MarcoZ The browser test is really a crash test, but it's really difficult to test a11y APIs properly using the crashtest framework. Differential Revision: https://phabricator.services.mozilla.com/D95107
3d5f376d44e0af99365a1372893c79ce5002711e: Merge autoland to mozilla-central. a=merge
smolnar <smolnar@mozilla.com> - Thu, 29 Oct 2020 11:49:46 +0200 - rev 554999
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Merge autoland to mozilla-central. a=merge
ff7124e703ef86512c34b62b080b0381a55963be: Bug 1674033 - Remove files in order to unbust win asan reporter. r=jwalden
Cosmin Sabou <csabou@mozilla.com> - Thu, 29 Oct 2020 02:55:42 +0000 - rev 554998
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1674033 - Remove files in order to unbust win asan reporter. r=jwalden Differential Revision: https://phabricator.services.mozilla.com/D95102
e7f1f7237720f49a9f0b1df1cf5f9ff875bbff94: Bug 1674000 - Use better colors for the search mode indicator in Windows high-contrast themes. r=ntim
Drew Willcoxon <adw@mozilla.com> - Thu, 29 Oct 2020 02:11:45 +0000 - rev 554997
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1674000 - Use better colors for the search mode indicator in Windows high-contrast themes. r=ntim Here's what this looks like in all of Windows 10's high-contrast themes. I tried keeping the border the same color as the text but I don't think it looked good, so I made it the same color as the background. {F2546521} Differential Revision: https://phabricator.services.mozilla.com/D95095
95bbb11ae3badfea80418d92717c7a23971bc3e8: Bug 1674031 - Clean up URL search mode indicator CSS. r=adw
Tim Nguyen <ntim.bugs@gmail.com> - Thu, 29 Oct 2020 02:11:45 +0000 - rev 554996
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1674031 - Clean up URL search mode indicator CSS. r=adw Differential Revision: https://phabricator.services.mozilla.com/D95099
dcb0a318d44df213f64330ce18e405e27585b74c: Bug 1673790 - Split `editor/libeditor/HTMLEditSubActionHandler.cpp` r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 28 Oct 2020 13:08:34 +0000 - rev 554995
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1673790 - Split `editor/libeditor/HTMLEditSubActionHandler.cpp` r=m_kato It's too big (+15k lines) and there are 2 groups which does not depend on the others. One is getting current state for `Document.queryCommandState` etc. This is copied to `HTMLEditorState.cpp`. And the other is delete handlers. This is copied to `HTMLEditorDeleteHandler.cpp`. Differential Revision: https://phabricator.services.mozilla.com/D94934
7a7cc42e5ff80dc207c8862ff13393e7baca3831: Bug 1638986 - Run 'mach talos-test' with python 3; r=sparky,perftest-reviewers
Geoff Brown <whole.grains@protonmail.com> - Thu, 29 Oct 2020 00:23:51 +0000 - rev 554994
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1638986 - Run 'mach talos-test' with python 3; r=sparky,perftest-reviewers Differential Revision: https://phabricator.services.mozilla.com/D94770
1acd12e7660e8791dce1ac8929018380df6b2025: Bug 1660054 - Hook up the zoom-reset action to also reset APZ/scaling zoom. r=Gijs,nika,botond
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 28 Oct 2020 22:48:57 +0000 - rev 554993
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1660054 - Hook up the zoom-reset action to also reset APZ/scaling zoom. r=Gijs,nika,botond The goal here is to hook up the ctrl+0 keyboard shortcut to reset the scaling zoom applied by pinch gestures (on touchscreen or trackpad), in addition to resetting the reflow zoom (aka full zoom). This patch also makes other mechanisms to reset the reflow zoom (e.g. clicking on the "100%" label in the hamburger menu) also reset scaling zoom, which I think makes sense for consistency. Most of this patch is just plumbing, but I'm unfamiliar with these codepaths so requesting review from relevant owners to make sure it's sane. Differential Revision: https://phabricator.services.mozilla.com/D94624
cf70edfb90e95bf7444772720254471f887a2547: Bug 1664558 - Improve layers id logging in layer tree. r=botond
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 28 Oct 2020 22:06:57 +0000 - rev 554992
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1664558 - Improve layers id logging in layer tree. r=botond Depends on D94894 Differential Revision: https://phabricator.services.mozilla.com/D94895
66d877d0037e9e22846e34321e8aeba626966360: Bug 1664558 - Propagate the layers id from InputData to gecko WidgetEvent types. r=botond
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 28 Oct 2020 22:02:00 +0000 - rev 554991
Push 37901 by smolnar@mozilla.com at Thu, 29 Oct 2020 09:56:39 +0000
Bug 1664558 - Propagate the layers id from InputData to gecko WidgetEvent types. r=botond Seems like an oversight that these fields were never propagated from APZ to the generated main-thread WidgetEvents. Differential Revision: https://phabricator.services.mozilla.com/D94894
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip