Workaround for Chrome 113

[metsma]

WE2-783

Signed-off-by: Raul Metsma raul@metsma.ee

[martinpaljak]

Having such random references to opaque internal issue trackers sort of defeats the spirit of open source (even if actual source is available). What is the reason? What is the dicussion? When was it reported?

[martinpaljak]

I make a wild guess - it caught everyone by surprise yesterday. AFAIK there are folks on RIA payroll who could (SHOULD!) be running development/canary releases of the major browsers/operating systems (month+ reaction time) all the time to detect such things before they happen (and this is not the first time when issues like this seem to come as a "sudden surprise" when in fact it is just lack of proactivity).

(This is not a remark about ticket paricipants @metsma and @mrts who are fine gentlement doing their best. This is a complaint from a taxpayer to @web-eid (RIA) as an organization)

[kristelmerilain]

All supported browsers Chrome, Edge and Firefox are tested on macOS, Ubuntu and Windows before and after the release of the new browser version.
The Chrome 113 version was also tested before it was made public. Unfortunately this issue did not come out during Chrome 113 beta testing and we discovered it yesterday when testing Chrome 113 released version.
We are currently actively working to make the new Web eID version public to users as soon as possible and we will certainly discuss internally how to avoid this kind of issues in the future.
We apologize for any inconvenience caused!

[mrts]

Kristel already explained the procedural side, let me also briefly explain the technical side (to answer "What is the reason?"). Chrome now directly launches the Native Host executable, rather than executing it via cmd.exe on Windows. As a consequence, the application window starts hidden (which is by design, it wasn't properly hidden before only because of the intermediate cmd.exe). This is explained in more detail in this mailing list post by Chrome developer Eric Lawrence. We actually had code for forcing the window to the foreground, but this is no longer sufficient to override the "start hidden" flag, hence the show-hide-show hack in this pull request.