Bug 10688 - Inspector painfuly slow when Drosera is attached
Summary: Inspector painfuly slow when Drosera is attached
Status: CLOSED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 420+
Hardware: Mac (PowerPC) OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
: 16534 (view as bug list)
Depends on: 17770
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-02 01:36 PDT by Hrvoje Blazekovic
Modified: 2008-05-17 09:55 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hrvoje Blazekovic 2006-09-02 01:36:06 PDT
Open a page in web kit, inspect an element with inspector. Everything works fine. Start and attach drosera. Now selecting elements in the inspector is wery slow. I tried out what I usualy do in firefox with firebug. Select a element and step trough javascript on that element.
Comment 1 Timothy Hatcher 2006-09-03 11:42:46 PDT
Slow because Drosera is debugging the inspector's JS also. We need a way to tell Drosera to debug just one WebView (and ignore the rest).
Comment 2 Alexey Proskuryakov 2006-09-04 12:11:56 PDT
Confirming per the above comment.
Comment 3 Adam Roben (:aroben) 2008-03-13 23:00:09 PDT
The situation will be improved once bug 17770 is fixed. However, we may still want a way to exclude WebViews from sending cross-process calls to Drosera about their JS execution.
Comment 4 Adam Roben (:aroben) 2008-03-13 23:22:44 PDT
*** Bug 16534 has been marked as a duplicate of this bug. ***
Comment 5 Kevin McCullough 2008-05-16 14:06:05 PDT
Drosera is going away and JS debugging is now happening in the WebInspector.
Comment 6 Timothy Hatcher 2008-05-17 09:55:58 PDT
Closing since Drosera has been replaced by the new Web Inspector debugger. Moving to the New Bugs component so the Drosera component can be closed and removed.