Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync page position #265

Open
gerroon opened this issue May 24, 2016 · 6 comments
Open

Sync page position #265

gerroon opened this issue May 24, 2016 · 6 comments
Labels
depends on wallabag server dependent on changes in wallabag server software Feature

Comments

@gerroon
Copy link

gerroon commented May 24, 2016

Hi

I am not sure if this issue possible but it would be neat if we could sync the current reading location of an article across devices.

thanks

@Strubbl
Copy link
Contributor

Strubbl commented May 24, 2016

Sounds like a nice feature. But is it easy to compare the scrolling position of the displayed text on a e.g. a smartphone to a notebook display?

@gerroon
Copy link
Author

gerroon commented May 24, 2016

@Strubbl

Maybe floating point based page position percentage might work?

@di72nn
Copy link
Member

di72nn commented May 24, 2016

Basic floating point values do not even give accurate results when screen orientation changes in Android app (because of text and images reflow). But these are still not bad results.

@di72nn di72nn added the Feature label Sep 30, 2016
@di72nn di72nn changed the title FR: Sync page position Sync page position Sep 30, 2016
@ghost ghost added the depends on wallabag server dependent on changes in wallabag server software label Dec 7, 2016
@ghost
Copy link

ghost commented Dec 7, 2016

Related to wallabag/wallabag#2643.

@azrdev
Copy link

azrdev commented Oct 18, 2019

As a first step, it would be nice if reading progress is saved in a way so it's not overwritten if I do a "full sync" (or should I rather file this as a separate bug?)

@di72nn
Copy link
Member

di72nn commented Oct 18, 2019

"Full sync" is inherently destructive for data that is not synchronized. So synchronizing the reading position will make the "full sync" problem nonexistent.
I don't think it's worth fixing it on its own since it's extra work and "full sync" is kind of a "last resort" function for when "fast sync" with "article sweeping" is not enough.
Anyway, if you really want to get it fixed for some reason, a separate issue is due.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depends on wallabag server dependent on changes in wallabag server software Feature
Projects
None yet
Development

No branches or pull requests

4 participants