[Webkit-unassigned] [Bug 91285] New: confirm() pauses thread execution but doesn't prevent new, default, events from firing.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 13 14:42:11 PDT 2012


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

           Summary: confirm() pauses thread execution but doesn't prevent
                    new, default, events from firing.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Event Handling
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ryan at ryanalbrecht.ca


Created an attachment (id=152338)
 --> (https://bugs.webkit.org/attachment.cgi?id=152338&action=review)
Test case illustrating confirm() not blocking new event threads

Calling confirm() inside an event handler does not stop the dom from creating new, default events, while the confirm box is waiting to be dismissed. This makes it impossible to prevent those default events from triggering as the event context is lost when the thread is paused.

See attached test case.
Tested in Firefox 11 and WebKit r122567

-- 
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