Bug 1383365 - Fix APZ focus target log parameter order. r=botond draft
authorRyan Hunt <rhunt@eqrion.net>
Sun, 23 Jul 2017 13:58:19 -0400
changeset 616526 cb1228dcd6923884e3304c7b51851dee07964706
parent 616205 f1693d664f8e8ee4c79801630c181c28095cad56
child 616527 6824ddf0e0d00134b49147fee21ee4e75455ff29
push id70717
push userbmo:rhunt@eqrion.net
push dateThu, 27 Jul 2017 05:04:58 +0000
reviewersbotond
bugs1383365
milestone56.0a1
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