My 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.
Safari Ruined My Tuesday
21–30 of 140 posts
Re: Safari Ruined My Tuesday
#22I 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
Oh yes it's trendy to criticize Apple but it's not trendy to criticize Google.
Honestly I don't know the reality some HN commenters live in.
Re: Safari Ruined My Tuesday
#23I'm trying to figure out which browser is the biggest cancer for the WWW. On the one hand, you have Safari whom has a parent company that isn't interested in making it have useful feature parity with the others because it'll then allow escape from their gravy train app store (fully working PWA's, non-compete with rendering engines in iOS). Their lack of keeping up is starting to look a bit like IE6 days. And on the o…
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…
> I think Safari, flaws and all, is pretty much the only browser that has any weight against Chrome.
This is a terrible argument. That an inferior, proprietary, broken browser made by a company trying to cripple the web to protect their lucrative walled garden should be more popular in order to prevent Google from having more market share just for reasons?
Chrome became popular and is popular because it works. It's cross-platform, it implements all the newest standards, it's just a good product.
Re: Safari Ruined My Tuesday
#24I 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.
Re: Safari Ruined My Tuesday
#25Earlier 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.
It is the Mobile Safari engine... "simply ignored Safari" = "simply ignore iPhone users".
Re: Safari Ruined My Tuesday
#26Earlier quoted context omitted.
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.
It is the Mobile Safari engine... "simply ignored Safari" = "simply ignore iPhone users".
Apple's the one ignoring them by shipping them a broken browser.
Re: Safari Ruined My Tuesday
#27My 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.
A recommendation predicated with "Get a Mac first for development work"?
Last I checked Safari unlike Firefox and Chrome is not cross platform.
Small aside: Webkit browsers used to have problems with CSS (especially things involving 3d) when hardware acceleration is unavailable. Spent so many hours back in the day debugging why certain CSS effects did not work. Switched to Firefox and worked like a charm... Only really understood the problem when I eventually switched to a system with HW acceleration support.
Re: Safari Ruined My Tuesday
#28Earlier quoted context omitted.
You might be surprised how often a CSS bug will break an entire site. I've seen it many times in my decades.
Oh, it can definitely happen. In earlier drafts of the current iteration of my website, I used `mix-blend-mode: multiply` liberally (most significantly for the left sidebar), and discovered that in Chromium under Windows anything you used it on would stop rendering after a few thousand pixels (4096 or 8192 or something, my memory’s fuzzy and I don’t have the bug IDs handy), meaning that most of some of my articles we…
Your bug reported 16,384px after accounting for device scale: https://bugs.chromium.org/p/chromium/issues/detail?id=992398
I knew it'd be this number right away, because it's also the maximum screenshot height thanks to being the maximum height of a surface in Chromium (Actually last I checked this technically depends on the GL backend used, but 16kpx seems common)
Re: Safari Ruined My Tuesday
#29> It's like living with IE6 again There is a CSS bug. CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare. I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop.…
Most CSS bugs just make things a bit uglier, rather than completely breaking your entire site.
On one of my sites it had made most important button "add to cart" unclickable
Re: Safari Ruined My Tuesday
#30I 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
Except when it's Chrome, it's probably a feature and not a bug. Remember that Google effectively controls the web "standards".