I can reliably reproduce with the steps in the description. I guess google generates intent:// URLs because it thinks it’s talking to an android device, which is very unfortunate. Not sure what’s the best way to address that. Maybe a UA override for google.com, or a custom protocol handler to intercept intent:// URLs (or even intercepting them at the navigationRequested level).
I can reliably reproduce with the steps in the description. I guess google generates intent:// URLs because it thinks it’s talking to an android device, which is very unfortunate. Not sure what’s the best way to address that. Maybe a UA override for google.com, or a custom protocol handler to intercept intent:// URLs (or even intercepting them at the navigationRequested level).