maemo.org Bugzilla – Bug 7445
mobile4arab.com: After zooming in, sometimes cannot drag to the right side
Last modified: 2019-09-11 19:49:48 UTC
You need to
before you can comment on or make changes to this bug.
SOFTWARE VERSION: 42-11
(Settings > General > About product)
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. open web browser
2. open for example www.mobile4arab.com
3. zoom in 2 or 3 times
4. try to slide to the right side.. it wount..
like other websites slide left and right
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US)
AppleWebKit/532.0 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/532.0
Thanks for reporting this.
What are other websites where this happens?
I can partially reproduce it in the current internal version 52-5 - it
sometimes works, sometimes it does not.
I thought we already had a public bug for this. The standard report of this is
Arab Facebook (it also affects Hebrew, and is roughly iiuc a split between a
bug in Gecko upstream and poor design by Facebook and friends).
(In reply to comment #2)
> The standard report of this is Arab Facebook (it also affects Hebrew
Any internal bug ID? Could not find one...
here are some other websites:
the summary here could use a rewrite (steal the one from bmo?)
fwiw, romaxa indicated to me this week he had a fix for this
In new firefox this has resolved.. And it works good now.
But still the same for MicroB..
adib: thanks, but we don't need such comments here.
fixed internally in 10.2010.03-12
please note that this build number is totally random and has no relationship to
anything else. Andre will come along and indicate when there's a build
available with this fix for you to use.
This has been fixed in packages
which are part of the internal build version
(Note: 2009/2010 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
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
*** Bug 9287 has been marked as a duplicate of this bug. ***
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).
(In reply to comment #5)
> the summary here could use a rewrite (steal the one from bmo?)