Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

font display problem in mozilla

0 views
Skip to first unread message

Rick Pasotto

unread,
May 30, 2002, 12:36:34 PM5/30/02
to
Depending on the size of the font (and maybe the font itself), if the
last line of text in a mozilla display is only partially visible, then
scrolling up one line sometimes results in the characters being only
partially displayed. A page-up followed by a page-down to return to the
same place corrects it.

Is this an X problem or a mozilla problem?

--
"Making fun of born-again christians is like hunting dairy cows with a
high powered rifle and scope."
-- P.J. O'Rourke
Rick Pasotto ri...@telocity.com http://www.niof.net


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org


Jason Lunz

unread,
May 30, 2002, 2:42:14 PM5/30/02
to
ri...@telocity.com said:
> Depending on the size of the font (and maybe the font itself), if the
> last line of text in a mozilla display is only partially visible, then
> scrolling up one line sometimes results in the characters being only
> partially displayed. A page-up followed by a page-down to return to
> the same place corrects it.
>
> Is this an X problem or a mozilla problem?

I've seed this too, and I'm surprised that more people haven't
complained about it. Maybe it only happens for certain setups. Has
anyone else seen this?

It shows up in both mozilla and galeon. The problem isn't so much a
font display problem as it is a page display problem. After scrolling,
portions of web pages are offset by a pixel or two. It happens for both
images and text, though I find it more noticable with text. Sometimes it
happens after scrolling, but I've been paying attention to this for a
while and sometimes these display offsets happen on a freshly-drawn
page.

The screen captures at http://orr.falooley.org/pub/mozilla_bug/ show
what I'm talking about. These shots are from galeon 1.2.1. The mozilla
"about:" page says:

Mozilla 1.0 Release Candidate 2
Mozilla/5.0 Galeon/1.2.1 (X11; Linux i686; U;) Gecko/20020421
Debian/1.2.1-2

I've been hoping that each new release of mozilla would cure this since
I first saw it in 0.9.6 or so.

anyone?

Jason

Colin Watson

unread,
May 30, 2002, 2:49:43 PM5/30/02
to
On Thu, May 30, 2002 at 02:41:32PM -0400, Jason Lunz wrote:
> ri...@telocity.com said:
> > Depending on the size of the font (and maybe the font itself), if the
> > last line of text in a mozilla display is only partially visible, then
> > scrolling up one line sometimes results in the characters being only
> > partially displayed. A page-up followed by a page-down to return to
> > the same place corrects it.
> >
> > Is this an X problem or a mozilla problem?
>
> I've seed this too, and I'm surprised that more people haven't
> complained about it. Maybe it only happens for certain setups. Has
> anyone else seen this?

Yeah, myself and a colleague at work have both seen it. It's an
off-by-one error in their rendering engine, but I'm not sure if it's
filed; I can never find my way around in Mozilla's bug tracking system.
:)

Selecting the text also causes the display glitch to disappear, by the
way.

--
Colin Watson [cjwa...@flatline.org.uk]

Rudy Gevaert

unread,
May 30, 2002, 3:00:04 PM5/30/02
to
On Thu, May 30, 2002 at 12:30:23PM -0400, Rick Pasotto wrote:
> Depending on the size of the font (and maybe the font itself), if the
> last line of text in a mozilla display is only partially visible, then
> scrolling up one line sometimes results in the characters being only
> partially displayed. A page-up followed by a page-down to return to the
> same place corrects it.
>
> Is this an X problem or a mozilla problem?

Yep, I've got it too :) :(

Has anybody filled a bug report?

Rudy
--
Rudy Gevaert - ru...@zeus.rug.ac.be - http://www.zeus.rug.ac.be
keyserverID=24DC49C6 - http://www.webworm.org
I'm a GNU/Linux advocate. Every action against my beliefs is useless


The concept is interesting and well-formed, but in order to earn better
than a 'C', the idea must be feasible.
- A Yale University management professor in response to student Fred Smith's paper proposing reliable overnight delivery service
(Smith went on to found Federal Express Corp.)

Jason Lunz

unread,
May 30, 2002, 3:09:33 PM5/30/02
to
In mlist.debian-user, you wrote:
> Yeah, myself and a colleague at work have both seen it. It's an
> off-by-one error in their rendering engine, but I'm not sure if it's
> filed; I can never find my way around in Mozilla's bug tracking
> system.

