Created an attachment (id=1855) [details]
1st screenshot showing the issue

Created an attachment (id=1856) [details]
2nd screenshot showing the bug

*** This bug has been confirmed by popular vote. ***

I doubt whether tagging this usability bug as beeing low priority is the
smartest thing on earth to do.

For the following reason:

The N900 misses some features its competitors (like the Apple iPhone,
Android-Phones or the Palm Pre) provide. And it offers some unique features;
the most important three of them are imho:

1. A large amount of the Maemo code is free Software (FOSS) [Ok, this is true
for Android as well]
2. Maemo is a standard Debian-compatible GNU+Linux-Distro
3. It has an outstanding Browser with Flash support.

If a usability bug like this diminishes the user experience of this important
component to this extent, imo it should be considered harmful.

Comment 5 Andre Klapper 2010-01-04 00:13:34 UTC

Priority by default is low. If a developer decides differently, that's up to
him/her.

> Priority by default is low. If a developer decides differently,
> that's up to him/her.

Well okay. I reported the bug with high priority, but it was set to low
priority by aklapper e€t openismus.com afterwards. Maybe he/she did this only
because the bug reporter must not set the priority himself.

Comment 7 Andre Klapper 2010-01-04 15:22:06 UTC

(In reply to comment #6)
> I reported the bug with high priority

We are currently working on upgrading Bugzilla so reporters cannot set this
field anymore.

Can we increase the priority and severity of this bug?
It makes the browser look very ugly (this is on release 2.2009.51-1.002).
The Fennec browser does not exhibit this problem.

Comment 9 Andre Klapper 2010-01-20 14:25:19 UTC

No, see https://bugs.maemo.org/page.cgi?id=fields.html#bug_severity

(In reply to comment #9)
> No, see https://bugs.maemo.org/page.cgi?id=fields.html#bug_severity
So, is there anyone looking into this?

Comment 11 Andre Klapper 2010-01-20 15:33:01 UTC

Yes, it's proposed for PR1.2, but adding "Are there news?" comments slow down
work, as much as I can understand general criticism on missing transparency
here (offtopic for this ticket, but also see bug 630).

(In reply to comment #11)
> Yes, it's proposed for PR1.2, but adding "Are there news?" comments slow down
> work, as much as I can understand general criticism on missing transparency
> here (offtopic for this ticket, but also see bug 630).
Possibly just set the status to ASSIGNED and add a short comment
such as "work in progress" :-)

Comment 13 Neil MacLeod 2010-01-20 15:57:54 UTC

This is almost certainly the "hinting" (not kerning) bug from Mozilla:

https://bugzilla.mozilla.org/show_bug.cgi?id=470440

Presumably the same fix has (or will) be applied to MicroB, or MicroB will
integrate the latest Mozilla Gecko in a future release.

FYI: This bug is already fixed in the latest Fennec aka Firefox Mobile for
Maemo.

Comment 14 Ryan Abel 2010-01-23 01:08:30 UTC

Is there any way to up the priority on this one? This is really a blocker for
usable zoom. . . .

Comment 15 tuukka.tolvanen 2010-02-28 17:26:04 UTC

f ~ 10.2010.06

Comment 16 Andre Klapper 2010-03-15 12:37:43 UTC

*** Bug 9550 has been marked as a duplicate of this bug. ***

Comment 17 Andre Klapper 2010-03-15 20:51:31 UTC

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).