I’ve tried that with both Brave and Chrome and it just shares the tab, not the session, not sure if I’m missing something. Even if it worked, Chrome requires Sync to be enabled to move tabs from mobile to other devices, so one must be logged in with a google account and Brave’s UX for it isn’t really intuitive, not sure about Safari. So the choice, if the workaround shared the session, would be between relying on a centralized entity to do a basic web3 task, dealing with unnecessary complexity or switching browser altogether.
After all there must be a reason if banks, CEXes, NFID and many other services dealing with sensitive data have been adding QR code auth as an option instead of relying on browser solutions: they are more user friendly and most importantly work, both of which aren’t the case for the browser counterpart right now.
Your suggestion also seem to contradict what another dev on the identity team said months ago:
So it comes as a surprise to hear it doesn’t seem be on the roadmap anymore.