Closed Bug 274941 Opened 20 years ago Closed 20 years ago

Scrollbar locks in Mac OS 9

Categories

(SeaMonkey :: UI Design, defect)

Product:
SeaMonkey
Component:
UI Design
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: thalltda, Unassigned)

Details

I've used the default Modern skin in Netscape 7.0 for Mac OS 9.  The problem is that after a while, the 
scrollbar will sometimes stop responding and I can only move by clicking on arrow buttons provided at 
the bottom of the scroll bar. It's inexcusably annoying.

I have ignored the prerequisites for first testing in a Mozilla build (rather than Netscape) and for 
reporting bugs in software over two weeks old.  Those rules are ridiculous, I had this problem months 
ago, and I should not be expected to upgrade more than every two weeks.
(In reply to comment #0)
> I've used the default Modern skin in Netscape 7.0 for Mac OS 9.  The problem
is that after a while, the 
> scrollbar will sometimes stop responding and I can only move by clicking on
arrow buttons provided at 
> the bottom of the scroll bar. It's inexcusably annoying.
> 
> I have ignored the prerequisites for first testing in a Mozilla build (rather
than Netscape) and for 
> reporting bugs in software over two weeks old.  Those rules are ridiculous, I
had this problem months 
> ago, and I should not be expected to upgrade more than every two weeks.

Then unless you or anyone can reproduce this in a current Mozilla build, go
report the bug to Netscape.  7.0 is a year and a half old.  Mozilla no longer
even supports OS 9.

Netscape bugs are not accepted here in any event unless they reproduce in Mozilla.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
So the fact that I'm using a browser almost directly based on Mozilla doesn't mean that it's a Mozilla 
bug?  Nice try.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
(In reply to comment #2)
> So the fact that I'm using a browser almost directly based on Mozilla doesn't
mean that it's a Mozilla 
> bug?  Nice try.

No, but it's a fact that we don't support Mac OS 9 anymore and Mozilla 1.2.1 was
the last version of Mozilla officially released for Mac OS 9 (I think). Netscape
7.0 is based on Mozilla 1.0. No one is working on this old code anymore. Your
bug report won't change this.

There is a unofficial version of Mozilla 1.3.1 for Mac OS 9:
http://wamcom.org/latest-131/ Maybe this version works better for you.

Also the rule to use a recent Mozilla build when reporting bugs isn't
ridiculous. Bug reports about bugs that were fixed some months ago are not useful.

Remember, bugzilla.mozilla.org is not a support medium, but a tool for testers
and developers to organize their work on Mozilla products. If installing a
recent build is something you don't want to do, well fine, but then it is very
unlikely that you can contribute something useful to bugzilla.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → INVALID
why have I been added to the CC list for a bug I've never heard of?
Status: RESOLVED → VERIFIED
Stop closing this bug.
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
(In reply to comment #3)
> (In reply to comment #2)
> > So the fact that I'm using a browser almost directly based on Mozilla doesn't
> mean that it's a Mozilla 
> > bug?  Nice try.
> 
> No, but it's a fact that we don't support Mac OS 9 anymore and Mozilla 1.2.1 was
> the last version of Mozilla officially released for Mac OS 9 (I think). Netscape
> 7.0 is based on Mozilla 1.0. No one is working on this old code anymore. Your
> bug report won't change this.
The age of the code does not mean that the bug does not remain in a newer build.  I fail to see how 1.0 
is "old" when compared to 1.2 or 1.4—a .4 is NOT a big difference.
> 
> There is a unofficial version of Mozilla 1.3.1 for Mac OS 9:
> http://wamcom.org/latest-131/ Maybe this version works better for you.
Thanks, but I no longer use OS 9.
> 
> Also the rule to use a recent Mozilla build when reporting bugs isn't
> ridiculous. Bug reports about bugs that were fixed some months ago are not useful.
Can someone show me evidence that it was fixed "some months ago"?  or at all?
> 
> Remember, bugzilla.mozilla.org is not a support medium, but a tool for testers
> and developers to organize their work on Mozilla products. If installing a
> recent build is something you don't want to do, well fine, but then it is very
> unlikely that you can contribute something useful to bugzilla.
I never tried to use bugzilla as a support medium.  However, if I find a bug in Mozilla or a Mozilla-
based Netscape browser, I *will* report it.  there's no reason that I shouldn't report older bugs, now is 
there?  It is unrealistic to expect me to install a new build every 20 minutes, and 7.0 is the latest 
Netscape available for me.  Thus, as the latest software available for a platform, I expect it to work 
properly.

***STOP CHANGING THIS BUG TO "INVALID" OR FACE CONSEQUENCES.  I WILL REPORT YOU TO 
MOZILLA!***
Stop adding me to the CC list -- someone please keep the "reporter" from doing this!
Please read http://www.mozilla.org/quality/bug-writing-guidelines.html.

FWIW I can tell you that the bug seems to be gone, since I can't repro the
problem with a recent nightly build on Mac OS 10.3.6...
(In reply to comment #8)
> Please read http://www.mozilla.org/quality/bug-writing-guidelines.html.
> 
> FWIW I can tell you that the bug seems to be gone, since I can't repro the
> problem with a recent nightly build on Mac OS 10.3.6...


Please note that Mac OS X (what you tested) and Mac OS 9 are entirely different operating systems and 
that is why you were unable to reproduce the bug.  Show me it not happening on an OS 9 system and I 
will let you go.  Not that the bug is really reproducible.

By the way, illyanep@gmail.com, the person who keeps removing himself from the CC: list, was actually 
the programmer who added this bug to the software.  I would appreciate it if people would stop 
gratuitously removing him from the list and make him take responsibility for his own faulty code.
(In reply to comment #9)
> (In reply to comment #8)
> > Please read http://www.mozilla.org/quality/bug-writing-guidelines.html.
> > 
> > FWIW I can tell you that the bug seems to be gone, since I can't repro the
> > problem with a recent nightly build on Mac OS 10.3.6...
> 
> 
> Please note that Mac OS X (what you tested) and Mac OS 9 are entirely
different operating systems and 
> that is why you were unable to reproduce the bug.

Mac OS 9 is no longer supported by Mozilla. This bug report is useless when this
is a bug that only happens on Mac OS 9, because it will never be fixed anyway.
So perhaps WONTFIX is a more appropriate resolution you can live with.

(But this bug is also INVALID because you reported a bug in an much to old
Mozilla version/Netscape 7.0.)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WONTFIX
HOW IS THE BUG TOO OLD???  I SHOULDN'T HAVE TO UPGRADE MY SOFTWARE ONCE A DAY!!!
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
(In reply to comment #11)
> HOW IS THE BUG TOO OLD???  I SHOULDN'T HAVE TO UPGRADE MY SOFTWARE ONCE A DAY!!!

In order to write useful bug reports you have to reproduce the bug with a recent
build. The version you are using is several years old already and the OS on
which this bug occurs isn't supported anymore by Mozilla.

Like I said before... you don't have to use a recent build. But if you don't
want to, you shouldn't file bugs in bugzilla.

From http://www.mozilla.org/quality/bug-writing-guidelines.html:

"Next, be sure that you've reproduced your bug using a build released within the
past three days. Our development process moves at lightning speed, and the bug
you've found may already have been fixed. (Nightly builds can be downloaded from
the mozilla.org binaries page.)

If you've discovered a new bug using a current build, report it in the guided
Bugzilla entry form."

Also notice the big red box at the top of that page about reporting Netscape-bugs.

These are the rules and even writing in UPPERCASE won't change them. ;-) So
please leave this bug resolved now. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WONTFIX
> "Next, be sure that you've reproduced your bug using a build released within the
> past three days. Our development process moves at lightning speed, and the bug
> you've found may already have been fixed. (Nightly builds can be downloaded from
> the mozilla.org binaries page.)
That is RIDICULOUS! Why should I upgrade software every three days??
> 
> Also notice the big red box at the top of that page about reporting Netscape-bugs.
It's not a Netscape bug.  It's a Mozilla bug that also occurs in a Netscape product.
> 
> These are the rules and even writing in UPPERCASE won't change them. ;-) So
> please leave this bug resolved now. Thanks!
I will not leave the bug resolved until someone where gives me a reason to.  So far there's been nothing 
but ****.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
> I will not leave the bug resolved until someone where gives me a reason to.

Definition of WONTFIX: The problem described is a bug which will never be fixed.

(see https://bugzilla.mozilla.org/page.cgi?id=fields.html#resolution)

Since this is a Mac OS 9-specific bug (see comment 8) and Mac OS 9 is not
supported anymore (this means no one fixes Mac OS 9-specific bugs anymore), this
bug will never be fixed.

Also this bug is INVALID...
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WONTFIX
****! **** YOU FOR NOT FIXING THE FAULTY SOFTWARE YOU WRITE!!!!!!!!!!!!
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
> I will not leave the bug resolved until someone where gives me a reason to. 
So far there's been nothing 
> but bullshit.

I see a lot of good reasons:

a) Mac OS 9 is not supported
b) It's on a Netscape product
c) Even if we supported Mac OS 9 your version is too old for a bug report. --

I suggest you try the 1.2.1 release or the unofficial release mentioned earlier. 

-->wontfix
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WONTFIX
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.