Summary: | WebKit2: Implement JavaScript unresponsiveness timer/callbacks | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Sam Weinig <sam> | ||||
Component: | New Bugs | Assignee: | Sam Weinig <sam> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | webkit-ews | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Other | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Sam Weinig
2011-04-22 15:28:16 PDT
Created attachment 90783 [details]
Patch
Attachment 90783 [details] did not build on qt: Build output: http://queues.webkit.org/results/8495589 Comment on attachment 90783 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90783&action=review > Source/WebKit2/UIProcess/WebPageProxy.cpp:1949 > + // Since runJavaScriptPrompt() can spin a nested run loop we need to turn off the responsiveness timer. Did you mean for this to be shouldInterruptJavaScript? Comment on attachment 90783 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90783&action=review > Source/WebKit2/UIProcess/API/qt/qwkpage.cpp:503 > + 0 /* saveDataToFileInDownloadsFolder */ Missing a comma here, which is what probably broke the Qt build. Committed r84702: <http://trac.webkit.org/changeset/84702> |