maemo.org Bugzilla – Bug 9555
Only the address bar is visible on the bottom panel
Last modified: 2010-10-26 15:32:01 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
1. Close all browser windows, including the bookmarks one.
2. Open any web page using external application, like raeddit or rss viewer. Do
not open the page using the browser's interface.
3. Notice that only the address bar and stop button is displayed while the page
4. Assuming the browser displays the page fullscreen: after the page has loaded
press the button in bottom-right corner to switch to windowed view.
5. Notice that only the address bar is displayed on the bottom panel.
Address bar is displayed along with the bookmark buttons, the history button
and fullscreen button.
Only the address bar is displayed.
Rebooting the phone does not help. Opening new browser windows doesn't change
behavior. Opening the browser using application menu icon (after all browser
windows were closed) brings things back to normal, but following the repro
steps causes the bug to reappear.
Created an attachment (id=2476) [details]
Illustration for step 3
Created an attachment (id=2477) [details]
Illustration for step 5
we believe this will be fixed in the next major update (i have no idea when
that would be, don't ask).
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).
This is not fixed in PR1.2.
*** Bug 10275 has been marked as a duplicate of this bug. ***
With pe1.2, this bug seems to occure quite invariably now. If browser is closed
and I open for example an rss feed via the maemo rss reader widget, the browser
window that opens is almost invariably the buggy kind now.
"Reproducible. Using raeddit or any application alone wasn't enough to
reproduce it. It's necessary to open links from at least 2 apps, raeddit + chat
conversation did the trick for me."
I had not witnessed this problem for several months. I then recognized that by
turning of rotation from the browser settings, the problem returned instantly.
After reactivating rotation in the browser, the problem disappears.
The bug seems to be related to the rotation of the browser.