On Sat, 20 Feb 2021 17:36:52 +0100 Eric Jensen wrote:
EJ> today i updated the wxWidgets version in one of my projects to the
EJ> latest trunk and it silently broke, because the default
EJ> wxWebViewBackend under Windows was switched from IE to Edge.
Hi Edge and sorry to hear about this!
I was unsure about this change but I've finally decided that this should
be fine because most users wouldn't build with Edge support anyhow, as it
requires doing something special, and if they did go to the trouble of
setting up the build to use Edge, then they probably want to use it.
EJ> BTW: I actively do use the Edge backend in another part of the same
But I clearly failed to take this case into account...
EJ> The problem was related to registering a custom scheme handler which
EJ> is currently not supported by the Edge backend.
EJ> So i'm questioning whether changing the default backend is a good
EJ> idea as long as the Edge backend doesn't support the same features?
I still think that this shouldn't affect most people, for the reasons
explained above, but clearly the changes of 788bef2cf2 (Select Edge as the
default backend on MSW, 2021-02-04) were not as safe as I thought. Not sure
what to do here, to be honest.
TT-Solutions: wxWidgets consultancy and technical support