Ok, so here's the problem as we know it. When the control is created on a form, the HTML Editor surface (NOT the HTML Editor itself) gets the focus and the caret is displayed.

Further, if the HTML Editor is on a tab and you click into a control that isn't on the tab, the HTML Editor never loses focus and you can continue to type.

At this time, .net reports that the form's active control is NOT the HTML Editor, but the control you clicked on, even though you get these weird results with the HTMLEditor and typing.

The core problem here seems to be a windows bug, but there has to be a way around it. Anyone have any ideas? This is the last critical bug that I can't work around and it's driving me nuts.

I've finally fixed this once and for all. Tim as the latest code from me that fixes this problem. It's a non-trivial fix (it's a hack really for a bug in the Stream Loading functions from MS) but it gets the job done. *Phew*

James / Tim,


I've been following this control for a few weeks ago, and was going to take a stab at fixing the 'focus' issue, but it sounds like you've already done this -- is the updated code available to try out yet?


Thanks,


Jeff Evans.

My solution is a hack. If you want to try a really good way of fixing the LoadDocument and LoadURL methods getting partial focus (i.e. a cursor) on load, I would be enternally greatful!