Bug 20803
| Summary: | JS objects in the console should be snapshots instead of live objects | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ojan Vafai <ojan> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bburg, dglazkov, graouts, irae, joepeck, rik, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Ojan Vafai
This matches user-expectation better and solves problems of needing to keep anonymous or otherwise unreferenced objects from being garbage collected.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Blaze Burg
I don't think this should be the default. But, maybe it could be an option for some RemoteObject uses, like objects from breakpoint actions.
Radar WebKit Bug Importer
<rdar://problem/15911174>
Timothy Hatcher
Works fine now. We fixed this.
Timothy Hatcher
Wrong bug.
Iraê
I think being the default is a good idea. I constantly have to console.log(JSON.stringify(obj)) to understand better large applications with a lot of different states.
When I want just a reference to the object itself I can console.log outside of the app lifecycle or assign it to window.copyOfObj = obj;
Timothy Hatcher
Is this better in the nightly / Safari 9 now that we have snapshot previews?
Timothy Hatcher
Object previews fixed this for what most developers expect and are satisfied with in other browsers.