Cefsharp browser gets stuck

[2019mmp003]

Hello everyone,

I am facing this issue of cefsharp browser getting stuck.
We have created a plug-in that uses a cefsharp browser embedded into Revit,
it gets loaded up on click of a button. In the image below we can see the dockable cefsharp
browser window to the right.

From the image above, we can see in the window, there are two buttons highlighted in red boxes. Whenever I click on any one of them it should get highlighted, and if the second one is previously highlighted, it should get dehighlighted, this is the logic implemented, on clicking these buttons some elements gets focussed in revit UI (that is secondary part).  

But, I am facing issue in dehighlighting. Suppose at start none of the button is clicked and both are in dehighlighted state. Now if I click on first one it gets highlighted. Now keeping the first one in highlight state, if I click on other button the second one gets highlighted, but the first one doesn't dehighlight. Both are shown highlighted as shown in image below.

Both the buttons remain highlighted unless an action is performed by the user, either double click on the page, or scrolling the page up or down. I think that whenever I click on any of these buttons, the cefsharp browser page is getting freezed or stuck. Due to which both buttons are shown highlighted. I am not facing this issue when debugging on chrome browser. Also this issue is faced only on Revit 2018 and 2019 plugins, but works fine with Revit 2020 and later versions. 

The cefsharp version used is 65.0.1 for Revit 2020, and 57.0.0 for revit 2018 and 2019.

Please let me know if there are any ways to solve this.

Also please be free to ask, if there is any other information I needed to provide.

[jeremy_tammik]

That sounds like a tricky problem. However, I wonder whether it really has anything to do with the browser, or whether you are just having problems retaining focus at the appropriate moments in your dockable panel. Can you minimise  your code to isolate the problem to prove exactly what is causing this issue? Do you have a similar, simpler dockable panel hosting the two buttons without the browser, proving that the buttons work well in that case?