Using the official Android app on a HTC Bravo. Items, most of which have a picture or video embedded, end up rendered half off to the left of screen. Usually it renders correctly first but at the first action, scrolling down or whatever, it re-renders off to the left. I haven’t managed to get a screenshot of it yet, but if I do I’ll add it here.
5 Likes
I’m sending this off to Ryan, but can you get a list of a few stories and feeds that do this? Also, does this happen every time you visit the story or only on first load?
Can confirm that it’s repeatable on stories with embedded images or videos, most notably for me in this feed http://feeds.feedburner.com/CrikeyBlo… Going back to feed view and then back to the item fixes it until you scroll again.
I’ve got the same issue, first saw it on the Wired Threat Level blog:
http://www.wired.com/threatlevel/feed/
Same behavior as described above, feed appears normal from top, but scrolling down just a bit past the title causes everything to shift off the left side of the screen.
Fixed in the latest build, which should be out within the week. Thanks!
Absolutely, but you’ll have to compile it yourself: http://github.com/samuelclay/NewsBlur…
So before the crashing set in I managed to check this out and it seems to be mostly fixed.
One feed I found that still had the issue was http://www.questionablecontent.net/QC… and it seems to be related to their use of banner ads. Other sites with images as part of the post content seem to be all working fine now.
What’s the feed? I’d love to get specific examples to my dev.
From http://www.economist.com/blogs/babbag… the story that points to http://www.economist.com/blogs/babbag… offsets to the left because of the embedded media.
An old issue, but it seems to be back on the current version of the Android app. I’m seeing it the most in the Kotaku feed. Here’s an example:
http://kotaku.com/normal-human-beings…
As described above, it appears normal, but scrolling down just a bit shoves everything off the left side of the screen.
I ran into this issue last night trying to read feeds.
If it happens, please include the story title and feed where you noticed it. It is possibly a rendering issue and we need a reproducible test case.