<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: add explicit version checking for legacy backends"
href="https://bugs.webkit.org/show_bug.cgi?id=148680#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: add explicit version checking for legacy backends"
href="https://bugs.webkit.org/show_bug.cgi?id=148680">bug 148680</a>
from <span class="vcard"><a class="email" href="mailto:joepeck@webkit.org" title="Joseph Pecoraro <joepeck@webkit.org>"> <span class="fn">Joseph Pecoraro</span></a>
</span></b>
<pre>I think we could just give the Inspector domain a version number. And bump it whenever we want/need to.
{
"domain": "Inspector",
"constants": [
{ "name": "Version", "value": 1000 }
]
}
Would generate:
InspectorBackend.registerConstant("Inspector.Version", 1000);
We could retroactively add it to Legacy Inspector-iOS-*.json files. And add WebInspector.BackendVersions.iOS7-9 constants (700, 800, 900) to the frontend.
That said, I still think we should be feature checking the protocol when possible. This would only be used for when we can't easily do that (like new properties in types).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>