6 ms·

For the majority of links there is no particular reason but for some specific cases where the link brings you to a App that the developer has build with that b

by cowl 4y ago

For the majority of links there is no particular reason but for some specific cases where the link brings you to a App that the developer has build with that browser in mind it is useful. I want a way to force the opening of that app in the browser for which I have tested and don't want to receive support calls that the app is not working because you opened it in your obscure browser of choice.

em-bee 4y ago
such apps should not exist. it's a throwback to the old internet explorer days. you will receive support calls from people who don't run windows and thus don't have edge
- LtWorf 4y ago
  Well it's how the mailto:blabla@blabla works.
  - em-bee 4y ago
    yes, but the target for each of those is user-configurable. any request to another browser would go back to my preferred one. regardless, web-apps that depend on a specific browser should not exist.
    - hardware2win 4y ago
      If browsers had equal features support then yea
      - em-bee 4y ago
        that's what the standards are for. any feature that is not implemented in all major browsers should be considered experimental. it might go away. it's fine to use such features for experiments, but they should not be put into production and relied upon. any differences in the implementation of the standard should be considered a bug. warning users about bugs is fine, but automatically redirecting me to some other browser that you deem working is not.
        hardware2win 4y ago
        Uh what? If one browser laggs behind then the rest shouldnt deploy? This is crazy
        em-bee 4y ago
        depends how much your users matter to you. if a browser[1] lags behind on a feature, you should avoid using that feature on a production website, or provide a gracefull fallback. but by no means should you redirect the users to a browser that supports that feature. [1] i am only counting major modern browsers here: chrome, edge, firefox, safari. you are welcome to support more, but these at a minimum.
        hardware2win 4y ago
        If I have 20% FF users and 70% chromium users, then I shouldnt deploy a feature which will serve those 70% and wait who knows how long till FF catches up? Wtf.
        em-bee 4y ago
        you are willing to anger 20% of your userbase? you can do whatever you want, just don't expect everyone to go along. but if i run a business and my revenue depends on my browser users, i'd be very hesitant at loosing even 5% of them, let alone 20%.
        hardware2win 4y ago
        Why would all of them leave your service just because one thing is not available on ff? Popular as hell services are constantly annoying users e.g reddit fb Or arent or werent available on web at all - iirc instagram If you have leverage then they aint gonna leave as hard as you make it sound
        em-bee 4y ago
  - yjftsjthsd-h 4y ago
    What? No, it's the exact opposite! If I set my system to open mailto links in Thunderbird, the link won't randomly override and open in Outlook. That's the whole point: The link specifies what should get opened, and then the application of the user's choice handles it.

by cowl 4y ago

em-bee 4y ago

such apps should not exist. it's a throwback to the old internet explorer days. you will receive support calls from people who don't run windows and thus don't have edge

LtWorf 4y ago
Well it's how the mailto:blabla@blabla works.
- em-bee 4y ago
  yes, but the target for each of those is user-configurable. any request to another browser would go back to my preferred one. regardless, web-apps that depend on a specific browser should not exist.
  - hardware2win 4y ago
    If browsers had equal features support then yea
    - em-bee 4y ago
      that's what the standards are for. any feature that is not implemented in all major browsers should be considered experimental. it might go away. it's fine to use such features for experiments, but they should not be put into production and relied upon. any differences in the implementation of the standard should be considered a bug. warning users about bugs is fine, but automatically redirecting me to some other browser that you deem working is not.
      - hardware2win 4y ago
        Uh what? If one browser laggs behind then the rest shouldnt deploy? This is crazy
        em-bee 4y ago
        depends how much your users matter to you. if a browser[1] lags behind on a feature, you should avoid using that feature on a production website, or provide a gracefull fallback. but by no means should you redirect the users to a browser that supports that feature. [1] i am only counting major modern browsers here: chrome, edge, firefox, safari. you are welcome to support more, but these at a minimum.
        hardware2win 4y ago
        If I have 20% FF users and 70% chromium users, then I shouldnt deploy a feature which will serve those 70% and wait who knows how long till FF catches up? Wtf.
        em-bee 4y ago
        you are willing to anger 20% of your userbase? you can do whatever you want, just don't expect everyone to go along. but if i run a business and my revenue depends on my browser users, i'd be very hesitant at loosing even 5% of them, let alone 20%.
        hardware2win 4y ago
        Why would all of them leave your service just because one thing is not available on ff? Popular as hell services are constantly annoying users e.g reddit fb Or arent or werent available on web at all - iirc instagram If you have leverage then they aint gonna leave as hard as you make it sound
        em-bee 4y ago
- yjftsjthsd-h 4y ago
  What? No, it's the exact opposite! If I set my system to open mailto links in Thunderbird, the link won't randomly override and open in Outlook. That's the whole point: The link specifies what should get opened, and then the application of the user's choice handles it.