Live data from Hacker News

Safari Ruined My Tuesday

fly.io

71–80 of 140 posts

Re: Safari Ruined My Tuesday

#71

Earlier quoted context omitted.

> 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. Indeed. While Safari does have its problems, it is a long, long way from being as bad as IE used to be. I recall one project where making it work on IE required that about 30% of the code be rewritten.

And that’s not even the worst part. The worst was all of the corporate sites that were built to run exclusively on IE6 and straight up couldn’t be used in alternative browsers. I’m talking scripts written in VBScript rather than JavaScript. ActiveX plug-ins rather than something cross-platform.

The browser landscape was very different when IE6 was new. In many cases the only way to write a performant, complex web app was to use ActiveX (or Flash). The problem is those apps were never updated as web technologies rapidly moved forward.

Re: Safari Ruined My Tuesday

#72
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.

Re: Safari Ruined My Tuesday

#73
post #6

I'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…

[deleted]

Re: Safari Ruined My Tuesday

#74
post #26

Earlier quoted context omitted.

Apple's the one ignoring them by shipping them a broken browser.

This is the kind of thing that only web devs care about. If someone can't use your web app on their phone, they're going to never try your app again, not demand changes to the browser.

It's generally the first thing we check for when trialling new software. Does it work in Chrome/FF/Safari and on iOS/Android. If not then we won't continue the trial.

Re: Safari Ruined My Tuesday

#75
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: https://twitter.com/SaraSoueidan/status/1457307545815732233

> 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!!

> 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?!

Re: Safari Ruined My Tuesday

#76

I had the weird experience of someone reporting that a SSL issue was occurring in Safari but not with Chrome. 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. https://my_name.domain.com -> works in Chrome, not in Safari This is interesting to me as Safari is _correct_ in their implementation (that the underscore char…

> 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

It's IE/Netscape all over again; a big driver of bugs back in the day was the one of them (usually but not always IE) was overly tolerant of some sort of bad behaviour).

Re: Safari Ruined My Tuesday

#77

Earlier quoted context omitted.

Well, you can't, but it'd be the same story as if you only had a Mac in 2006 and wanted to test IE6. Consumers have a choice for the devices they use, so it might make business sense to test changes with hardware your customers use at the same frequency or more often than you do on your own preferred hardware.

As dumb as it was, IE was providing free VMs preloaded with IE versions for developers. Apple is horribly developer hostile. My company refuses to test and run around with Safari bugs, the advice is to install a better browser.

> As dumb as it was, IE was providing free VMs preloaded with IE versions for developers.

Not in 2006 no. MS started providing free VMs for browser testing circa 2013, after the release of IE10.

Re: Safari Ruined My Tuesday

#78
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.

Re: Safari Ruined My Tuesday

#79

Earlier quoted context omitted.

> 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. Indeed. While Safari does have its problems, it is a long, long way from being as bad as IE used to be. I recall one project where making it work on IE required that about 30% of the code be rewritten.

And that’s not even the worst part. The worst was all of the corporate sites that were built to run exclusively on IE6 and straight up couldn’t be used in alternative browsers. I’m talking scripts written in VBScript rather than JavaScript. ActiveX plug-ins rather than something cross-platform.

When I worked at the radar company we would have to go to a Unix machine on a different network and do our time cards. It was Firefox.

Then the time card website upgrade, which only worked in ie.

So now log onto Unix, use a VPN (Citrix) to log onto a windows NT machine, then use IE. It had to be done daily and wasn’t fun.

Re: Safari Ruined My Tuesday

#80
post #71

Earlier quoted context omitted.

And that’s not even the worst part. The worst was all of the corporate sites that were built to run exclusively on IE6 and straight up couldn’t be used in alternative browsers. I’m talking scripts written in VBScript rather than JavaScript. ActiveX plug-ins rather than something cross-platform.

The browser landscape was very different when IE6 was new. In many cases the only way to write a performant, complex web app was to use ActiveX (or Flash). The problem is those apps were never updated as web technologies rapidly moved forward.

I bet a lot of corporations would have loved for Microsoft to launch a sandboxed version of IE6 that had enough "knobs" for the sysadmins to only allow it to work on an intranet or going to specific sites. Saves a lot of investment, but becomes the new COBOL.
Post reply on HN