[Webkit-unassigned] [Bug 110164] New: Web Inspector: provide the id of associated nodes for layers when calling InspectorLayerTreeAgent::getLayerTree()
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Feb 18 16:00:56 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=110164
Summary: Web Inspector: provide the id of associated nodes for
layers when calling
InspectorLayerTreeAgent::getLayerTree()
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: graouts at apple.com
CC: timothy at apple.com, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
apavlov at chromium.org, loislo at chromium.org,
vsevik at chromium.org,
webkit-bug-importer at group.apple.com,
web-inspector-bugs at googlegroups.com
Right now, the layer tree provided by InspectorLayerTreeAgent::getLayerTree() only lists layer ids, but not the id of the layer's associated node. In order to get that id, the front-end needs to call InspectorLayerTreeAgent::nodeIdForLayerId(). However, the frequency of "layerTreeDidChange" events might be high enough that the resulting calls to getLayerTree() and subsequent calls to nodeIdForLayerId() would have the unexpected impacts of obtaining the node ids for layers that were reported too long ago and the layer tree has already changed significantly.
We should let getLayerTree() report node IDs in the returned object without pushing the nodes to the front-end. That way the front-end will be able to use that information without having to request information from the backend with the latency involved.
--
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