Saard

Yeah. No. Not how it works for a professional development shop--as Affinity most certainly is.
I worked for two decades as a software architect for major enterprises, as an expert on the Microsoft tech stack. When you produce "shrink-wrapped" software, you do what your customers need first, and never EVER break their workflows because of the fashions and whims of the technology stack provider. UNLESS: that stack provider introduces breaking changes and stops supporting the legacy tech. And when/if that happens, it's always a very big deal to let your customers know exactly how and when it's coming, what the conflicts and issues will be, and to provide them documented workarounds IN ADVANCE.

None of those things happened here.

Thank you Hans De Smaele. 
The workaround works with Adobe Bridge for me.
This workaround should not be necessary.  Serif should release software that works with existing programs, not insist that others developers adapt to them.  This seems especially true as I suspect that many Serif users call Affinity from other programs such as Adobe, DxO, RawTherapee, etc.  Seems obvious to me that this would be advantageous to Serif.  Why would other vendors want to make it easy to access Serif software.  If Serif wants to isolate its software, then I think it needs at a minimum to include a Browser similar to Adobe Bridge.