This is due to the way we use webkit and mako to render the streams and how we handle tracking position of the view so the user doesn't get bounced to the top on each refresh.
This won't be a problem in 3.2, the new client will handle this much better.
This is due to the way we use webkit and mako to render the streams and how we handle tracking position of the view so the user doesn't get bounced to the top on each refresh.
This won't be a problem in 3.2, the new client will handle this much better.