Closed Bug 3885 Opened 26 years ago Closed 26 years ago

My "N" just won't stop throbbing (after pressing Stop... ;)

Categories

(Core Graveyard :: Tracking, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 3853

People

(Reporter: elig, Assigned: don)

Details

* TITLE/SUMMARY My "N" just won't stop throbbing, after pressing Stop... ;) * STEPS TO REPRODUCE 0) Launch Apprunner 1) Load a web site (I used www.netscape.com, www.macosrumors.com, etc.) 2) After the site has begun loading, press the "Stop" button one or more times. * RESULT - What happened Status bar says "Document: Done", but the N logo just won't stop throbbing. - What was expected 'N' animation to stop throbbing after stop button pressed (as it does on a page that naturally finishes loading without being prematurely terminated.) * REGRESSION - Occurs On Mac OS Apprunner (3.16.99 optimized build) Win32 Apprunner (3.16.99 optimized build [NT 4, Service Pack 3]) - Doesn't Occur On Linux Apprunner (3.16.99 optimized build --- can't reproduce, but only tried for 2 minutes.) * CONFIGURATIONS TESTED - [Mac] Power Mac 8500/120 (233 Mhz 604e), 64 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.5.1 - [Win32] Vectra VL (233 Mhz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP3. - [Linux] Vectra VL (266 Mhz P2), 96 MB RAM.
Summary: My "N" just won't stop throbbing, after pressing Stop... ;) → My "N" just won't stop throbbing (after pressing Stop... ;)
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 3853 ***
QA Contact: 3853 → 1698
I'll believe it's a duplicate when I see bug #3853 fixed. Until then, QA assigning to myself, and I'm leaving this bug as Resolved/ Duplicate.
Status: RESOLVED → VERIFIED
Okay, okay...verified duplicate in 3.17.99 build.
Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.