Earlier quoted context omitted.
I think Safari, flaws and all, is pretty much the only browser that has any weight against Chrome. Tell your manager that you want the web site to support Firefox or Brave or something else, and they'll tell you it's a waste of time. Tell them that the web site won't work on their MacBook, and it's a four-alarm fire. In a lot of ways, I wish Safari would deviate even more from Google's "standards" just so that maybe…
Microsoft Edge is gaining some serious ground and is closing in on Safari [0]. Their aggressive conversion tactics seem to be paying off. The problem with Safari is that they either simply haven't, and, in some cases, even flat out refuse to implement certain standards that they themselves have had a hand in establishing. And then most of what is available comes half-arsed, undocumented, and is not supported/iterated…
Safari Ruined My Tuesday
31–40 of 140 posts
Re: Safari Ruined My Tuesday
#32My general recommendation is to make Safari your main browser for development work. Check your work in Firefox later. By that point it should be good. If any weirdness shows up in Chrome, you'll just end up comparing it to IE6.
How do you that if you don't own a mac?
Re: Safari Ruined My Tuesday
#33I encounter random CSS bugs all the time in Chrome, it's just trendy to say Safari is behind the times. Google wants everything to be done in the browser, their browser, so they can track everything without cookies to sell ads
I want everything in the browser too - except the ads. And FF isn't keeping up :( WebUSB for example.
About the only worse thing would be a WebPCIe.
Re: Safari Ruined My Tuesday
#34Re: Safari Ruined My Tuesday
#35Earlier quoted context omitted.
Mobile safari… since it’s the only engine on iOS … that ends up being a good chunk of users depending on your user base probably many try to use your website on an iPhone … if blink engine was allowed by apple on iOS - safari would die tomorrow
And if enough developers simply ignored Safari then maybe it would force Apple to either simply adhere to web standards or allow competing browser engines... Catering to them signals that their shitty behaviour is condoned.
Who will the developers' manager blame: Apple or the developers?
Re: Safari Ruined My Tuesday
#36i sympathize with the author. safari and browsers aside, there is something bigger going on. there is a massive disconnect between applications users and makers nowadays. i have started to think that they a) don't care b) have misaligned priorities c) have weird notions of "acceptable" errors. i have a long list of applications that break every time there is an update. even UX updates introduce bugs nowadays. i have…
Updates to Wordpress / WooCommerce and accompanying plugins can make one go suicidal.
Re: Safari Ruined My Tuesday
#37i sympathize with the author. safari and browsers aside, there is something bigger going on. there is a massive disconnect between applications users and makers nowadays. i have started to think that they a) don't care b) have misaligned priorities c) have weird notions of "acceptable" errors. i have a long list of applications that break every time there is an update. even UX updates introduce bugs nowadays. i have…
Why should any developer care about supporting Safari? Chrome and Firefox support most (all?) of the current web standards. Every site I use works on both. I don't hear any concerns about Brave, Edge or Opera either. How is it that Safari is the only broken browser these days? As for 'acceptable' errors, I find software to be pretty reliable these days. I remember way more things being messed up back in the day...
Those updates broke a lot of websites - you might have noticed SSO failing, iframes failing, or websites confusing unmodified Safari users for adblock users.
Firefox adopted the changes a bit later. By the time they made the switch, I think most had resolved their sites because of Safari. Last I read, Chrome is slated to implement similar for 2022.
Not intended to be a defense of Safari, especially for OP's bug. But at least some breaking changes were deliberate and in the name of privacy enhancements.
Re: Safari Ruined My Tuesday
#38I encounter random CSS bugs all the time in Chrome, it's just trendy to say Safari is behind the times. Google wants everything to be done in the browser, their browser, so they can track everything without cookies to sell ads
I would like to see a strong competitor to Chrome someday though... - Firefox still has weird issues occasionally (most recently scroll position randomly jumping sometimes). I still keep it around though because its sane when it comes to standards and will remain sane even if things like HW acceleration are not available. - Safari is out of the question as it is not even cross-platform (might as well be IE6) - Chromium and derivatives aren't distinct enough from Chrome and a lot of the new ones have weird cryptocurrency integrations that just don't feel right. - Is Opera still alive?
Re: Safari Ruined My Tuesday
#39My general recommendation is to make Safari your main browser for development work. Check your work in Firefox later. By that point it should be good. If any weirdness shows up in Chrome, you'll just end up comparing it to IE6.
>My general recommendation is to make Safari your main browser for development work. How do you that if you don't own a mac?
Re: Safari Ruined My Tuesday
#40Earlier quoted context omitted.
I want everything in the browser too - except the ads. And FF isn't keeping up :( WebUSB for example.
WebUSB is insane security-wise. About the only worse thing would be a WebPCIe.