Yes, that works! It looks like it takes an object of one of these forms PHID-DREV-xxxx (a revision), PHID-DIFF-xxxx (a specific diff in that revision), or a PHID-HMBB-xxxx (a buildable).

Thanks, in the last option, what kind of thing should I pass into harbormaster.queryautotargets for the objectPHID? If I leave it blank I get

{"result":null,"error_code":"ERR-CONDUIT-CORE","error_info":"No such object \"\" exists."}

My request was

{
  "targetKeys": [
    "arcanist.unit"
  ]
}

Thanks -- it's hugely helpful to know that Phabricator already merges coverage!

Two follow-up questions, as I'm stuck again, although further down the road:

Yes, thanks! That flow looks like it will work.

Thanks for adding me to this issue! Please don't rely on mouseovers/hovering. I want to be able to just look at the results and see which ones are relevant without having to move my mouse.

@jhurwitz: both #2 and #3 are a big improvement. Others: I don't have enough context, I'll let you all sort this out from here.

Well I felt insulted by your quick "that's a feature / there's a workaround" response. We'd have to update hundreds of wiki pages to address this. Surely there's some CSS in a central place we can tweak?

@chad: It's ugly bordering on unusable in all of Remarkup, for all installs. So yes.

It is a usability issue though. See for yourself: https://www.dropbox.com/s/qa2oexmuc7sobty/Screenshot%202015-04-27%2014.58.52.png?dl=0