| Summary: | Web Inspector: "document" and "window" are evaluated on the page a lot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Timothy Hatcher <timothy> | ||||
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bburg, graouts, inspector-bugzilla-changes, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Local Build | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
I'm 90% sure this is the result of our workaround to obtain a remote object for the document because we can't do it via protocol directly. |
Created attachment 276957 [details] Screenshot Steps: 0) Make isWebKitInternalScript() and isWebKitInternalScript() always return false. 1) Inspect about:blank 2) Evaluate something in the console. 3) Click around i the Debugger sidebar. I would see a new "document" and "window" eval happen by just viewing a script resource. DOMTree.js does evaluate "document" in _requestRootDOMNode, but I would not expect it to happen like this. I am not sure where the "window" eval comes from.