Thank you for the tip. I will try it out later todayI use Wipr on macOS and iOS, it works very well in my experience.
Thank you for the tip. I will try it out later todayI use Wipr on macOS and iOS, it works very well in my experience.
It’s works sometimes… and it’s stable when it wants too… like iCloud going out every few weeksTabs? What's a tab?
I still command-click to open new windows. Just like I did in Netscape 1.0N.
Also have been using Safari since Dave Hyatt started the Surfin' Safari blog. Was a huge leap forward from OmniWeb.
Still using Safari. Still love it. Not sure what the whining is about - it's fast, it works, it's stable.
Because you live in the Apple bubble where Apple does no wrong, I like Apple a lot but I can ca them out of safari and iCloud needing to revamped after with the outages that keeping happening on iCloud, because it just works, right ?Never had any issues with Safari and use it everyday. Don't get the hate tbh.
To what? A previous version???? How? Apple locks you into the new version when you upgrade any software! And yes, this is yet another horrible issue with Apple software. If you try it, and discover it's broken, you can't wind it back, and you're stuck with all the new bugs.So switch it back?
The Apple consumer syndrome, let's all pay for half baked extensions & ad blockers, because.. cough cough "privacy".Thanks for pointing out, I will check that.
Edit: Sadly a subscription, no way.
Good points, but I think these are webkit developers that want to know about the problem with rendering. I don’t see too many posts, even in this thread, specifically about how webkit is lacking.15 pages huh.
Anyway, I don’t want to repeat myself. Here is what I want to say.
![]()
(RANT) Safari is a literal piece of (beep)
WARNING: This post is a RANT post. If you don't want to read this, please close the tab NOW. I have also sent feedback to Apple already for all points mentioned below. Ever since I got my M1 MacBook Pro, I was impressed with its great battery life, decent performance and good portability...forums.macrumors.com
WebKit is mostly under the hood where problems resides on other area, UI, experience, interaction etc. That’s why.Good points, but I think these are webkit developers that want to know about the problem with rendering. I don’t see too many posts, even in this thread, specifically about how webkit is lacking.
So the Amazon and Google outages that happen just as often I’m sure aren’t important, Right?Because you live in the Apple bubble where Apple does no wrong, I like Apple a lot but I can ca them out of safari and iCloud needing to revamped after with the outages that keeping happening on iCloud, because it just works, right ?
What's wrong is your perception that this is why Safari doesn't work.What’s wrong? You don’t think developers are coding specifically for Chrome? I mean, they are, you just don’t think they are?
I think that’s the point the webkit developer is making. Safari’s problem doesn’t reside in webkit, it’s in the application layer that the webkit developers don’t have a lot of control over.WebKit is mostly under the hood where problems resides on other area, UI, experience, interaction etc. That’s why.
Developers ARE coding specifically for chrome, it’s been mentioned several times in this thread. Anything that’s coded specifically for chrome won’t work in Safari.What's wrong is your perception that this is why Safari doesn't work.
I wonder whether that's a DRM issue. Are you using an external display by any chance?Some things just don’t work. Playing a TV show on itv.com is an example. Sound but no picture.