Claude Gohier wrote:
I haven't seen this bug for many months. Did you try a clean install or
are you always installing new builds over old ones?
I regulary use the installer-package. Before installing a new build, I
make a clean de-install of the old one. Indeed, I seem not to be alone,
Hi!
Since several mozilla releases on Win2000 (other OSes I didn't have
tested) I recognize an unpleasent effect, when I visit
http://slashdot.org/ (and only there the effect seems to occur!). It's
difficult to describe, so please have a look at my screenshot first:
Sierk Bornemann wrote:
Hi!
Since several mozilla releases on Win2000 (other OSes I didn't have
tested) I recognize an unpleasent effect, when I visit
http://slashdot.org/ (and only there the effect seems to occur!). It's
difficult to describe, so please have a look at my screenshot
Garth Almgren wrote:
I'm not seeing your exact problem, but I am noticing a couple other
rendering glitches on /,
Have a look on my screenshot
http://home.t-online.de/home/sierk.bornemann/test/sshot1.png or go to
the screenshots of http://bugzilla.mozilla.org/show_bug.cgi?id=37589,
then
Sierk Bornemann wrote:
[..]
It's unbelievable for me, that this bug is filed but not fixed since
nearly two years!!
There's a lot of much more important stuff.
These rendering glitches and the ones, you describe, are still nerving
my eyes.
Nerving your eyes? Are you kidding? Gad, if
In article [EMAIL PROTECTED], Sierk Bornemann wrote:
It's unbelievable for me, that this bug is filed but not fixed since
nearly two years!!
Perhaps you should have tried reading the bug. Had you done so, you would
have found that it was fixed in late 2000, as far as anyone could tell,
Garth Almgren wrote:
Sierk Bornemann wrote:
CUT
Yep, I see the same problems and in the same way they might appear or
disappear with scrolling.
But the white line inside the red circle of Sjerk's screenshot shows up as
a black one in Konquerer
It is indeed a bit of a blemish but it is
Sierk Bornemann wrote:
Chris Hoess wrote:
Perhaps you should have tried reading the bug. Had you done so, you
would have found that it was fixed in late 2000, as far as anyone
could tell, and someone reopened it today for what may or may not
even be the same problem.
I think it