Samsung Galaxy S2 Android 2.3.5 1.5 GHz dual-core procesor 1 GB RAM 4.5" 800*400 pixel screen Soup build from March 7th, 2012 from people.mozilla.com/~dclarke/openwebapps/Soup The Sky Guide app on Android does not fit the screen properly causing some elements to be cut-off. Parts of the page are cut-off from the top panel (especially in portrait mode where the Sign in button is), writing in main headlines is cut-off and search bar is cut-off as well. This is best seen when in portrait mode. Steps to Reproduce: 1. Install Soup on an Android device 2. Install Sky Guide 3. Launch Sky Guide with the phone in portrait mode Actual Results: Parts of the page are cut-off and elements are missing and can only be seen in landscape mode (for example the search text-box and the Sign in button). User cannot scroll to see the missing elements. Expected Results: The app fits properly within the current screen dimensions with no content missing.
Checking against the Gecko vs. Webkit Browser Analysis recently conducted, this is probably a problem with the actual app rendering in a mobile environment, not a problem with Soup. Migrating to tech evangelism flagged as a top app.
Isn't bug 734793 just a special case of this one?
Sounds like it. This appears to be more of the general bug that was logged, while 734793 is a sub-bug that falls under this.
This is also cut off in Android stock browser on my HTC One. Amusingly, the only browser that renders the full text readable most of the time is Opera Mobile Classic - good job Presto ;)
(In reply to Hallvord R. M. Steen from comment #5) > This is also cut off in Android stock browser on my HTC One. Amusingly, the > only browser that renders the full text readable most of the time is Opera > Mobile Classic - good job Presto ;) Does this mean the same problem manifests in Chrome and Safari as well? If so, this is a general problem with the mobile version of this site. In this case, let's resolve as won't fix.
I saw the same problem in "stock Android" browser (no idea whether to call it Chrome or Safari :-p though probably closer to Chrome, right?). Just re-tested, I still see it. Closing the bug.