maemo.org Bugzilla – Bug 8104
Browser portrait mode makes it stop working after a while
Last modified: 2010-03-15 20:51:46 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
1. Turning on portrait mode on the browser
2. Playing around a bit, surfing the web turning portrait/landscape a few times
in different websites
3. The browser just shows white pages whenever I try to load a page. The
"progress bar"( I mean the little line below the location field) just goes back
and forward again and again
EXPECTED OUTCOME: To keep working ;)
ACTUAL OUTCOME: Browser stops working
7/10 (probably depends on how much you change between portrait/landscape
EXTRA SOFTWARE INSTALLED: some apps from the ovi store and plenty of apps from
Turning the portrait mode off seems to solve the problem and the browser starts
could be related to int-152973 though portrait isn't implicated there
Same issue as before really. General us of the ctrl shift and o trick, before
the browser shut down and now refuses to launch.
"I'm not able to reproduce it on any latest image internally. Are there any
reliable steps for this issue?"
(In reply to comment #3)
> "I'm not able to reproduce it on any latest image internally. Are there any
> reliable steps for this issue?"
I can't seem to find the steps to make this happen :S
Although I can assure you it happens sometimes. I'll look further into it to
see if I can find something usefull.
Well, after testing it for a few days... I can't find a way to reproduce it.
Although I must say it just happened once more in this last week.
Should we close the bug report?
This cannot be reproduce internally in current internal versions 2010.04-*,
plus a similar bug is marked as FIXED.
A future public update include the fix. (This is not always already the next
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
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).