mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
972aedb76b
There is some ambiguity about whether ScheduleComposite will necessarily trigger a composite all the way to nsWindow::DrawWindowUnderlay. Android robocop tests assume it will, because they rely on DrawWindowOverlay being called so they can take a screenshot and make progress, but this is a very fragile assumption. They also rely on the entire window being painted, which is also a fragile assumption. This patch improves the situation by explicitly invalidating the current window area when Android Java code needs to trigger a composite. This avoids regressions from future patches in this series which make composition bail out when there is nothing invalid. The resulting setup is still a bit fragile for my taste but I'm not sure what the ideal solution would be. |
||
---|---|---|
.. | ||
android | ||
bindings | ||
jni | ||
AndroidBridge.cpp | ||
AndroidBridge.h | ||
AndroidBridgeUtilities.h | ||
AndroidContentController.cpp | ||
AndroidContentController.h | ||
AndroidDirectTexture.cpp | ||
AndroidDirectTexture.h | ||
AndroidGraphicBuffer.cpp | ||
AndroidGraphicBuffer.h | ||
AndroidJavaWrappers.cpp | ||
AndroidJavaWrappers.h | ||
AndroidJNI.cpp | ||
AndroidJNIWrapper.cpp | ||
AndroidJNIWrapper.h | ||
GeneratedJNIWrappers.cpp | ||
GeneratedJNIWrappers.h | ||
GfxInfo.cpp | ||
GfxInfo.h | ||
moz.build | ||
NativeJSContainer.cpp | ||
NativeJSContainer.h | ||
nsAndroidProtocolHandler.cpp | ||
nsAndroidProtocolHandler.h | ||
nsAppShell.cpp | ||
nsAppShell.h | ||
nsClipboard.cpp | ||
nsClipboard.h | ||
nsDeviceContextAndroid.cpp | ||
nsDeviceContextAndroid.h | ||
nsIAndroidBridge.idl | ||
nsIdleServiceAndroid.cpp | ||
nsIdleServiceAndroid.h | ||
nsIMEPicker.cpp | ||
nsIMEPicker.h | ||
nsLookAndFeel.cpp | ||
nsLookAndFeel.h | ||
nsPrintOptionsAndroid.cpp | ||
nsPrintOptionsAndroid.h | ||
nsScreenManagerAndroid.cpp | ||
nsScreenManagerAndroid.h | ||
nsWidgetFactory.cpp | ||
nsWindow.cpp | ||
nsWindow.h |