Not going to expected place when going back one page

[curiousgeorge61]

I have noticed that when I have gone to view an observation from the total observation list and agree with the ID  or not that when I click the  go back one page button I end up at the top of the first page rather than going back to the point of the observation I just viewed. Before I would end up at what ever place the observation was on the list and not at the top of the list. It worked much better for me the old way.
George

[Ken-ichi]

I don't think we really changed anything that would cause that
behavior. Can you provide an example? E.g. I go to

http://www.inaturalist.org/observations/kueda

and scroll down to my observation of California larkspur. When I click
on the link, I go to

http://www.inaturalist.org/observations/256142

When I click the back button in my browser, I go back to

http://www.inaturalist.org/observations/kueda

and it's still scrolled to where I was before. Things might work
different at http://www.inaturalist.org/observations because it's
changing all the time, which is kind of a problem. We should probably
make those URLs more stable. I don't think the map view there would
ever scroll you back to where you were before.

-ken-ichi

> --
> You received this message because you are subscribed to the Google Groups
> "iNaturalist" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to inaturalist...@googlegroups.com.
> To post to this group, send email to inatu...@googlegroups.com.
> Visit this group at http://groups.google.com/group/inaturalist?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[curiousgeorge61]

If I start at observations by everyone I scroll down to about the middle of the list on page one and click the view button and I go to

http://www.inaturalist.org/observations/261506

If I click the go back one page button I am at the top of the list on page one rather than where I was when I hit the view button. If I then go to page two and scroll down about half way I click on the view button and go to

http://www.inaturalist.org/observations/261448

If I click on the go back button I end up at the top of the list on page two.

I know it isn't a big thing, but it requires scrolling back to where I was when I hit the view button so takes more time than it did before when I would end up at the point on the list where I clicked on view.

Thanks,

George

[Chuck Sexton]

I'm seeing a variation on this "returning to scroll point" issue:  The behavior differs by browser.  For instance, when viewing "Your Content", scrolling down, clicking to view an observation, comment, etc., and then returning to the observation list, I am *correctly* returned to the scroll point with FireFox (vers. 47.0) and Google Chrome (Version 51.0.2704.103 (64-bit)),  but Safari (9.1.1 (11601.6.17)) does *not*.  The latter brings me back somewhere near the top of the observation list, not at the top, but somewhere a few observations down the list.

Such a variation among browsers is far beyond my comprehension as far as the inner workings of iNat, but, hey, almost all of its working are beyond my comprehension!!

Chuck

[Tony Iwane]

I agree with Chuck, it's probably a browser issue. Safari often behaves weirdly when going back sometimes. Two finger swipe to go back results in Safari reloading the page, which is even more infuriating. 

[Chuck Sexton]

In fact, I've noticed that the "return to scroll point" issue has been *worsened* in Safari with the new Dashboard format.  Safari used to return me to a given point pretty well in various lists of observaions, etc.  Now with the new Dashboard format, it *never* does.  This is quite annoying when going back and forth to review observations well down on a given page, for instance.

@kueda, @loarie: Is there something in the code of the newly formatted Dashboard (i.e. the list of observations on the left side of the screen) which Safari doesn't recognize or can't latch onto or can't place a return tag on?  (It'll be obvious to you that I don't understand code at all, so pardon me if I'm phrasing my question improperly.)

Chuck