[Webkit-unassigned] [Bug 7657] REGRESSION: digg.com comments page so slow it seems like a hang (image load events mistaken for page load)

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=7657





------- Comment #27 from rdas7 at yahoo.com  2006-06-13 02:21 PDT -------
(In reply to comment #26)
> From the point of view of the "stop JavaScript infinite loop" code, there's no
> difference between code that takes a long time to run and code that loops
> forever.

I don't think it's up to webkit dev to "guard" against what could be described
as faulty programming (it will always be possible to write buggy code!). In
this case, it's a problem with how digg was coded. They seem to have fixed the
problem now however, as I am no longer experiencing the long-wait.

(In reply to comment #12)
> So I think we probably should not emulate this old Mozilla bug, even though
> digg.com seems to rely on it.

It seems like while this thread is directly related to digg, the "bug" in
question is a more generic interpretation of how load events are handled. So
long as this isn't a bug in how WebKit is actually running the code it's given,
can we mark this bug as closed?


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.