> It's like living with IE6 again<p>There is a CSS bug.<p>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.<p>I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop. But it's still way better than dealing with IE6.
Heh, reading the title I thought this was going to be someone losing all their tabs because "clear history" on mobile Safari apparently does that: <a href="https://twitter.com/SaraSoueidan/status/1457307545815732233" rel="nofollow">https://twitter.com/SaraSoueidan/status/1457307545815732233</a><p>> Oh dear God.. Clearing history on Safari iOS closes all currently-opened tabs?! Why is there nothing that warns you of that?! Why does clearing history on mobile work differently from the way it does on mac? I had 60+ important tabs open and now they're gone!!<p>> I had so many notes, bookmarks, and links I needed to use in my course + so many pages unrelated to work, all open for later reference. And no I don't have a backup to restore from. What the heck, Apple?!
Part of the problem is the very slow release cadence of Safari. Features are tied to annual OS releases, bug fixes seem to often not meet the bar for incremental updates, which have no discernable schedule.
I encounter random CSS bugs all the time in Chrome, it's just trendy to say Safari is behind the times.<p>Google wants everything to be done in the browser, their browser, so they can track everything without cookies to sell ads
Chrome fucked up one of my days, because it suddenly changed the way updating a video element's source worked. On Android 11, and not even all platforms, by the looks of the log files. So, you hack around it, deploy, shrug, and add a notch to your eternally flaming hatred for everything the internet has become.
Yikes, that's an awful bug. I make heavy use of pointer-events none. And I've _already_ had to have a special case for Safari, because it didn't seem to support setting `pointer-events: all` on SVG tspan elements. Now I have to double check to see if/what is broken in Safari 15 :(
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.<p>If any weirdness shows up in Chrome, you'll just end up comparing it to IE6.
i sympathize with the author.<p>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.<p>i have a long list of applications that break every time there is an update. even UX updates introduce bugs nowadays. i have started to dread updates and upgrades.<p>we have lost all notion of stability.
In my brief experience in front-end, I've encountered weird Safari bugs on every single project.<p>In one case the code failed because the form object there doesn't implement the method to validate and submit. In another, it wasn't sending a form field if it was styled with "display: none;" (had to change to "left: -9999px;"). In another, playing a non-muted video would error out some of the time, if clicking an element wasn't recognized as a user event. In yet another, the mobile version refused to center text inside <button> no matter what. And so on.
> CSS includes a handy pointer-events attribute that makes buttons and links flip to non-interactive<p>Except that it doesn't, you can still focus those with keyboard and click them. You should always disable buttons with `disabled` property instead of that hack.
It's quite interesting to read the history of how Blink came to be[0]. Seems like it started on what amounts to a misunderstanding. And now, because of it, Safari's fallen hopelessly behind in web standards support, security, and even resource use (see RAM use in Safari vs Chrome with many tabs open, Safari uses 1.5x-2x more RAM). Apple's big weakness is that it has laser focus on a few cash cows, and lets everything else linger; the quality of Chrome developer relations, carefulness to not break things in updates (see Safari & IndexDB), huge resources invested in Chrome security, and focus on features and power users (tab list in the menu bar! tab search that doesn't take seconds to load on x86! better UI! tabs on top! multiple profile support! ability to open local HTML files without going into the Develop menu!). Why can't Apple just care to make a good browser?<p>Does anyone have any insights into how the Safari team functions at Apple, and why they're not catching up?<p>[0]: <a href="https://news.ycombinator.com/item?id=5489641" rel="nofollow">https://news.ycombinator.com/item?id=5489641</a>
I had the weird experience of someone reporting that a SSL issue was occurring in Safari but not with Chrome.<p>After a bunch of investigation and rabbit holes it turned out that it was an app issue where the "_" character wasn't being filtered from sub-domains.<p><a href="https://my_name.domain.com" rel="nofollow">https://my_name.domain.com</a> -> works in Chrome, not in Safari<p>This is interesting to me as Safari is _correct_ in their implementation (that the underscore character isn't valid in domains), but again an instance of FF+Chrome working where Safari doesn't.
When you're doing cross-platform development like this for the web, you're going to have a "least common denominator" that you have to design for. Safari is that least common denominator right now only because Microsoft switched to using Chromium.
But if Apple switched Safari to use Chromium, then Firefox would be the least common denominator and supporting Firefox would suddenly seem like a burden.<p>It's fine to criticize Safari and encourage Apple to do better in the space, since Apple isn't super incentivized to improve Safari. But this narrative that always targets the browser with the smallest feature-set at any given time will only stop when all browsers are Chromium based. (At which point they'll start complaining about other browsers using a Chromium version that's slightly behind Chrome.)
I’m not at my desk to try it right now, but I wonder if this can be worked around by forcing a repaint. Animating a custom property, for instance, can fix “stuck” styles for eg scroll shadows (see <a href="https://www.bram.us/2019/10/24/pure-css-scroll-shadows-vertical-horizontal/#note-mobilesafari" rel="nofollow">https://www.bram.us/2019/10/24/pure-css-scroll-shadows-verti...</a>).
Here’s my latest browser issue that drove me crazy: In Safari the TextMetrics.actualBoundingBoxRight returned from CanvasRenderingContext2D.measureText() includes dangling spaces, and Chrome does not. So you’ll get different text measurements if the text has a space on the end, which broke my app’s logic of rendering multiline rich text in Chrome. Ugh.
I'm trying to figure out which browser is the biggest cancer for the WWW.<p>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.<p>And on the other, you have Chrome whom has a parent company that claims it wants to improve privacy (FLoC), but to me it is more of a "pulling the ladder up on everyone else" because they have so many other methods to track you (DNS, GA, Android, etc.) that limiting everyone would be disingenuous. Pushing AMP is another example of bullying behavior.
> This is a post about a bug in Safari, but if you just want to ship a Phoenix app, the easiest way to learn more is to try it out; you can be up and running in just a couple minutes<p>I'm sort of sick of this phenomena/trend of marketing/promotional material being masked as technically helpful content.<p>This is exactly like the appalling methods of native advertising (aka sponsored content), but now used for self-promotion.