c84a0cd61b682b11c2a3a2b2adc5b87011241aa2: Bug 1479528: Remove FrameConstructionItem::mIsForSVGAElement. r=bz
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 30 Jul 2018 20:13:46 +0200 - rev 826242
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479528: Remove FrameConstructionItem::mIsForSVGAElement. r=bz It was needed presumably because XBL could override the tag name and what not. But I removed that capability for elements other than XUL elements, so we can just poke at the content directly. Differential Revision: https://phabricator.services.mozilla.com/D2520 MozReview-Commit-ID: B5Ihu0gaNd8
5947eab0392411a7d710225b0d2b635dcf550f0e: Bug 1479528: Move all the data-finding related stuff into a single function. r=dholbert
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 31 Jul 2018 14:44:45 +0200 - rev 826241
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479528: Move all the data-finding related stuff into a single function. r=dholbert To make it hopefully a bit easier to follow. Differential Revision: https://phabricator.services.mozilla.com/D2564 MozReview-Commit-ID: 2LMf7IXM1kr
935ad68fc5db5270bd95b3f5ee37ad086b0b2626: Bug 1479528: Move the XBL binding loads a bit more away. r=dholbert
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 31 Jul 2018 14:42:26 +0200 - rev 826240
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479528: Move the XBL binding loads a bit more away. r=dholbert They're pretty ugly... Differential Revision: https://phabricator.services.mozilla.com/D2563 MozReview-Commit-ID: CUDUyfe9Bgp
cd23a7207dbbec30a3d1682d678ed76d73a6248b: Bug 1479528: Make the ShouldSuppressFrameIn* functions take references. r=dholbert
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 31 Jul 2018 14:36:39 +0200 - rev 826239
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479528: Make the ShouldSuppressFrameIn* functions take references. r=dholbert Differential Revision: https://phabricator.services.mozilla.com/D2562 MozReview-Commit-ID: 8lcn1XW4aik
3f58dc7309e39047199a848db90d9ce940308505: Bug 1480354 - Better approach for nested blobs construction, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Fri, 03 Aug 2018 08:58:32 +0200 - rev 826238
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480354 - Better approach for nested blobs construction, r=smaug
56cd87390012d2959066c06a33e968ffea544e07: Bug 1480364 - AbortSignal doesn't need to keep alive AbortController, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Fri, 03 Aug 2018 07:06:16 +0200 - rev 826237
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480364 - AbortSignal doesn't need to keep alive AbortController, r=smaug
3686ee636ac2a7ff2a37318b93fcaea1ac605c51: Bug 1479010 - don't populate a ScaledFont's cairo scaled font unless targeting cairo. r=jrmuizel
Lee Salzman <lsalzman@mozilla.com> - Fri, 03 Aug 2018 00:56:06 -0400 - rev 826236
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479010 - don't populate a ScaledFont's cairo scaled font unless targeting cairo. r=jrmuizel
2d7701c11a218faaaddb1acc9dff6ad12cafe7ae: Bug 1480660 - Remove ConstExprHash{UntilZero,String}(). r=froydnj
Nicholas Nethercote <nnethercote@mozilla.com> - Fri, 03 Aug 2018 14:47:41 +1000 - rev 826235
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480660 - Remove ConstExprHash{UntilZero,String}(). r=froydnj They were workarounds for bugs in GCC 4.9, which is no longer supported.
2058357d242cd5a8e87ed7507478790541473e80: Bug 1470910 - Migrate input-box and input-box-spell to a Custom Element;r=paolo
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 02 Aug 2018 20:53:59 -0700 - rev 826234
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1470910 - Migrate input-box and input-box-spell to a Custom Element;r=paolo Instead of `<xul:hbox class="textbox-input-box">`, consumers now should use `<xul:moz-input-box />`. This covers the normal case and also handles [spellcheck=true] while sharing much of the code within one class. MozReview-Commit-ID: DjvT8sFq3SQ
e123d0aa911c4fa3501042d2febecac1a2766b60: Bug 1479569 part 3. Remove nsIContentFrameMessageManager. r=kmag
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 02 Aug 2018 23:49:09 -0400 - rev 826233
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479569 part 3. Remove nsIContentFrameMessageManager. r=kmag
b828a58404e548fc88b551e4df66c72baf6787b6: Bug 1479569 part 2. Use the new messageManager getter on docshell. r=kmag
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 02 Aug 2018 23:49:09 -0400 - rev 826232
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479569 part 2. Use the new messageManager getter on docshell. r=kmag I generally tried to preserve the behavior of consumers where they treated an exception from getInterface(Ci.nsIContentFrameMessageManager) as a signal to use some sort of fallback. I did change the behavior of consumers that walked up to the root same-type docshell before getting the message manager to just get it directly from the docshell they have. Please review those parts carefully, and let me know if you want me to ask some subject area experts to review those.
97041ef8f3117925f75b6b5f7c5e97da7ba54e04: Bug 1479569 part 1. Add a ContentFrameMessageManager getter on nsIDocShell. r=kmag
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 02 Aug 2018 23:49:09 -0400 - rev 826231
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1479569 part 1. Add a ContentFrameMessageManager getter on nsIDocShell. r=kmag
6c0410ddd1f6950a7398321c10b520ac1d378ed2: Bug 1480361 - Introduce HashTable::LookupReason. r=luke
Nicholas Nethercote <nnethercote@mozilla.com> - Fri, 03 Aug 2018 10:03:37 +1000 - rev 826230
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480361 - Introduce HashTable::LookupReason. r=luke Again inspired by PLDHashTable, this makes things a bit clearer than passing 0 or sCollisionBit. It also guarantees more strongly that we'll end up with appropriately specialized code for the Add vs. NonAdd cases. (That guarantee isn't currently needed because the compiler inlines things sufficiently anyway, but it can't hurt.)
d9baec9cf420acf68530b10bca19f67b72e3cb2b: Bug 1480361 - Tweak handling of removed entries in HashTable::lookup(). r=luke
Nicholas Nethercote <nnethercote@mozilla.com> - Fri, 03 Aug 2018 10:03:31 +1000 - rev 826229
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480361 - Tweak handling of removed entries in HashTable::lookup(). r=luke There are two improvements here. - When we're just doing a lookup (i.e. aCollisionBit==0), we don't need to do any special handling of removed entries. (Inlining means that the removed entry code is entirely removed for lookups.) - When we're doing an insertion (i.e. aCollisionBit==sCollisionBit), we now stop adding collision markings once we find a removed entry, because they're unnecessary after that point. This change brings the code in alignment with PLDHashTable::SearchTable().
d4ca2c8982afbcac4494d91b65cff5c64e59498a: Bug 1478563 - Re-use function objects in MeatballMenu; r=jdescottes
Brian Birtles <birtles@gmail.com> - Thu, 02 Aug 2018 10:09:11 +0900 - rev 826228
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1478563 - Re-use function objects in MeatballMenu; r=jdescottes To avoid needless re-renders due to props changing object identity. Differential Revision: https://phabricator.services.mozilla.com/D2641
2d0225ff21ff1238cf61e4a3c239dd89b7b7fc25: Bug 1474234 - Don't pass internal props onto child button in MenuButton; r=jdescottes
Brian Birtles <birtles@gmail.com> - Thu, 02 Aug 2018 09:59:24 +0900 - rev 826227
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1474234 - Don't pass internal props onto child button in MenuButton; r=jdescottes Otherwise we will get errors like: console.error: "Warning: React does not recognize the `menuId` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `menuid` instead. If you accidentally passed it from a parent component, remove it from the DOM element.\n in button (created by MenuButton)\n in MenuButton (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in ToolboxToolbar (created by ToolboxController)\n in ToolboxController" console.error: "Warning: React does not recognize the `menuPosition` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `menuposition` instead. If you accidentally passed it from a parent component, remove it from the DOM element.\n in button (created by MenuButton)\n in MenuButton (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in ToolboxToolbar (created by ToolboxController)\n in ToolboxController" console.error: "Warning: React does not recognize the `menuOffset` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `menuoffset` instead. If you accidentally passed it from a parent component, remove it from the DOM element.\n in button (created by MenuButton)\n in MenuButton (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in div (created by ToolboxToolbar)\n in ToolboxToolbar (created by ToolboxController)\n in ToolboxController" It's also not what we intend to do. Differential Revision: https://phabricator.services.mozilla.com/D2640
4c9740da28ee579f62463510226f405711b33b5e: Bug 1474234 - Add keys for MeatballMenu and MenuItem children; r=jdescottes
Brian Birtles <birtles@gmail.com> - Thu, 02 Aug 2018 09:41:47 +0900 - rev 826226
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1474234 - Add keys for MeatballMenu and MenuItem children; r=jdescottes Differential Revision: https://phabricator.services.mozilla.com/D2639
c6d07c3eec16e02846db3abadd7844c4fa4c4c13: Bug 1480553 - part 3 - add mappings for aarch64 in Windows configure paths; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 21:40:40 -0400 - rev 826225
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480553 - part 3 - add mappings for aarch64 in Windows configure paths; r=glandium We need to add mappings for target.cpu to MSVC's arm64 name for determining various paths, and we need to add an extra case to get_vc_paths so the compiler can find all the necessary DLLs.
d87760979a3eccce946f59ade6a145251c04a8ba: Bug 1480553 - part 2 - add a case for aarch64* when setting MIDL_FLAGS; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 21:40:40 -0400 - rev 826224
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480553 - part 2 - add a case for aarch64* when setting MIDL_FLAGS; r=glandium
4dbeee9501bdd367b73d353075a98521015238a4: Bug 1480553 - part 1 - add Windows-specific aarch64 macro detection; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 21:40:40 -0400 - rev 826223
Push 118275 by bmo:dharvey@mozilla.com at Fri, 03 Aug 2018 11:44:33 +0000
Bug 1480553 - part 1 - add Windows-specific aarch64 macro detection; r=glandium MSVC doesn't define __aarch64__, but uses its own symbol instead.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip