Version information in the browser_protocol.json and `js_protocol.json` are not useful.
Reported by
w...@imaginaryindustries.com,
Mar 30 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.111 Safari/537.36 Vivaldi/1.8.770.50 Steps to reproduce the problem: Basically, I'm writing some tooling that interacts with the chromium remote debugger interface. The remote debugger interface has a json file that specifies it's methods, and also has a version number in it. That version number hasn't been changed while features have been added and removed repeatedly. What is the expected behavior? I'd expect changes to the remote debugging interface to be associated with a change of the remote debugging interface number. This would be a clear indicator that I need to update my interface, and would also provide a definitive way to refer to one version of the interface specification when dealing with bugs in either my software or chromium. As it is, I have no idea why the version number is even there, since it seems like it doesn't ever get changed or updated. What went wrong? People, I assume. Or broken assumptions on my part. Did this work before? N/A Chrome version: Not Relevant Channel: n/a OS Version: Not Relevant Flash Version: Not Relevant
,
Apr 5 2017
,
Apr 6 2017
Quite a bit was changed in the last year around our protocol, versions and the partition of it. We created a github page to help a bit with this. We understand that the documentation in using protocol for stable environments is a little difficult and would like to make this better. Can you please file an issue here: https://github.com/ChromeDevTools/devtools-protocol/issues We'll discuss the issues with using protocol and hopefully update some documentation about what the version number means and what is "safe" to use and "not safe". Thanks! (marking WontFix in lue of it going to github issue)
,
Apr 7 2017
Ok. Created https://github.com/ChromeDevTools/devtools-protocol/issues/6 in response. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Apr 4 2017