We probably have enough information on the dashboard so that given two chrome commit positions A and B, to find, say, the first clank hash A' with src@A and the last clank hash B' with src@B.

Could that be doable? For humans entering manual ranges it's often much easier to think about commit positions rather than, e.g., clank hashes.

Simon: for background on how the dashboard deals with clank revisions, see the discussion in https://github.com/catapult-project/catapult/issues/3014

If a_default_rev were set properly, maybe we could have special handling of multiple revision types in the bisect dialog? It would definitely add complesity, so would depend how big a problem this is.

So if I'm understanding correctly, the suggestion is if you're on clank and input chromium revisions, to auto-match them to when clank rolled them and fill in the corresponding clank hashes?