On Mon, 2005-05-16 at 20:27 +0200, Loïc Minier wrote:
>  It's really strange you don't suffer from such problems with Mozilla.

  Aha!  For some reason, mozilla's fonts are sized differently than
galeon's on my machine, so mozilla doesn't show corruption in the test
case I was using for galeon, but I _can_ get it to show corruption on
some different text.  Sorry about that.
  I was also insufficiently vigorous about trying to find instances of
corruption; by searching diligently, I was able to find corruption even
in galeon at 100 DPI, which I had reported as working previously.  It's
certainly much more subtle at 100 DPI; I'd been running at 100 DPI for
quite a while without seeing it (I used to get it all the time, when I
scrolled), but with effort I was able to find it again at 100 DPI now.
  The short version of the story is that all the browsers get corruption
in all configurations I tested _except_ when screen_resolution is set to
96.  I would therefore recommend reopening the upstream bug, and adding:

// Workaround for off-by-one display errors
// See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=148916
pref("browser.display.screen_resolution", 96);

  ... to Debian's /etc/mozilla/prefs.js until upstream gets a fix
together.  That's assuming, of course, that someone else can reproduce
this, and it's not just monkeys in my /usr/bin or something.  A quick
sanity check would be to open mozilla (with 100 DPI and
screen_resolution set to 0) and drag an xterm over part of the URL bar
and back off again: On my system, the obscured part of the URL bar gets
shifted vertically by a pixel or so.
  BTW, adding 'user_pref("browser.display.screen_resolution", 96);'
to /etc/mozilla/prefs.js does nothing in any browser AFAICS, but adding
'pref("browser.display.screen_resolution", 96);'
to /etc/mozilla/prefs.js fixes it in all browsers for me.
 
>  Did you check for corruptions of your display with:
>  - firefox
>  - epiphany
>  - galeon

  Yes; all of those have corruption at 91x90 and 100x100 DPI (with
screen_resolution set to 0), but not when screen_resolution is set to
96.  For the record, the full results are below.  They're very boring.
The corruption test I was using was to drag an xterm chaotically around
over the browser text.

---+ mozilla 1.7.8-1

1. DPI 91x90, screen_resolution 0: corruption in the page
("home/awards/contribute" at bottom of slashdot) and in the URL bar
2. DPI 100x100, screen_resolution 0: corruption in the page
("home/awards/contribute" at bottom of slashdot) and in the URL bar
3. DPI 91x90, screen_resolution 96: no corruption AFAICS
4. DPI 91x90, xprint voodoo: corruption in the page
("home/awards/contribute" at bottom of slashdot) and in the URL bar

---+ galeon 1.3.20-1

1. DPI 91x90, screen_resolution 0: corruption in the page (summary &
flags text on bugzilla)
2. DPI 100x100, screen_resolution 0: corruption in the page ("all
trademarks and copyrights" at bottom of slashdot)
3. DPI 91x90, screen_resolution 96: no corruption AFAICS
4. DPI 91x90, xprint voodoo: corruption in the page (fortune blurb at
bottom of slashdot)

---+ firefox 1.0.4-1

1. DPI 91x90, screen_resolution 0: corruption in the page ("all
trademarks and copyrights" at bottom of slashdot) and in the tab labels
2. DPI 100x100, screen_resolution 0: corruption in the page ("all
trademarks and copyrights" at bottom of slashdot) and in the tab labels
3. DPI 91x90, screen_resolution 96: no corruption AFAICS
4. DPI 91x90, xprint voodoo: corruption in the page ("all trademarks and
copyrights" at bottom of slashdot) and in the tab labels

---+ epiphany 1.4.8-3

1. DPI 91x90, screen_resolution 0: corruption in the page (story blurbs
on slashdot)
2. DPI 100x100, screen_resolution 0: corruption in the page ("all
trademarks and copyrights" at bottom of slashdot)
3. DPI 91x90, screen_resolution 96: no corruption AFAICS
4. DPI 91x90, xprint voodoo: corruption in the page (story blurbs on
slashdot)

>  Please also try with:
>     pref("print.xprint.font.rejectfontpattern",.
>          
> "fname=-dt-.*;scalable=.*;outline_scaled=false;xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*");

  That didn't help; that config is "xprint voodoo" above.  For that
test, I left the screen_resolution pref at 0.

>  I asked for the upstream bug to be reopened, thinking this probably
>  ain't Galeon specific.

  It certainly doesn't look like it is.  It might be a general (font-)
rendering problem on my system, I guess, though I've not seen this sort
of corruption in any other application that I can remember.  Certainly
the corruption in the URL bar of mozilla and the tab labels of firefox
argue for it being specific to me; if that were happening everywhere,
I'd think someone would have noticed before now. :-)

-- 
Andrew Moise <[EMAIL PROTECTED]>


Reply via email to