[Webkit-unassigned] [Bug 53733] Timers can fire after a frame has been put into the page cache

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jan 23 09:21:24 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=53733





--- Comment #7 from Allan Sandfeld <sandfeld at kde.org>  2012-01-23 09:21:23 PST ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > This will be fixed by that patch for https://bugs.webkit.org/show_bug.cgi?id=76063
> > > 
> > > Why this assertion?
> > > 
> > > 76063 repeatedly purports to be about WebKit2 API only yet this is a cross WebProcess-only crossplatform WebCore bug.
> > 
> > Reading through 76063 I now see that it is was more complicated in scope than the claimed "Add a new WK2 API" task.  *sigh*
> 
> With the API old bugs were exposed and fixed.

It should be noted that without the new API it is hard to trigger cases of this bug, making it is practically impossible to test, and I am not going to submit patches without having tested them first. So the API is required.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list