searching for reviewer(billm)
3ba34ca57b5b5c73a07a026a6103cbc7394c2207: Bug 1353767 - BufferList methods that can OOM should all be MOZ_MUST_USE. r=billm
dOn'tReallycAre <vadfgsvrtascas@yahoo.com.tw> - Tue, 26 Mar 2019 13:24:00 +0200 - rev 466270
Push 35763 by csabou@mozilla.com at Wed, 27 Mar 2019 04:45:26 +0000
Bug 1353767 - BufferList methods that can OOM should all be MOZ_MUST_USE. r=billm The Pickle methods can use MOZ_ALWAYS_TRUE because the BufferList is infallible, so the WriteBytes calls will never fail.
34cf0986960016de09041a9c8b62a0f8173ffd83: Bug 1207696 Part 1e - Disable crash reporting when recording/replaying, r=billm.
Brian Hackett <bhackett1024@gmail.com> - Mon, 23 Jul 2018 14:33:42 +0000 - rev 427868
Push 34320 by rgurzau@mozilla.com at Tue, 24 Jul 2018 09:50:07 +0000
Bug 1207696 Part 1e - Disable crash reporting when recording/replaying, r=billm.
92fc9eca3135c077362eec871fb0015b1440f552: Bug 1207696 Part 10g - Initialize replay-specific and middleman state, r=billm.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:40:24 +0000 - rev 427716
Push 34314 by csabou@mozilla.com at Mon, 23 Jul 2018 09:31:12 +0000
Bug 1207696 Part 10g - Initialize replay-specific and middleman state, r=billm.
03c14ea47865f40b1da9a30191d9948ee07e49aa: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 401652
Push 33351 by btara@mozilla.com at Wed, 31 Jan 2018 10:00:45 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v (grafted from 308a4ed50826254e195fa2f4a14334d4114bd1f9)
4efc37f978d2817177068b0df224fcdc3abebeee: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 399671
Push 33272 by toros@mozilla.com at Wed, 17 Jan 2018 21:48:44 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
a30d2216e0b9c8fc902f5e1704eafabab828fcff: Bug 1373708 - Part 2: Wait until all tabs are closed. r=billm
Liang-Heng Chen <xeonchen@gmail.com> - Thu, 07 Sep 2017 18:16:00 -0400 - rev 398659
Push 33228 by aciure@mozilla.com at Thu, 11 Jan 2018 09:55:35 +0000
Bug 1373708 - Part 2: Wait until all tabs are closed. r=billm MozReview-Commit-ID: 2Ky8t2jpDyY
2cfdaedf635996efdc462bb12d5075b84b3e93e8: Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r=billm
Mike Conley <mconley@mozilla.com> - Thu, 21 Dec 2017 13:40:52 -0500 - rev 398054
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r=billm During the macOS fullscreen mode change, the window entering fullscreen reports being occluded for a brief time (presumably due to the "stretch" effect that macOS is applying overtop of the window). This causes us to preserve the layers for the selected tab, and deactivate its docShell. According to https://bugzilla.mozilla.org/show_bug.cgi?id=1279086#c34, we preserve layers like this when minimizing or fully occluding the window. This way, we avoid a flicker when the window is un-minimized or partially revealed. However, if during that transition, the mouse hovers over a background tab (which is the case during the automated tests) and an async tab switcher doesn't already exist, we can trigger a warming attempt on that background tab, which creates an async tab switcher, and causes the switcher to run its init() method. Beyond setting some initial state, the init() method also makes it so that the initial browser at the time of calling init() sets preserve layers to false. If we get into this situation, then what we end up with is a tab that is rendering layers, is no longer preserving them, but the docShell is not activated. Soon after, the async tab switcher responds to the occlusionstatechange event when the window is revealed again. Before this patch, we did nothing, since it was assumed that postActions would eventually activate the docShell. However, since warming isn't currently activated by default, the async tab switcher soon destroys itself, and the initial tab's docShell is never activated. This causes the browser_domFullscreen_fullscreenMode.js test to hang (and probably other bugs as well). This patch makes it so that if we see an occlusionstatechange or sizemodechange event when the async tab switcher exists, and the window is no longer minimized or fully occluded, that we attempt to activate the currently selected tab's docShell. MozReview-Commit-ID: yJTUj8bBrs
c592bf74cad182c919e808892c1ee3859fb38d53: Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 19 Dec 2017 08:44:18 -0800 - rev 398053
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
8605e2ebcc92df713072d4923ecc21c5a62fa827: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 398052
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm Calling GetPresShell() might create a content viewer, which might cause script to run. This is bad if there's a ForcePaint message queued up, because it could mean running the force painting code while we're still in the midst of making a tab hidden, which would put us in an inconsistent state. MozReview-Commit-ID: 3rw2wGllGdk
707a2b0aede11d52aa5ab818a975170f894ba550: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 398051
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm This assumption also mirrors how non-remote browsers have their docShells active by default. In order to do this, I also have to increase the initial epoch's for the TabParent and TabChild, as if a RenderLayers has been called. Originally, since the epochs initted at 0, and the epochs stored by the [Layer|WebRender]TransactionParent were also initted at 0, we'd hit this branch: https://searchfox.org/mozilla-central/rev/c633ffa4c4611f202ca11270dcddb7b29edddff8/gfx/layers/ipc/LayerTransactionParent.cpp#703 and then we'd never alert the TabParent about the layer upload. MozReview-Commit-ID: 6PP1eCnisYK
3fa35817d29d5fe75e59f92cb794dcd6adb4f9b4: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 398050
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm This is necessary because sometimes the async tab switcher will instantiate when there already exists some background tabs that are rendering via print preview. When that happens, it's important for the state to be set correctly for them so that we don't accidentally treat them as still loading, and wait (forever) for them to report having finished loading. MozReview-Commit-ID: 2dwo5WlXlgJ
f6e07e9760454bdb813ab63b1c5b15d4d6ff259f: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 398049
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm Tab warming was originally disabled in this test because it was accidentally setting the DocShell to be active at an unexpected time. Because tab warming no longer activates DocShells, we can revert this change, though we also have to make it deal with the fact that switching tabs no longer makes docShells become activate immediately. MozReview-Commit-ID: K0fiA5AVfEm
d39683d8f79f01c24b34625988e0ba39535bf587: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 398048
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm MozReview-Commit-ID: KWwDee0ujR
44d6efb9fa693766d667adb95281edbc9954d16d: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 398047
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm MozReview-Commit-ID: Go2EdMXGwa7
f77d887fffcb7cef5ddb5c224639496cc77aac75: Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 11:27:29 -0400 - rev 398046
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm MozReview-Commit-ID: 1bBNwew7uCk
4dd5d1624aba5390d015023c9d836f12bf5f3d16: Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 07 Nov 2017 15:08:47 -0500 - rev 398045
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm MozReview-Commit-ID: 7UT036vUY85
7dc566272fee7b5bb2e16ed0e3277915fb792e59: Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:21:34 -0800 - rev 398044
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm MozReview-Commit-ID: KTDhXM7PRdc
b0c38584a789814fc80bfd3c139e23d7ab193417: Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:05 -0400 - rev 398043
Push 33200 by apavel@mozilla.com at Sat, 06 Jan 2018 09:49:11 +0000
Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm Originally, setting the active state on the DocShell for remote browsers also did the work of making the TabChild render its layers and upload them to the compositor. This patch adds a new renderLayers method to nsITabParent which allows more fine-grained control - we can now, for example, cause layers to be rendered and uploaded without activating the DocShell. Note that if one activates or deactivates the DocShell, we'll still do the work of attempting to render / clear the layers if it hasn't already been done. MozReview-Commit-ID: KkLaMDTzfHi
0f87d8c908c39aed95ce68bc021e168fc69ebca2: Bug 1422649 - Remove a bogus exception from the early pref access checking. r=billm
Nicholas Nethercote <nnethercote@mozilla.com> - Mon, 04 Dec 2017 12:08:43 +1100 - rev 396817
Push 33112 by dluca@mozilla.com at Tue, 19 Dec 2017 10:10:10 +0000
Bug 1422649 - Remove a bogus exception from the early pref access checking. r=billm New content processes get prefs in three ways. - They read them from greprefs.js, prefs.js and other such files. - They get sent "early prefs" from the parent process via the command line (-intPrefs/-boolPrefs/-stringPrefs). - They get sent "late prefs" from the parent process via IPC message. (The latter two are necessary for communicating prefs that have been added or modified in the parent process since the file reading occurred at startup.) We have some machinery that detects if a late pref is accessed before the late prefs are set, which is good. But it has a big exception in it; late pref accesses that occur early via Add*VarCache() and RegisterCallbackAndCall() are allowed. This exception was added in bug 1341414. The description of that bug says "We should change AddBoolVarCache so that it doesn't look at the pref in the content process until prefs have been received from the parent." Unfortunately, the patch in that bug added the exception to the checking without changing Add*VarCache() in the suggested way! This means it's possible for late prefs to be read early via VarCaches (or RegisterCallbackAndCall()) when their values are incorrect, which is bad. Changing Add*VarCache() to delay the reading as bug 1341414 originally suggested seems difficult. A simpler fix is to just remove the exception in the checking and extend the early prefs list as necessary. This patch does that, lengthening the early prefs list from ~210 to ~300. Fortunately, most (all?) of the added prefs are ints or bools rather than strings, so it doesn't increase the size of the command line arguments for content processes by too much.
003d418a3516b9fffc40f4a5f6f9f6e75f2de448: Bug 1407878 - P2. Add PLoginReputation.ipdl for LoginReputationService. r=billm,francois
DimiL <dlee@mozilla.com> - Thu, 07 Dec 2017 16:32:52 +0800 - rev 396441
Push 33092 by nbeleuzu@mozilla.com at Fri, 15 Dec 2017 01:43:44 +0000
Bug 1407878 - P2. Add PLoginReputation.ipdl for LoginReputationService. r=billm,francois Right now the only parameter will be sent via the IPC message is form URI. IPC is triggered when a password field is focusd (See P2.) MozReview-Commit-ID: J8lVwRhTFIr
ea64f1bb6c97bfc9437a8841b1d9a2bc54938016: Bug 1372476 - Add event load listener before start loading in docshell/test/browser/browser_bug349769.js. r=billm
Tooru Fujisawa <arai_a@mac.com> - Sun, 10 Dec 2017 20:12:11 -0600 - rev 396030
Push 33068 by toros@mozilla.com at Mon, 11 Dec 2017 09:57:17 +0000
Bug 1372476 - Add event load listener before start loading in docshell/test/browser/browser_bug349769.js. r=billm
8f36094d67c5faf0d91a258b6dcb51d7fc8fdd94: Bug 1424090 - Use dedicated observer notification instead of domwindowclosed to catch onClosed in testcases for SessionStore.jsm. r=billm
Tooru Fujisawa <arai_a@mac.com> - Sat, 09 Dec 2017 09:52:33 -0600 - rev 395925
Push 33059 by apavel@mozilla.com at Sat, 09 Dec 2017 20:22:52 +0000
Bug 1424090 - Use dedicated observer notification instead of domwindowclosed to catch onClosed in testcases for SessionStore.jsm. r=billm
e441cdecaa27e4ed7638f1b12fc376e6fab4d1b6: Bug 1228841 - Part 0: Remove remaining conditional catch consumers in dom/. r=billm
Tooru Fujisawa <arai_a@mac.com> - Tue, 05 Dec 2017 09:42:37 +0900 - rev 395318
Push 33038 by dluca@mozilla.com at Wed, 06 Dec 2017 22:02:18 +0000
Bug 1228841 - Part 0: Remove remaining conditional catch consumers in dom/. r=billm
9651b5f82d299c7d7b043ea9dbdbd3b783af0e8a: Bug 1228841 - Part 0: Remove remaining conditional catch consumers in dom/. r=billm
Tooru Fujisawa <arai_a@mac.com> - Tue, 05 Dec 2017 09:42:37 +0900 - rev 394963
Push 33026 by shindli@mozilla.com at Tue, 05 Dec 2017 09:59:24 +0000
Bug 1228841 - Part 0: Remove remaining conditional catch consumers in dom/. r=billm
8994162ee112a8c0a0b33f3404f04ebd9fad1285: Bug 1397426 - Expose renderLayers state via nsITabParent and correctly set initial tab states in async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:48:10 -0800 - rev 394730
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and correctly set initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
78073667ddc6e932408f49076b74c448a74bb710: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 394729
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm Calling GetPresShell() might create a content viewer, which might cause script to run. This is bad if there's a ForcePaint message queued up, because it could mean running the force painting code while we're still in the midst of making a tab hidden, which would put us in an inconsistent state. MozReview-Commit-ID: 3rw2wGllGdk
b9b2895b11a32f3da0f4c8fe364bf3bdfc7defb6: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 394728
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm This assumption also mirrors how non-remote browsers have their docShells active by default. In order to do this, I also have to increase the initial epoch's for the TabParent and TabChild, as if a RenderLayers has been called. Originally, since the epochs initted at 0, and the epochs stored by the [Layer|WebRender]TransactionParent were also initted at 0, we'd hit this branch: https://searchfox.org/mozilla-central/rev/c633ffa4c4611f202ca11270dcddb7b29edddff8/gfx/layers/ipc/LayerTransactionParent.cpp#703 and then we'd never alert the TabParent about the layer upload. MozReview-Commit-ID: 6PP1eCnisYK
53bb2bc2b67673572dafc3093280fa72973b3d32: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 394727
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm This is necessary because sometimes the async tab switcher will instantiate when there already exists some background tabs that are rendering via print preview. When that happens, it's important for the state to be set correctly for them so that we don't accidentally treat them as still loading, and wait (forever) for them to report having finished loading. MozReview-Commit-ID: 2dwo5WlXlgJ
e7a6fe9f9ce7186e8dc3c7aaeab47362c7060f5a: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 394726
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm Tab warming was originally disabled in this test because it was accidentally setting the DocShell to be active at an unexpected time. Because tab warming no longer activates DocShells, we can revert this change, though we also have to make it deal with the fact that switching tabs no longer makes docShells become activate immediately. MozReview-Commit-ID: K0fiA5AVfEm
5580c145af589494221aa1878d38882287d2b5d0: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 394725
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm MozReview-Commit-ID: KWwDee0ujR
a5b279d39c01e78f7e15154cf2a416294cd9d59f: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 394724
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm MozReview-Commit-ID: Go2EdMXGwa7
4643e46ff8d3e84d10ff178e15a1be7f734b020f: Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 11:27:29 -0400 - rev 394723
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm MozReview-Commit-ID: 1bBNwew7uCk
4dd20bf8c0f696417aea91cc9f48df25cd6a74ac: Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 07 Nov 2017 15:08:47 -0500 - rev 394722
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm MozReview-Commit-ID: 7UT036vUY85
2cd697170fb3c207f9aa342172633c2089508990: Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:21:34 -0800 - rev 394721
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm MozReview-Commit-ID: KTDhXM7PRdc
261be8ec05542a9e50c0ca03a59a8a44997269b7: Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:05 -0400 - rev 394720
Push 33019 by btara@mozilla.com at Mon, 04 Dec 2017 20:16:32 +0000
Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm Originally, setting the active state on the DocShell for remote browsers also did the work of making the TabChild render its layers and upload them to the compositor. This patch adds a new renderLayers method to nsITabParent which allows more fine-grained control - we can now, for example, cause layers to be rendered and uploaded without activating the DocShell. Note that if one activates or deactivates the DocShell, we'll still do the work of attempting to render / clear the layers if it hasn't already been done. MozReview-Commit-ID: KkLaMDTzfHi
cbfc68a9fa54b09b4ffcb2cce6eb2fd5570fedfc: Bug 1379680. Add an ipc ByteBuf type. r=billm
Jeff Muizelaar <jmuizelaar@mozilla.com> - Wed, 29 Nov 2017 10:11:15 -0500 - rev 394249
Push 32995 by btara@mozilla.com at Wed, 29 Nov 2017 22:41:41 +0000
Bug 1379680. Add an ipc ByteBuf type. r=billm This adds a ByteBuf type that can be sent by taking ownership of its buffer instead of having to make a copy.
66ba728d4fe90ac1eb4e79d072e219be5a36037c: Bug 1379680. Add a way to append buffers to a BufferList. r=billm
Jeff Muizelaar <jmuizelaar@mozilla.com> - Wed, 29 Nov 2017 10:11:13 -0500 - rev 394248
Push 32995 by btara@mozilla.com at Wed, 29 Nov 2017 22:41:41 +0000
Bug 1379680. Add a way to append buffers to a BufferList. r=billm
e09c9404d4176afa327adc1a1361c408d5dd30b6: Bug 1415158 - Don't notify ContentParent of a load if our IPC channel is closed. r=billm
Nika Layzell <nika@thelayzells.com> - Tue, 28 Nov 2017 15:30:56 -0500 - rev 394101
Push 32990 by dluca@mozilla.com at Wed, 29 Nov 2017 10:27:31 +0000
Bug 1415158 - Don't notify ContentParent of a load if our IPC channel is closed. r=billm MozReview-Commit-ID: 4HBIalVCfno
5690f4b488028760c1dbc44296decba18291455a: Bug 1402519 - Remove MOZ_CRASHREPORTER directives from ipc; r=billm
Gabriele Svelto <gsvelto@mozilla.com> - Tue, 10 Oct 2017 12:06:35 +0200 - rev 393529
Push 32962 by aiakab@mozilla.com at Fri, 24 Nov 2017 10:01:11 +0000
Bug 1402519 - Remove MOZ_CRASHREPORTER directives from ipc; r=billm MozReview-Commit-ID: 4mDW7cJqHDn
e3dd6e5b073f05e639ced9cb4e61b269f94e5411: Bug 1402519 - Remove MOZ_CRASHREPORTER directives from ipc; r=billm
Gabriele Svelto <gsvelto@mozilla.com> - Tue, 10 Oct 2017 12:06:35 +0200 - rev 393266
Push 32956 by csabou@mozilla.com at Thu, 23 Nov 2017 09:44:48 +0000
Bug 1402519 - Remove MOZ_CRASHREPORTER directives from ipc; r=billm MozReview-Commit-ID: 4mDW7cJqHDn
e37007fcbd347557bb6f7935037536a46c91fcbd: Bug 1418048 - Add a callback-based Send API to async returning IPDL methods, r=billm
Nika Layzell <nika@thelayzells.com> - Thu, 16 Nov 2017 15:12:06 -0500 - rev 392811
Push 32942 by toros@mozilla.com at Tue, 21 Nov 2017 09:56:05 +0000
Bug 1418048 - Add a callback-based Send API to async returning IPDL methods, r=billm Currently if you write an async IPDL method which has a return value, we expose a SendXXX method which returns a MozPromise. This MozPromise can then be ->Then-ed to run code when it is resolved or rejected. Unfortunately, using this API loses ordering guarantees which IPDL provides. MozPromise::Then takes an event target, which the resolve runnable is dispatched to. This means that the resolve callback's code doesn't have any ordering guarantees relative to the processing of other IPC messages coming over the same protocol. This adds a new overload to SendXXX with two additional arguments, a lambda callback which is called if the call succeeds, and a lambda callback which is called if the call fails. These will be called in order with other IPC messages sent over the same protocol. MozReview-Commit-ID: FZHJJaSDoZy
db0886825a54e3e600bc6ddbf7162f7266eac299: Bug 1282172 - Detect enum constants generated by macros when generating the Searchfox index. r=billm
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 18 Nov 2017 20:05:53 -0500 - rev 392610
Push 32933 by btara@mozilla.com at Sun, 19 Nov 2017 21:49:44 +0000
Bug 1282172 - Detect enum constants generated by macros when generating the Searchfox index. r=billm MozReview-Commit-ID: 5RUsVSMTU8
74ced70141b30f7485a79ac69de4c64f8c462536: Bug 1416250 - Remove conditional catch consumers in dom/. r=billm
Tooru Fujisawa <arai_a@mac.com> - Sat, 18 Nov 2017 22:57:17 +0900 - rev 392585
Push 32927 by rgurzau@mozilla.com at Sat, 18 Nov 2017 20:49:21 +0000
Bug 1416250 - Remove conditional catch consumers in dom/. r=billm
f53d4e3b563526a4191ea488d374cb0ebc7b597e: Bug 1401786 - Move base::LaunchApp options into a LaunchOptions struct, like upstream Chromium. r=billm
Jed Davis <jld@mozilla.com> - Fri, 08 Sep 2017 20:35:06 -0600 - rev 391614
Push 32896 by ccoroiu@mozilla.com at Tue, 14 Nov 2017 10:22:27 +0000
Bug 1401786 - Move base::LaunchApp options into a LaunchOptions struct, like upstream Chromium. r=billm MozReview-Commit-ID: 74IXV4oGeWR
89994077d440cfaac3adba3191a480a52637384f: Bug 1414138 - Keep IndexedDB in sandbox unlabeled. r=billm
Bevis Tseng <btseng@mozilla.com> - Mon, 06 Nov 2017 11:58:13 +0800 - rev 390881
Push 32849 by archaeopteryx@coole-files.de at Thu, 09 Nov 2017 09:53:32 +0000
Bug 1414138 - Keep IndexedDB in sandbox unlabeled. r=billm Script evaluated inside sandbox could touch scripts exposed by its creator in content. We should keep indexedDB in sandbox unlabeled instead of labeling it with SystemGroup.
21303d9216f2d0c02f31d76b9a399be87bb90d72: Bug 1412283 - Remove navigator.mozE10sEnabled r=billm
Tooru Fujisawa <arai_a@mac.com> - Wed, 01 Nov 2017 22:45:17 +0900 - rev 389643
Push 32789 by archaeopteryx@coole-files.de at Wed, 01 Nov 2017 21:55:42 +0000
Bug 1412283 - Remove navigator.mozE10sEnabled r=billm
7cc3c1afc8ce8eee7879e2b194eae2643b35a7b6: Bug 1412313 - Handle large string lengths in nsAString's ParamTraits. r=billm
Alex Gaynor <agaynor@mozilla.com> - Fri, 27 Oct 2017 16:13:46 -0400 - rev 389168
Push 32778 by archaeopteryx@coole-files.de at Mon, 30 Oct 2017 22:52:59 +0000
Bug 1412313 - Handle large string lengths in nsAString's ParamTraits. r=billm MozReview-Commit-ID: HR6kMzSkewS
8f657b9623fb25776c074651abc4a4d7e8cffea0: Bug 1408333 Get rid of nsIIPCBackgroundChildCreateCallback - part 19 - ContentChild, r=billm, r=asuth
Andrea Marchesini <amarchesini@mozilla.com> - Tue, 24 Oct 2017 12:02:41 +0200 - rev 387847
Push 32738 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 21:58:00 +0000
Bug 1408333 Get rid of nsIIPCBackgroundChildCreateCallback - part 19 - ContentChild, r=billm, r=asuth
baa55120263b9763e48dec6e63d94ea04e20583c: Bug 1410232 - fix SchedulerGroupSet::Put when transitioning to multiple groups; r=billm
Nathan Froyd <froydnj@mozilla.com> - Mon, 23 Oct 2017 08:49:41 -0400 - rev 387670
Push 32733 by archaeopteryx@coole-files.de at Mon, 23 Oct 2017 21:50:54 +0000
Bug 1410232 - fix SchedulerGroupSet::Put when transitioning to multiple groups; r=billm We were moving state from single -> multi, but we weren't doing anything with the group that was passed in for such cases.
f33ef94ef46cf5294152b98a00220568fa6ed4bc: Bug 1401790 - Remove ProcessArchitecture from IPC. r=billm,jimm
Jed Davis <jld@mozilla.com> - Wed, 04 Oct 2017 20:31:12 -0600 - rev 387499
Push 32723 by archaeopteryx@coole-files.de at Sun, 22 Oct 2017 09:33:30 +0000
Bug 1401790 - Remove ProcessArchitecture from IPC. r=billm,jimm This was used to support cross-architecture NPAPI plugins on OS X, but we stopped supporting that in 54 (bug 1339182). MozReview-Commit-ID: 2BcWYD6mguY