https://bugs.winehq.org/show_bug.cgi?id=42324
--- Comment #5 from Henri Verbeet hverbeet@gmail.com --- (In reply to Ken Thomases from comment #4)
In Apple's terminology, the context changes which "virtual screen" is active for the context. In theory, a Mac app should note when the context's virtual screen changes, re-query the GL extensions and limits, and reconfigure its rendering pipeline accordingly. However, Windows OpenGL apps are not prepared to do that. In theory, D3D apps should cope if WineD3D would tell them that the device was "lost", but the Mac driver doesn't have a good way to tell WineD3D that and, to my knowledge, WineD3D doesn't currently support marking devices as lost.
Not in wined3d itself, but wined3d clients like ddraw or d3d9 do. See e.g. device_parent_mode_changed() and device_parent_activate() in ddraw.