You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Target.attachToTarget now returns a sessionId instead of success
Target.detachFromTarget requires sessionId instead of targetId
Target.sendMessageToTarget requires sessionId instead of targetId
These deprecation / changes in Chrome DevTools Protocol will make popup step not work.
Making a commit with codebase update to work with this newer version. Tested on Chrome - version 61.0.3163.100 (Official Build) (64-bit) by verifying expected behavior and validating tagui_chrome.log. Raising this issue for easy reference in future.
The text was updated successfully, but these errors were encountered:
Chrome DevTools Protocol, under Target domain
(https://chromedevtools.github.io/devtools-protocol/tot/Target/),
- Target.attachToTarget now returns a sessionId instead of success
- Target.detachFromTarget requires sessionId instead of targetId
- Target.sendMessageToTarget requires sessionId instead of targetId
These deprecation / changes in Chrome DevTools Protocol will make popup
step not work.
Making a commit with codebase update to work with this newer version.
Tested on Chrome - version 61.0.3163.100 (Official Build) (64-bit) by
verifying expected behavior and validating tagui_chrome.log.
Raising issue #64 for easy reference in future.
kensoh
changed the title
Chrome DevTools Protocol - targetId deprecated in some methods
popup step - Chrome DevTools Protocol - targetId deprecated in some methods
Oct 31, 2017
Under Target domain,
These deprecation / changes in Chrome DevTools Protocol will make popup step not work.
Making a commit with codebase update to work with this newer version. Tested on Chrome - version 61.0.3163.100 (Official Build) (64-bit) by verifying expected behavior and validating tagui_chrome.log. Raising this issue for easy reference in future.
The text was updated successfully, but these errors were encountered: