[Webkit-unassigned] [Bug 113595] New: Web Inspector: associating objects with dom elements
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Mar 29 12:10:16 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=113595
Summary: Web Inspector: associating objects with dom elements
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Enhancement
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: tj at vision-media.ca
CC: keishi at webkit.org, pmuellr at yahoo.com,
pfeldman at chromium.org, yurys at chromium.org,
apavlov at chromium.org, loislo at chromium.org,
vsevik at chromium.org,
web-inspector-bugs at googlegroups.com
The ability to associate objects with dom elements, and making this easy to inspect would be great for inspecting high density client-side applications. Primarily because it is often difficult to single out objects with console.log() calls without setting up a bunch of conditionals.
I whipped up https://github.com/component/inspect as an example, and while this technique works fine there's still quite a bit of indirection, you have to:
- add this component
- associate the data
- click the element in web inspector
- invoke inspect($0)
I would love the ability to find the dom element, right click and have a context menu item to inspect it. As far as making this a generic solution I'm not sure what would be best. Maybe an "Inspect" context menu item could simply console.log($0) or similar. The JavaScript portion is also obviously too opinionated, maybe a better solution would just be to add the ability to extend the context menu from scripts? I was also trying to find out if $0 was exposed to scripts at all so my inspect($0) hack could simply be inspect().
--
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