3 ms·

I’ve been shocked at the number of show-stopper bugs shipping in Safari recently so I’m doing what I can to draw attention to it. I hope it helps the Safari tea

by feross 5y ago

I’ve been shocked at the number of show-stopper bugs shipping in Safari recently so I’m doing what I can to draw attention to it. I hope it helps the Safari team get the resources they need from the big wigs at Apple. Also: Didn’t mean to imply I wrote that report. We were about to open a duplicate issue before noticing yours. Thanks!

tb100 5y ago
No worries, I imagine many teams have been through the same process over the past couple of weeks! We've definitely had the same experience of Safari introducing way more issues with new releases than Chrome, and the fact it's part of the iOS image seems to make quick patching just never really an option. I just wish they'd engage a bit more directly on the bug tracker - find it hard to believe that twitter is a more effective means to get attention on bugs.
chubot 5y ago
I've always been a Linux user, but recently I got a new Macbook Air and wanted to try a non-Chrome browser. Then I loaded up my 2005-vintage personal wiki which has been working fine for 15 years on all the browsers I use (Chrome and Firefox). And it has a tabindex bug in Safari! https://stackoverflow.com/questions/1848390/safari-ignoring-tabindex https://stackoverflow.com/questions/1848390/safari-ignoring-... I'm not sure but isn't this a violation of the spec? Or is there some newer thing for tabindex? Either way I switched back to Firefox and Chrome. I kinda like the idea of a browser that doesn't implement all the Chrome crap. But I also feel like it should interpret 15 year old pages correctly!
- machello13 5y ago
  I'm confused, you said there's a bug but as far as I can tell it's just that Safari disables using "tab" for more than form elements by default.
  - chubot 5y ago
    It might not be a bug in the sense that it's a spec violation, but it's behavior that every other browser I've used for 15 years has. If this were a commercial product (my wiki), there would be a bug in the tracker for it :) In the link people have given JS workarounds.

by feross 5y ago

tb100 5y ago

No worries, I imagine many teams have been through the same process over the past couple of weeks! We've definitely had the same experience of Safari introducing way more issues with new releases than Chrome, and the fact it's part of the iOS image seems to make quick patching just never really an option. I just wish they'd engage a bit more directly on the bug tracker - find it hard to believe that twitter is a more effective means to get attention on bugs.

chubot 5y ago

I've always been a Linux user, but recently I got a new Macbook Air and wanted to try a non-Chrome browser. Then I loaded up my 2005-vintage personal wiki which has been working fine for 15 years on all the browsers I use (Chrome and Firefox). And it has a tabindex bug in Safari! https://stackoverflow.com/questions/1848390/safari-ignoring-tabindex https://stackoverflow.com/questions/1848390/safari-ignoring-... I'm not sure but isn't this a violation of the spec? Or is there some newer thing for tabindex? Either way I switched back to Firefox and Chrome. I kinda like the idea of a browser that doesn't implement all the Chrome crap. But I also feel like it should interpret 15 year old pages correctly!

machello13 5y ago
I'm confused, you said there's a bug but as far as I can tell it's just that Safari disables using "tab" for more than form elements by default.
- chubot 5y ago
  It might not be a bug in the sense that it's a spec violation, but it's behavior that every other browser I've used for 15 years has. If this were a commercial product (my wiki), there would be a bug in the tracker for it :) In the link people have given JS workarounds.