It seems that I can reproduce this - it isn't that easy to reliably find out that no click happened.
The header is ok and I couldn't find a related bug - so I have no idea.
You could try to use the debug DLL and decrease CefLogSeverity, maybe you get a hint somehow.
The best way to test, whether it is supposed to work or not, is to hack together a small CEF C(++) app - but unfortunately I'm very busy again

Apart from that I would generally advise - if your code happens to be in a Cef-Callback with
Browser param - to use it instead of Chromium.Browser.
This should be more reliable (e.g. makes sure you are in the "right" thread) and even faster.