Closed Bug 6284 Opened 25 years ago Closed 25 years ago

Stop Button doesn't function right

Categories

(Core Graveyard :: Tracking, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 3469

People

(Reporter: thully, Assigned: radha)

Details

(Whiteboard: waiting QA Input)

Kernel 2.2.6, Red Hat 5.2, KDE 1.1, Mozilla M5 w/ Apprunner If I start to load a web page with Mozilla, and then I press the Stop button on the toolbar, the web page continues to load, no matter how many times I press the Stop button. It ends when the web page is finished downloading, but sometimes the progress bar or throbber continues to go.
Assignee: shuang → don
Reassign it to Don for review.
Assignee: don → radha
Component: UE/UI → Apprunner
Priority: P3 → P2
Target Milestone: M6
Radha, is this fixable now?
Status: NEW → ASSIGNED
Target Milestone: M6 → M10
The behavior of stop is quite inconsistent right now. because it has a lot to do with how the netlib & UI threads get to run. We do put in the request to netlib to stop the current load as soon as the stop button is pressed. That is how far we can get. In the most recent builds, the stop button seems to work right to me. But I wouldn't say that this problem is fixed. so, I'm going to push this bug further hoping we will be in better shape when necko comes in.
Component: Apprunner → other
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.
QA Contact: claudius
Whiteboard: waiting QA Input
Making Claudius the QA contact. Can you verify this in recent builds. Please note that clicking stop sometimes may not stop instantly because, 1) this is dependant on when the necko thread gets scheduled and it gets the stop message.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 3469 ***
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.