4 ms·

The fun part in web dev is to make sure everything works on the 0.5% non mainstream browser/platforms. Only supporting 99.5% is boring.

by z3t4 5y ago

franga2000 5y ago
It is to a point, but then it just becomes painful. If you want to keep a good user experience for modern browsers while supporting ancient ones, you'll probably be writing at least all your layouts twice.
- michaelt 5y ago
  You guys are getting a good user experience from your banks?
  - franga2000 5y ago
    I am since reverse engineering their mobile app protocol and developing a Python library for it :)
rocqua 5y ago
A popup "your OS browser combination is not supported, some things may not work" is a much less nuclear option.
- rzzzt 5y ago
  If you know which parts will not work in advance. What if the "Send $$$" button does not appear due to a CSS misfire?
  - zeorin 5y ago
    eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature. [0] https://github.com/amilajack/eslint-plugin-compat https://github.com/amilajack/eslint-plugin-compat [1] https://github.com/ismay/stylelint-no-unsupported-browser-features https://github.com/ismay/stylelint-no-unsupported-browser-fe...
- joppy 5y ago
  Things fail in the weirdest ways in unsupported environments though, it’s not like the “make transfer” button doesn’t work, it’s more like it might not even show up in the first place. Having 99% of your website work and the last 1% not work is a dealbreaker in many cases, and these “the site may not work for you based on your OS” banners lead the user into thinking it does work 100% if it works in 99% of the cases. Not saying this is the way it should be, just saying that “doing your best” to allow unsupported platforms often leads to a terrible and confusing user experience.
  - alvarlagerlof 5y ago
    Unlikely. This is a browser. If it's going to fail, it won't be some js somewhere. It's going to be the whole thing.
    - Kaze404 5y ago
      That's not true. All it takes is using an unsupported CSS rule for something to simply disappear from the page under certain circumstances. As a recent example, I found out some of our users couldn't find a specific button in an application. It still existed, but we used the zoom property to make it stand out more, which for some reason is only supported in Chrome.
- indymike 5y ago
  How about assuming it works until users report it does not?
- op00to 5y ago
  I would not want a money transfer to “not work” and end up moving $500,000 rather than $500.

The fun part in web dev is to make sure everything works on the 0.5% non mainstream browser/platforms. Only supporting 99.5% is boring.

by z3t4 5y ago

The fun part in web dev is to make sure everything works on the 0.5% non mainstream browser/platforms. Only supporting 99.5% is boring.

franga2000 5y ago

It is to a point, but then it just becomes painful. If you want to keep a good user experience for modern browsers while supporting ancient ones, you'll probably be writing at least all your layouts twice.

michaelt 5y ago
You guys are getting a good user experience from your banks?
- franga2000 5y ago
  I am since reverse engineering their mobile app protocol and developing a Python library for it :)

rocqua 5y ago

A popup "your OS browser combination is not supported, some things may not work" is a much less nuclear option.

rzzzt 5y ago
If you know which parts will not work in advance. What if the "Send $$$" button does not appear due to a CSS misfire?
- zeorin 5y ago
  eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature. [0] https://github.com/amilajack/eslint-plugin-compat https://github.com/amilajack/eslint-plugin-compat [1] https://github.com/ismay/stylelint-no-unsupported-browser-features https://github.com/ismay/stylelint-no-unsupported-browser-fe...
joppy 5y ago
Things fail in the weirdest ways in unsupported environments though, it’s not like the “make transfer” button doesn’t work, it’s more like it might not even show up in the first place. Having 99% of your website work and the last 1% not work is a dealbreaker in many cases, and these “the site may not work for you based on your OS” banners lead the user into thinking it does work 100% if it works in 99% of the cases. Not saying this is the way it should be, just saying that “doing your best” to allow unsupported platforms often leads to a terrible and confusing user experience.
- alvarlagerlof 5y ago
  Unlikely. This is a browser. If it's going to fail, it won't be some js somewhere. It's going to be the whole thing.
  - Kaze404 5y ago
    That's not true. All it takes is using an unsupported CSS rule for something to simply disappear from the page under certain circumstances. As a recent example, I found out some of our users couldn't find a specific button in an application. It still existed, but we used the zoom property to make it stand out more, which for some reason is only supported in Chrome.
indymike 5y ago
How about assuming it works until users report it does not?
op00to 5y ago
I would not want a money transfer to “not work” and end up moving $500,000 rather than $500.