Basically, if I have a TAdvRichEditor on a form with a TEdgeBrowser on it and I select some text in the TEdgeBrowser, the TAdvRichEditor does not properly get the focus when I click in it. I can double click in the TAdvRichEditor and even select text, but it doesn't get focus and I can't edit it.
I have to click on another control (such as the button on the form) before the TAdvRichEditor accepts focus when I click in it.
I have experimented with putting message boxes in the OnExit and OnEnter events of both the TAdvRichEditor and the TEdgeBrowser, and neither fire when clicking in the TAdvRichEditor. The TEdgeBrowser's OnExit does fire when I click the button.
As this only seems to affect the TAdvRichEditor (I've tried with the regular TMemo and there's no problem) it looks to me like the problem is with TAdvRichEditor...
(Same problems happen if I create this demo app in Delphi...)
It looks like this is rather something in the Embarcadero TEdgeBrowser.
I tested this here with our TAdvWebBrowser (that also wraps Edge Chromium) and I could not reproduce this.
If this behaviour is identical with all other components, then I'd agree with you. As it is, I the only other component that where this behaviour occurs with with the TAdvStringGrid. I'm not saying you're wrong - it's just weird that the problem seems to be selective about which components it occurs with.
One interesting thing is that if I place a TAdvStringGrid and TAdvRichEditor on the same form, the bad behaviour only occurs on the first control I switch focus to.
For example, I highlight something in the Edge browser, I then click on TAdvStringGrid - nothing happens and the Edge browser's OnLeave does not fire. But if I now click on the TAdvRichEditor it properly gets the focus and the Edge Browser's OnLeave event occurs. It feels like something is intercepting a Windows event but not handling it 100% correctly
I will, of course, raise a support case with Embarcadero, but I think they'll say it's the TMS components that have the problem and, as they can't replicate the problem with standard components, they can't help...
When I get a chance at the weekend, I'll trap with Windows events that occur on the form and log them - they may provide a clue about what is is going on...
