Skip to content
This repository has been archived by the owner on Nov 25, 2019. It is now read-only.

Using zoom causes some articles to open wrong #38

Open
doozan opened this issue Jan 28, 2012 · 6 comments
Open

Using zoom causes some articles to open wrong #38

doozan opened this issue Jan 28, 2012 · 6 comments

Comments

@doozan
Copy link
Contributor

doozan commented Jan 28, 2012

After I changed my zoom setting to be zoomed in twice, opening articles on the English wikipedia (the 'Food' article, for example) will display the article not at 0,0 but at 0,XX so when it appears it seems that it has been scrolled down a line or two. Pressing pageUp repositions the article correctly.

I couldn't find a quick solution for this, but I could reproduce it without the eink patches so I assume this is a general webview/aarddict problem.

@itkach
Copy link
Member

itkach commented Jan 28, 2012

Doesn't happen for me on Nexus One/Android 2.3.6

@doozan
Copy link
Contributor Author

doozan commented Jan 28, 2012

Weird. It's only problematic with the articles 'Foo' and 'Food' in the English Wikipedia from March 2011. Some other articles will scroll down a little bit after they're loaded, which causes a screen refresh on the eink display, however, only the articles for 'Foo' and 'Food' actually scroll down far enough to obscure the first line of text.

@itkach
Copy link
Member

itkach commented Mar 4, 2013

is this still an issue?

@doozan
Copy link
Contributor Author

doozan commented Mar 5, 2013

Yes, when zoomed in, articles open with an offset so that the first few lines are obscured. It's also visible if you reset zoom to normal, open an article, and then zoom in several times -- the first line of the article is no longer visible. Tested on my Nook, which is running Android 2.1

@itkach
Copy link
Member

itkach commented Mar 5, 2013

As I mentioned before this doesn't seem to happen on Android 2.3, Android 4.2 seems to fine too. If that's 2.1 specific problem then I don't think there's anything to be done in the application.

@doozan
Copy link
Contributor Author

doozan commented Mar 6, 2013

I can't reproduce it on 2.3, either. I'll submit a patch if I ever find a workaround, but for now I'm okay with closing this issue as a 2.1 anomaly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants