8697764fdb68ae0865469da5dfda1cfc3a448d24: No bug, Automated HPKP preload list update from host bld-linux64-spot-037 - a=hpkp-update
ffxbld - Wed, 22 Nov 2017 10:46:15 -0800 - rev 702136
Push 90389 by kgupta@mozilla.com at Wed, 22 Nov 2017 19:22:39 +0000
No bug, Automated HPKP preload list update from host bld-linux64-spot-037 - a=hpkp-update
2ca49183666a6d9954d3e1e15b26a673c13811f7: No bug, Automated HSTS preload list update from host bld-linux64-spot-037 - a=hsts-update
ffxbld - Wed, 22 Nov 2017 10:46:12 -0800 - rev 702135
Push 90389 by kgupta@mozilla.com at Wed, 22 Nov 2017 19:22:39 +0000
No bug, Automated HSTS preload list update from host bld-linux64-spot-037 - a=hsts-update
9a990e8c0104aff4b43a77a1d7fbf2bc3bdd692c: Bug 1410240 - Search suggestions keep displacing awesomebar results as I'm about to click on them. r?mak draft
Drew Willcoxon <adw@mozilla.com> - Wed, 22 Nov 2017 11:16:46 -0800 - rev 702134
Push 90388 by bmo:adw@mozilla.com at Wed, 22 Nov 2017 19:17:09 +0000
Bug 1410240 - Search suggestions keep displacing awesomebar results as I'm about to click on them. r?mak MozReview-Commit-ID: 2NdV9qWzld1
b759672d2e9ef3b1e63fd999d149cf753df60539: Bug 1020698 - Implement @autocomplete for <textarea>. r=baku draft
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Wed, 08 Nov 2017 21:35:04 -0800 - rev 702133
Push 90387 by mozilla@noorenberghe.ca at Wed, 22 Nov 2017 19:14:13 +0000
Bug 1020698 - Implement @autocomplete for <textarea>. r=baku The dom.forms.autocomplete.formautofill check in nsContentUtils::InternalSerializeAutocompleteAttribute will control if values other than "on" and "off" are supported. MozReview-Commit-ID: 48X3OzvuOpV
b58e600aab991eebf1c3f732fb432fb0aa6d47d7: Bug 1020698 - Remove dom.forms.autocomplete.formautofill check on HTMLSelectElement.autocomplete. r=baku draft
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Wed, 22 Nov 2017 14:09:44 -0500 - rev 702132
Push 90387 by mozilla@noorenberghe.ca at Wed, 22 Nov 2017 19:14:13 +0000
Bug 1020698 - Remove dom.forms.autocomplete.formautofill check on HTMLSelectElement.autocomplete. r=baku It's not necessary to hide the implementation of the property since nsContentUtils::InternalSerializeAutocompleteAttribute already does a pref check to decide whether values other than "on"/"off" are supported. MozReview-Commit-ID: 4yG1tfOJavX
d2ec431b2f3bf776fc215fd223099c609940a49e: Bug 1416319 - 8. Switch to using LayerSession coordinates APIs; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:23 -0500 - rev 702131
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 8. Switch to using LayerSession coordinates APIs; r?rbarker Use the LayerSession coordinates APIs instead of manually calculating coordinates using viewport metrics and toolbar height, which is prone to error. MozReview-Commit-ID: 4ebI3BHEOXR
5d94c5608a7c6cd5e96799ade2a29b1bcc6b998d: Bug 1416319 - 7. Don't expose viewport metrics from LayerSession; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:23 -0500 - rev 702130
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 7. Don't expose viewport metrics from LayerSession; r?rbarker Provide a set of coordinates APIs in LayerSession instead of exposing the raw viewport metrics, which are hard to use. This also lets us remove ImmutableViewportMetrics completely. The new APIs provide rectangular bounds in client or surface coordinates, and matrices to transform those coordinates to screen coordinates. This is done because the transformation to screen coordinates could (in the future) involve skew, rotation, etc, so it's up to the application to decide how to handle non-rectangular screen bounds. MozReview-Commit-ID: 8Yw8L63TmrQ
81e834ef25038fd735281def9d7780c517595cea: Bug 1416319 - 6. Remove DynamicToolbarAnimator from LayerView; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:23 -0500 - rev 702129
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 6. Remove DynamicToolbarAnimator from LayerView; r?rbarker Remove all DynamicToolbarAnimator-related code from LayerView now that they are in LayerSession. MozReview-Commit-ID: 56AO79T3NoK
af5a55d7398c896d74e0f361cbcfac43e095799d: Bug 1416319 - 5. Update DynamicToolbarAnimator usage in other classes; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:22 -0500 - rev 702128
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 5. Update DynamicToolbarAnimator usage in other classes; r?rbarker Use DynamicToolbarAnimator through the session in places where we need to interact with the toolbar or get the current toolbar height. MozReview-Commit-ID: PdGX4FEHp5
85d42387419012bbe66a9e5d70b890333e8f0923: Bug 1416319 - 4. Store DynamicToolbarAnimator in LayerSession; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:22 -0500 - rev 702127
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 4. Store DynamicToolbarAnimator in LayerSession; r?rbarker Add getter/setter for DynamicToolbarAnimator in LayerSession in lieu of LayerView. It is then LayerSession's responsibility to keep track of how changes in the toolbar affects other things like the window and viewport bounds. MozReview-Commit-ID: HmRqxZ7EUCZ
ba491771124baaea743acbf22908d122bcc6ce41: Bug 1416319 - 3. Clean up DynamicToolbarAnimator API; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:22 -0500 - rev 702126
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 3. Clean up DynamicToolbarAnimator API; r?rbarker The plan is to incorporate DynamicToolbarAnimator into the official GeckoView API and expose getter/setter in LayerSession. This patch cleans up the class to make sure only public APIs are public, and to assert they are called on the UI thread. MozReview-Commit-ID: D3ePV3k2HvX
7c0d22091ad36f188bc8603e4086b18f91848815: Bug 1416319 - 2. Remove usage of MetricsListener by FormAssistPopup; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:22 -0500 - rev 702125
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 2. Remove usage of MetricsListener by FormAssistPopup; r?rbarker This code is supposed to reposition the form assist popup if the toolbar appears or disappears while the popup is visible, but we can move that to a resize event listener in JS, so we don't have to maintain the MetricsListener API for DynamicToolbarAnimator. MozReview-Commit-ID: HR6wcJrGloR
190e24ed0c1b765448c34b91145f706d49994e1d: Bug 1416319 - 1. Move content-document-is-displayed flag to native code; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Wed, 22 Nov 2017 14:12:22 -0500 - rev 702124
Push 90386 by bmo:nchen@mozilla.com at Wed, 22 Nov 2017 19:12:37 +0000
Bug 1416319 - 1. Move content-document-is-displayed flag to native code; r?rbarker One fix I forgot to make in bug 1416310 is to change the code to reset the flag in LayerView. I think it's better if we just moved the whole thing to native code, since we don't really use the flag in Java. MozReview-Commit-ID: 9cbcYb89LhC
4d8757af5d9921b05cb83fdd11adbe0f16faf7fa: Bug 1397426 - Expose renderLayers state via nsITabParent and correctly set initial tab states in async tab switcher. r?billm draft
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:48:10 -0800 - rev 702123
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and correctly set initial tab states in async tab switcher. r?billm MozReview-Commit-ID: IIMmwrgJUV6
c254635e7461e8053f74d5140b8184456eb3f32e: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r?billm draft
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 702122
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +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
2768b7f3a726c1a717751f564ccf27780810b9af: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r?billm draft
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 702121
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +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
464840beb1f8c56e75a45d70906e22e577be5677: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r?billm draft
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 702120
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +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
f669f3dc73385be2f503936da2162b6772d7b0fd: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r?billm draft
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 702119
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +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
6e947b8d437daa58f98e5a79c107450ce32ff65c: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r?billm draft
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 702118
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r?billm MozReview-Commit-ID: KWwDee0ujR
d089d3f37b759f63e836bbdc68c03c4112ee482f: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r?billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 702117
Push 90385 by bmo:mconley@mozilla.com at Wed, 22 Nov 2017 19:08:31 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r?billm MozReview-Commit-ID: Go2EdMXGwa7
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip