Long term it would be great if we could use some browser provided id in the renderer (e.g. process.frame_tree_node_id). Short term perhaps it's sufficient to send DevTool's renderer generated FrameId to the browser with the proviso it shouldn't be trusted too much (because it came from the renderer). If we do go down that route we should remove it once a longer term solution is available.
Comment 1 by alexclarke@chromium.org
, Apr 26 2017