It appeared to be a common issue regarding ActiveX + IE.
We need to call TranslateAccelerator() so the IE will be able to process the tab key.
I’m new to Windows/ActiveX programming so I don’t really know where is the place in the code to do it.
I saw some snippets of code that do it in a CALLBACK functions like the CALLBACK activeXHookWndProc() in juce_win32_ActiveXComponents,
others do it in a HHOOK objects.
You can’t just create a new window class - the window already has a class! I guess I’d have to add the TranslateAccelerator call somewhere in the normal wndproc routine. How is it supposed to be called?
I guess you might be able to use win32 calls to find a suitable child HWND, then find its ComponentPeer, get its component and then attempt a dynamic_cast <WebBrowserComponent*>… all pretty icky, I’m afraid!
Shlomi: Did you manage to create a working fix for this issue?
jules: Any chance of getting an official fix for this in the juce codebase?
We’ve run into the problem when we use a browser component showing a web page where there’s form fields to fill with info. Not being able to tab between the fields rather breaks the user experience I’m afraid…