3 ms·

This gets brought up every time this concept is floated. As if web developers don't already face this challenge today, and as if web browsers aren't developed w

This gets brought up every time this concept is floated. As if web developers don't already face this challenge today, and as if web browsers aren't developed with huge amounts of regression analysis. Not only that, but today browsers are considerably more consistent between them.

giraffe_lady 3y ago
I think to some extent developers today are choosing not to face this challenge directly. A couple years ago I started using safari instead of chrome, and since then I've worked on a couple projects where my dev time has been the only testing on safari done. In this time also out on the normal internet, I've seen a shocking number of sites with critical functionality broken on safari. I'm talking nav, login, payment, on the sites of major brands, wireless carriers, saas companies. So, do we face this challenge today? It exists certainly, but it seems like increasingly we are pretending it doesn't.
- postdb 3y ago
  Often these web apps, just doesn't work on iOS. Seen that happen quite a few times. Also keep in mind Safari on iOS has 7-Day Cap on All Script-Writeable Storages such as: Indexed DB LocalStorage Media keys SessionStorage Service Worker registrations and cache Unless if the Web Applications was added to the Home Screen. https://web.dev/storage-for-the-web/ https://web.dev/storage-for-the-web/
- r3trohack3r 3y ago
  There are a few inconsistencies between modern browsers left, but in my day-to-day so far the fixes have been quick and straightforward. The only exception is 100vw and 100vh. On desktop, building an “app” that fills the screen with a header on top and a footer on bottom, this works great. On some mobile browsers, it places the footer below the browsers navbar because the navbar is not subtracted from the pages height. I’ve had a heck of a time working around this in css, particularly because the fix for mobile seems to break desktop chrome. But compared to even a decade ago, this is nirvana.
  - hell_monkeyo 3y ago
    The new svh (smallest vertical height) units will help you with that problem on mobile, Firefox will require a fallback vh though.
- waboremo 3y ago
  The problem you're describing isn't a lack of interest in facing cross platform/browser challenges, but rather substantial barriers to entry preventing developers from doing their job. To test on Safari, you need a mac. That is a substantial cost. We assume it doesn't exist because we work at places that offer us macbooks (of note, all my teammates test on Safari because we easily can now), but when we are talking about the web at large this is a tremendous cost and is why so many websites are broken on Safari-exclusively (as opposed to both Safari and Firefox). So many websites, even from large companies, are developed by a handful of people, and their habits carry over. This establishes an expectation of not caring about Safari and all of its quirks, it gets relegated to "the user will just use another browser if it's broken". For this problem to cease existing, Safari needs to be released on other operating systems. Until then, Safari will always be disregarded and untested.

giraffe_lady 3y ago

I think to some extent developers today are choosing not to face this challenge directly. A couple years ago I started using safari instead of chrome, and since then I've worked on a couple projects where my dev time has been the only testing on safari done. In this time also out on the normal internet, I've seen a shocking number of sites with critical functionality broken on safari. I'm talking nav, login, payment, on the sites of major brands, wireless carriers, saas companies. So, do we face this challenge today? It exists certainly, but it seems like increasingly we are pretending it doesn't.

postdb 3y ago
Often these web apps, just doesn't work on iOS. Seen that happen quite a few times. Also keep in mind Safari on iOS has 7-Day Cap on All Script-Writeable Storages such as: Indexed DB LocalStorage Media keys SessionStorage Service Worker registrations and cache Unless if the Web Applications was added to the Home Screen. https://web.dev/storage-for-the-web/ https://web.dev/storage-for-the-web/
r3trohack3r 3y ago
There are a few inconsistencies between modern browsers left, but in my day-to-day so far the fixes have been quick and straightforward. The only exception is 100vw and 100vh. On desktop, building an “app” that fills the screen with a header on top and a footer on bottom, this works great. On some mobile browsers, it places the footer below the browsers navbar because the navbar is not subtracted from the pages height. I’ve had a heck of a time working around this in css, particularly because the fix for mobile seems to break desktop chrome. But compared to even a decade ago, this is nirvana.
- hell_monkeyo 3y ago
  The new svh (smallest vertical height) units will help you with that problem on mobile, Firefox will require a fallback vh though.
waboremo 3y ago
The problem you're describing isn't a lack of interest in facing cross platform/browser challenges, but rather substantial barriers to entry preventing developers from doing their job. To test on Safari, you need a mac. That is a substantial cost. We assume it doesn't exist because we work at places that offer us macbooks (of note, all my teammates test on Safari because we easily can now), but when we are talking about the web at large this is a tremendous cost and is why so many websites are broken on Safari-exclusively (as opposed to both Safari and Firefox). So many websites, even from large companies, are developed by a handful of people, and their habits carry over. This establishes an expectation of not caring about Safari and all of its quirks, it gets relegated to "the user will just use another browser if it's broken". For this problem to cease existing, Safari needs to be released on other operating systems. Until then, Safari will always be disregarded and untested.