From 7c2403e7a155e8ebb35f1f5f6fed4158e6c65f14 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lorenz=20H=C3=BCbschle-Schneider?=
 <lorenz-dev@lgh-alumni.de>
Date: Tue, 11 Feb 2014 20:40:25 +0000
Subject: [PATCH] Scrolling: Do not use webkit-specific function to scroll
 readmarker into view

Sorry for that.
---
 js/glowingbear.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/js/glowingbear.js b/js/glowingbear.js
index 148957b..8230238 100644
--- a/js/glowingbear.js
+++ b/js/glowingbear.js
@@ -619,10 +619,10 @@ weechat.controller('WeechatCtrl', ['$rootScope', '$scope', '$store', '$timeout',
             // Give the check 3 pixels of slack so you don't have to hit
             // the exact spot. This fixes a bug in some browsers
             if ((nonIncremental && sTop < sVal) || (sTop - sVal < 3)) {
-                var readmarker = document.getElementById('readmarker');
+                var readmarker = document.querySelector(".readmarker");
                 if (nonIncremental && readmarker) {
                     // Switching channels, scroll to read marker
-                    readmarker.scrollIntoViewIfNeeded();
+                    bl.scrollTop = readmarker.offsetTop - readmarker.parentElement.scrollHeight + readmarker.scrollHeight;
                 } else {
                     // New message, scroll with buffer (i.e. to bottom)
                     bl.scrollTop = bl.scrollHeight - bl.clientHeight;