I actually looked this up once; it was reported fixed in debian bug
#138788, which refers to bugzilla bug #83289. That "fix" didn't work,
though, or at least didn't address all the problems. I suppose #138788
should be reopened.

> Selecting the text also causes the display glitch to disappear, by the
> way.

Yes. You can often see text jump by a few pixels when you select it;
however, the resulting position isn't always correct. You can also fix
the entire display by switching to another virtual desktop and back, and
you can sometimes see offsets change in galeon's display by moving
another window around on top of it.

Jason

Hall Stevenson

unread,
May 30, 2002, 3:35:55 PM5/30/02
to
> Yes. You can often see text jump by a few pixels
> when you select it; however, the resulting position isn't
> always correct. You can also fix the entire display by
> switching to another virtual desktop and back, and
> you can sometimes see offsets change in galeon's
> display by moving another window around on top of it.

Switching desktops or moving a window over your galeon/mozilla
window doesn't cause the browser to "re-render" the page.

Is this actually an X problem and not a galeon/mozilla one ??


Hall

Hubert Chan

unread,
May 30, 2002, 4:24:05 PM5/30/02
to
--=-=-=
Content-Transfer-Encoding: quoted-printable

>>>>> "Jason" =3D=3D Jason Lunz <lu...@reflexsecurity.com> writes:

Jason> I actually looked this up once; it was reported fixed in debian
Jason> bug #138788, which refers to bugzilla bug #83289. That "fix"
Jason> didn't work, though, or at least didn't address all the
Jason> problems. I suppose #138788 should be reopened.

My experience doesn't really match Mozilla bug #83289. I think it's
more related to Mozilla bug #63336, which unfortunately has been
targeted as "future."

FWIW, I think I started seeing this problem when I switched my X server
From=2075 dpi to 100 dpi. Of course, a lot of stuff happened at around
the same time, so it's hard to say. Does Mozilla use the X server's dpi
settings at all?

=2D-=20
Hubert Chan <hub...@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE89oo4rynHGRJLYfoRAvNCAJ933S+yf0i2xr0bC1o4nRyVVx2pOwCeN1+U
zGT5b0ob3iIS0kwO0CzysBc=
=NzlD
-----END PGP SIGNATURE-----
--=-=-=--

Hubert Chan

unread,
May 30, 2002, 5:07:55 PM5/30/02
to
--=-=-=
Content-Transfer-Encoding: quoted-printable

I added this line:
user_pref("browser.display.screen_resolution", 96);
to my .galeon/mozilla/galeon/prefs.js file, and it seems to have fixed
it. Maybe try fiddling around with the 96. (Mozilla has an entry in
the preferences dialog to change this, but Galeon doesn't.)

=2D-=20
Hubert Chan <hub...@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE89pR0rynHGRJLYfoRAulhAJ9SACQb0fYEwRU1WqWAkaZOlKb/FACeNaX/
jrr4jsisSzsVPJOPSWYlb0M=
=5NAZ

Peter Whysall

unread,
May 30, 2002, 5:14:55 PM5/30/02
to

--=-qLogbZVDhjjPwvsJSLaJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2002-05-30 at 22:06, Hubert Chan wrote:
> I added this line:
> user_pref("browser.display.screen_resolution", 96);
> to my .galeon/mozilla/galeon/prefs.js file, and it seems to have fixed
> it. Maybe try fiddling around with the 96. (Mozilla has an entry in
> the preferences dialog to change this, but Galeon doesn't.)

Positive result here - I did have it set to "system setting", and
flipping it to 96 has cured it for me.

Thanks.

Peter.

--=20
Peter Whysall
peter....@ntlworld.moc
The TLD in my email address is sdrawkcab.
Debian GNU/Linux 3.0 sid -- kernel 2.4.18

--=-qLogbZVDhjjPwvsJSLaJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA89pY7lVWixHgFVeURApqxAJ9/dy5BJr0slSZjbtM4ATBnleoKiACguOie
tys1StMWuCAjVo69pHW1UwE=
=2U1q
-----END PGP SIGNATURE-----

--=-qLogbZVDhjjPwvsJSLaJ--

0 new messages