[Webkit-unassigned] [Bug 53659] Web Inspector: Better support for finding "leaked" DOM

[bugzilla-daemon at webkit.org]

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





--- Comment #8 from anton muhin <antonm at chromium.org>  2011-02-07 03:54:14 PST ---
(In reply to comment #6)
> I'm not completely following the discussion here, but have a meta-comment.
> 
> I suspect the scenario you're wanting to track may be something that not everyone needs.  And on the flip-side, there are other similarly-scoped scenarios that other people have, that they'd like to have specialized debugging support for.
> 
> What I'm wondering is: is there some way that we can give you some low-level tools (JS APIs, at this point, I guess) so you could build the analyzer you want, without having to wait for it to show up in Web Inspector?
> 
> Turn a default/command-line option on, to enable the additional JS APIs available.

Patrik, the problem is what exact kind of API you want?  Plus those low-level APIs sometimes can expose security stuff.  But we can always run a private version of Chromium with some additional stuff exposed and somehow (e.g. C++ defines, or something else) disable it for prod builds.

But main problem is what kind of API people want and who have enough time and interest to implement them :)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.