5 ms·

Great news! Not because I use WebRTC at all, but because I use Safari. Why would you do that?? It integrates nicely with the OS. Spell checking, keychain, serv

Great news! Not because I use WebRTC at all, but because I use Safari. Why would you do that?? It integrates nicely with the OS. Spell checking, keychain, services, keyboard shortcuts, right-click dictionary lookup, easy link sharing. Little things. I have recently noticed more and more sites are starting to break on Safari. Ever since Chrome forked webkit, it has started to lag behind. Since Safari has a small marketshare and a different engine from the major players, some sites dropped support for it. A prime example is file-upload to Github issues. You'd think that uploading files is as old as the web itself, but when you try to do this in Safari, it says something like "Sorry, Safari does not support file attachments. Please use a modern browser like Firefox or Chrome."

JohnTHaller 11y ago
If the only way for me to test your small market share desktop browser is to buy hardware from you because you artificially lock your os to your hardware, I'm not going to test on your browser. On Mac OS, the solution for users is to run a different browser like Chrome or Firefox, as nearly all of my Mac friends do. If this issue starts to affect media consumption sites on iOS's Safari, that's another story since iOS users aren't allowed to use an alternate browser (they're all running Safari underneath).
- wbl 11y ago
  It's file upload: I'm 99.9% sure that the most braindead 90's style way of doing it will work on all browsers today, and continue to work in the future. Why do you need to break it?
  - untog 11y ago
    Newer methods allow you to do a lot more - report progress of the upload, even read the file locally before upload (so you can resize images, for example). They're all great features to add, and I guess that GitHub decided that it was worth adding them and not keeping an older experience for Safari users. IMO, they're both at fault here. GitHub should be able to provide a fallback, but also Safari should be keeping up to date.
kevingadd 11y ago
Some of it is from falling behind, but a big part of the burden on web devs is that Safari updates just frequently break existing JS and webpages. I don't know if it's because Apple has insufficient testing before releases or because they expect web devs to roll over and do what they want, but either way, it sucks. Back when Safari had windows builds, I at least made an effort to test locally and fix the bugs they kept introducing. But many of the bugs only reproduced on OS X, and now there's no Windows port, so there's no way I'm going to drop a bunch of money to buy a Mac just so I can do their work for them. Safari bugs have broken my JS more often than every other browser combined. IE included.
jackweirdy 11y ago
Also, battery life. I switched from Chrome to Safari about a month ago, and have been getting at least 10-20% longer out of my battery depending on whether I'm just browsing/developing.

JohnTHaller 11y ago

If the only way for me to test your small market share desktop browser is to buy hardware from you because you artificially lock your os to your hardware, I'm not going to test on your browser. On Mac OS, the solution for users is to run a different browser like Chrome or Firefox, as nearly all of my Mac friends do. If this issue starts to affect media consumption sites on iOS's Safari, that's another story since iOS users aren't allowed to use an alternate browser (they're all running Safari underneath).

wbl 11y ago
It's file upload: I'm 99.9% sure that the most braindead 90's style way of doing it will work on all browsers today, and continue to work in the future. Why do you need to break it?
- untog 11y ago
  Newer methods allow you to do a lot more - report progress of the upload, even read the file locally before upload (so you can resize images, for example). They're all great features to add, and I guess that GitHub decided that it was worth adding them and not keeping an older experience for Safari users. IMO, they're both at fault here. GitHub should be able to provide a fallback, but also Safari should be keeping up to date.

kevingadd 11y ago

Some of it is from falling behind, but a big part of the burden on web devs is that Safari updates just frequently break existing JS and webpages. I don't know if it's because Apple has insufficient testing before releases or because they expect web devs to roll over and do what they want, but either way, it sucks. Back when Safari had windows builds, I at least made an effort to test locally and fix the bugs they kept introducing. But many of the bugs only reproduced on OS X, and now there's no Windows port, so there's no way I'm going to drop a bunch of money to buy a Mac just so I can do their work for them. Safari bugs have broken my JS more often than every other browser combined. IE included.

jackweirdy 11y ago

Also, battery life. I switched from Chrome to Safari about a month ago, and have been getting at least 10-20% longer out of my battery depending on whether I'm just browsing/developing.