Use a cookie to save the "furthest read location" for a user

[AndrewMagliozzi]

We could consider using HTML5’s progress element for the scrubber. Here’s more about that:

http://css-tricks.com/reading-position-indicator/

Also, it would be great if the app could keep track of user’s progress through a book so they can pick up where they left off. Not sure of the development options for this feature but something to start thinking about. Cookie? Something else for those with an account?

[btbonval]

I know Google Plus does something like this via cookie. If you're reading your stream and a new post arrives, there will be a button floating in the upper left that says "new". If you click it, one of the visible posts on the screen will be bookmarked and then you are scrolled to the top of the feed. There's a button that says something like "return to position" or somethin which kicks you back down to the bookmarked post.

It's cookie-specific, though. So it won't maintain that if you log out and log in, or if you use a different browser.

The CSS trick looks pretty lofty. I wonder if there's an easier way to do it. Unfortunately looking at Google's code will not be helpful.

[AndrewMagliozzi]

Thanks for chiming in Bryan. Perry sent this over and I wanted to preserve
it. We'll discuss in more depth when we start implementing the new
designs.

On Thu, May 8, 2014 at 11:39 AM, Bryan Bonvallet
notifications@github.comwrote:

I know Google Plus does something like this via cookie. If you're reading
your stream and a new post arrives, there will be a button floating in the
upper left that says "new". If you click it, one of the visible posts on
the screen will be bookmarked and then you are scrolled to the top of the
feed. There's a button that says something like "return to position" or
somethin which kicks you back down to the bookmarked post.

It's cookie-specific, though. So it won't maintain that if you log out and
log in, or if you use a different browser.

The CSS trick looks pretty lofty. I wonder if there's an easier way to do
it. Unfortunately looking at Google's code will not be helpful.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-42565528
.