Bug 1383365 - Fix APZ focus target log parameter order. r=botond
authorRyan Hunt <rhunt@eqrion.net>
Sun, 23 Jul 2017 13:58:19 -0400
changeset 420272 c9d5da3bd0fa1fc3d5da478c8a4c9878114c4188
parent 420271 5b4c249619e5c9d0421bb910eebf62bbac1f4bbf
child 420273 633262ca601a590faffcae53e98dd07aad22650f
push id7566
push usermtabara@mozilla.com
push dateWed, 02 Aug 2017 08:25:16 +0000
treeherdermozilla-beta@86913f512c3c [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersbotond
bugs1383365
milestone56.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1383365 - Fix APZ focus target log parameter order. r=botond MozReview-Commit-ID: DJtXaylyseg
gfx/layers/apz/src/FocusTarget.cpp
--- a/gfx/layers/apz/src/FocusTarget.cpp
+++ b/gfx/layers/apz/src/FocusTarget.cpp
@@ -161,18 +161,18 @@ FocusTarget::FocusTarget(nsIPresShell* a
 
   // The content to scroll is either the focused element or the focus node of
   // the selection. It's difficult to determine if an element is an interactive
   // element requiring async keyboard scrolling to be disabled. So we only
   // allow async key scrolling based on the selection, which doesn't have
   // this problem and is more common.
   if (focusedContent) {
     FT_LOG("Creating nil target with seq=%" PRIu64 ", kl=%d (disabling for focusing an element)\n",
-           mFocusHasKeyEventListeners,
-           aFocusSequenceNumber);
+           aFocusSequenceNumber,
+           mFocusHasKeyEventListeners);
 
     mType = FocusTarget::eNone;
     return;
   }
 
   nsCOMPtr<nsIContent> selectedContent = presShell->GetSelectedContentForScrolling();
 
   // Gather the scrollable frames that would be scrolled in each direction