"Stop" means STOP means stop means ...

[Jason Kerr]

I forgot to include the version which demo'd the problem - OW 5.1b3 
(and b1,2)

On Nov 9, 2004, at 3:37 PM, Ken Case wrote:

> On Nov 9, 2004, at 9:52 AM, Jason Kerr wrote:
>> I often find that I am unable to make OW _stop_ loading a page (and 
>> all sub-requests). No matter how many times I select the STOP button, 
>> the status indicator still shows that the page is loading. (This 
>> isn't just a problem with the indicator, the Network Activity window 
>> shows that one or more elements of the page are active.)
>
> We have this issue entered in our bug database as:
>
> 	<bug://bugs/17219>: Stop button does not always work

Cool. I'm not familiar with Omni's bug db, is it user-accessible? (I 
assume not, from the missing URL data, but I thought I'd ask.)

> I just fixed an issue where the Stop button would stop a page load but 
> the page status indicators wouldn't notice (so they would go on 
> spinning forever), but I believe there are other circumstances under 
> which the Stop button doesn't work properly.

Yes, there have to be. The instance that 'put me over the top' and made 
me reply wasn't simply a problem with the indicator. The Network 
Activity window showed an image download as aborted, but clearly either 
the download or abort wasn't complete as it was still listed. (As I 
said in my original message, I'm assuming that elements/loads are 
removed from the activity 'tree' as they are completed and this is what 
the Network Activity window displays.)

> To fix other instances of this problem, it would be helpful to have a 
> clear description of when you're seeing the Stop button fail, 
> something which I can use to reproduce the problem here.  For example, 
> something like this would be great:
>
> 	Procedure:
>
> 		1. Enter [page x] in the URL field, then hit return
> 		2. Wait until some text starts to appear
> 		3. Click Stop before the images finish loading
>
> 	Expected Result: The images should stop loading.
> 	Actual Result: The images continue to load.

I'll certainly try - but unfortunately, these 'hanging loads' are not 
repeatable. That is, following your listed procedure does not always 
produce the same results. I know, I've tried for my own benefit to no 
avail. I suspect that the status of network interaction has a 
significant role in the 'hanging stop', making reproduction tricky.

For example, the site that hung yesterday was 
http://www.regenttheatre.com/seating_chart.html .

When I first loaded the page, some element wasn't loaded completely 
(pro'ly a graphic); I clicked stop, it didn't. I clicked again, 
etcetera, to no avail. I closed the tab and later loaded again, 
clicking stop before the page was complete; no problem.

In this example, the page hadn't completed loading when I clicked stop. 
I'm not sure if this is true for the other cases. I'll keep track.

jason