|
Something is fishy. Qt uses opengl on macOS to do backing store for native menus. QtWebEngine runs its own process and uses an opengl shared context to have the renderer be separate from the chromium browser parts.
It is only the QtWebEngine part that is having problems. So how can opengl work for the main app process and not the QtWebEngine process? That makes no sense. The only Qt related Bug I can find is QTBUG-81693 and it seems QtWebengine uses a different test to decide what opengl features to use. That bug lists a workaround code that I may build a test version with just to see if it matters.
|