Skip to content

Supported features and API

Kenneth Auchenberg edited this page Apr 15, 2016 · 3 revisions

The Edge Diagnostics Adaptor implements two endpoints:

  1. HTTP Endpoint
  2. Web Socket endpoint

HTTP endpoint

See HTTP endpoint for details and supported API.

Chrome Debugger Protocol API

The following API of the Chrome Debugger Protocol is supported:

Area Method
DOM getDocument
DOM getAttributes
DOM hideHighlight
DOM highlightNode
DOM setInspectModeEnabled
DOM requestChildNodes
DOM pushNodesByBackendIdsToFrontend
DOM pushNodeByPathToFrontend
DOM pushNodeByPathToFrontend
CSS getInlineStylesForNode
CSS getMatchedStylesForNode
CSS getComputedStyleForNode
CSS getStyleSheetText
CSS setPropertyText
Page enable
Page reload
Page navigate
Page getCookies
Page getResourceTree
Page getAnimationsPlaybackRate
Page getNavigationHistory
Page deleteCookie
Page setOverlayMessage
Page canScreencast
Page canEmulate
Page screencastFrameAck
Page startRecordingFrames
Page stopRecordingFrames
Page startScreencast
Page stopScreencast
Page setShowViewportSizeOnResize
Runtime enable
Runtime evaluate
Runtime callFunctionOn
Runtime getProperties
Debugger canSetScriptSource
Debugger disable
Debugger enable
Debugger evaluateOnCallFrame
Debugger getScriptSource
Debugger removeBreakpoint
Debugger pause
Debugger resume
Debugger setBreakpointByUrl
Debugger stepInto
Debugger stepOut
Debugger stepOver
Clone this wiki locally