[Webkit-unassigned] [Bug 49048] Web Inspector: Feature Request: links from console to elements/scripts

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Nov 7 23:13:55 PST 2010


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





--- Comment #4 from Pavel Feldman <pfeldman at chromium.org>  2010-11-07 23:13:55 PST ---
(In reply to comment #3)
> Thanks Pavel for your timely fix.
> 
> However, I'd still argue (1). I think making elements in the console link to Elements panel could be useful. A scenario might be that a developer uses console.log to print an element with page script (where inspect() is not accessible), and then inspects them in the console. The developer could achieve this in another way, but different developers might have different habits in debugging. 
> 
> Another benefit of (1) is that an extension can interact with the inspector in this way without using the inspector extension API. For example, a compatibility detection extension finds a problematic element and print it with console.log(), then the user can inspect the element to find more details.

Today, if you use console.dirxml or console.dir, you get the element dumped into the console. We can provide a "Reveal in Elements Panel" context menu item on such elements. Would that cover your scenario?

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



More information about the webkit-unassigned mailing list