Backed out changeset 14d0e2a451e7 (bug 1383365) for perma crashes in test_wheel_transactions.html
authorCarsten "Tomcat" Book <cbook@mozilla.com>
Wed, 26 Jul 2017 13:59:12 +0200
changeset 419992 12f55e239e9d482261170f1e47f6b419f6d80ed8
parent 419991 ff7c09a77c2914fc37307168ec1a5c80d79bb814
child 419993 5dc08811c6a664e788d7cf21d6911ab187c15c1a
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)
bugs1383365
milestone56.0a1
backs out14d0e2a451e769dcd23f1a47f954b31231519dae
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
Backed out changeset 14d0e2a451e7 (bug 1383365) for perma crashes in test_wheel_transactions.html
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",
-           aFocusSequenceNumber,
-           mFocusHasKeyEventListeners);
+           mFocusHasKeyEventListeners,
+           aFocusSequenceNumber);
 
     mType = FocusTarget::eNone;
     return;
   }
 
   nsCOMPtr<nsIContent> selectedContent = presShell->GetSelectedContentForScrolling();
 
   // Gather the scrollable frames that would be scrolled in each direction