4 ms·
This answer and your other answer are basically non-answers. You haven't listed any specific reasons why using them is difficult. Unless you have a specific sce
by dpkonofa 7y ago
This answer and your other answer are basically non-answers. You haven't listed any specific reasons why using them is difficult. Unless you have a specific scenario that applies to enough people, EPRs are the best way to handle this currently in a way that gives the users control over what happens. You shouldn't need to work around these controls.
- josteink 7y agoWell try it yourself then, in a production project, and see what bounce-rates you get with your users. There’s a reason literally no big companies are using this tech anymore, when they used to do so 10 years ago. Go on. I’ll be here to say “I told you so”.
- prophesi 7y agoI'm looking at Slack, Steam, and any Email client ever (granted, mailto opening an external app has been standard practice for ages). I'm not sure if I know of any big companies that surreptitiously run a local web-server to save users a click whom haven't received flak for it.
- josteink 7y agoYou misunderstand. I'm not advocating running a local web-server. That's bad. What I'm saying is that none of the big actors are using custom protocols anymore even though lots of them used to, because browser security policies have rendered them useless for regular end-user interaction. They have all found other approaches instead. (Some bad, like here. Others better, like the solutions I chose instead).