There are several questions regarding bugs - how many are there, how difficult are they to find, how difficult are they to fix.
It seems that there are many Safari bugs that are difficult to find, and to fix, which makes them worse than other browsers.
In this case I believe the bug is actually difficult to find, this guy found it but I bet a lot of developers just went and ahead and wrote it down as a bug with safari, can't or won't fix. But now we know it's an easy fix - don't write Welcome Back in a page if you don't want this behavior.
My question is if your language is another one - like lang="DE" will it then have the same behavior on a page with the German version of Welcome Back.
Are there other magic strings that serve the same purpose as Welcome Back in Safari's mind.
on edit: changed difficult to fix to difficult to find.
And there's all the quirks additionally to all of that.
I suspect you either didn't read those release notes fully or you don't fully understand what they mean.
I develop primarily on Safari, and only occasionally test on Chrome (for my hobby side project), and occasionally I run into instances where Chrome differs. To me, those look like Chrome bugs because Safari is my "default".
If you're using Chrome (or Firefox, which, in my recent experience, tries specifically to be compatible with Chrome because Chrome is the overwhelming default for people like IE was) primarily, and expecting Safari to exactly match its behavior, of course you'll run into various cases where Safari appears buggy. But to use that to claim that Safari is "the new IE6" is just ludicrous.
I don't know how old other people in this thread are—maybe those making the comparison to Safari weren't actually around for the IE era, or maybe it's just been so long you've forgotten how bad it really was—but I was actually doing some web development back when IE6 and even IE4 were common. They were an absolute nightmare. I don't recall the precise details at this late date, but there were fairly basic HTML tags they didn't implement, and others they implemented completely differently. Javascript features were all over the map.
That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense.
For the tags I do agree but for the Javascript I have a good bunch of pollyfills just for Safari in place.
> That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense.
All of those issues are current and very much not fixed. Yeah they are very old and have been there for almost 10 years I do agree, but it's still broken now, even after 10 years.
