I'm not positive what change will be made here, if any, because this is actually Chrome's own highlighting for accessibility purposes. If you tab/shift-tab, you'll see what I mean. It's generally important to leave that for accessibility. We have some code that detects mouse vs keyboard navigation to hide it, but we can't proactively hide it until we know what interaction type is used.
Saying that, the most recent version of Chrome does support a new pseudo-class that roughly does the detection for us which we might be able to use, but it's not well supported at all.