Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New WebKit features in Safari 15.4

webkit.org

Post reply on HN
Print view View original

161–170 of 311 posts

Re: New WebKit features in Safari 15.4

#161

Post by alwillis »

ryanbrunner wrote: post #129
doctor_eval wrote: post #39

Earlier quoted context omitted.

Unless you’re Chrome, in which case it’s really great. /s

Being first is fine so long as you're not last in anything. If you announce that you're the first do to something and you're the only one who hasn't done something else, you're holding back everyone so you can introduce features no one can really use.

That’s false.

If that were the case, nobody could use new features unless all three major browser engines supported them at the same time and that’s clearly not happening.

It’s pretty easy to use @supports to check for feature support. CSS and HTML are pretty resilient with code they don’t understand.

Remember Chrome ships things all the time other browsers don’t support but that’s okay for some reason…

Re: New WebKit features in Safari 15.4

#162

Post by arilotter »

Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a workaround) - or if it comes out in iOS 16, then a good chunk of our users will never get the fix - so I'm stuck finding a workaround, still.

The bundling of Safari versions with iOS, combined with the draconian policy of "Safari is the only legal rendering engine on iOS", bites me every day as a developer that's working on a mobile site for iDevices.

Re: New WebKit features in Safari 15.4

#164

Post by avazhi »

nwienert wrote: post #148
avazhi wrote: post #143

Is Apple going to do anything about Safari (on my 2021 16" M1 Pro) hitting 200 points in BrowserBench, while Chrome hits 299? Sure, Safari battery life is great, but the browser is slow, buggy (refreshes the page when I back a page half the time; can't speed up videos without audio distortion; typing into the search bar is laggy and I on a daily basis arrow down to select a previously used URL, hit enter, and then fi…

Safari FUD tires me more than any other because it's so consistent and yet consistently wrong (usually driven by feelings from ~2+ years ago). Here's both, no plugins, latest versions: https://user-images.githubusercontent.com/12100/158299113-a0... Chrome opens and closes slower, resizes slower, opens tabs slower, closes tabs slower, restores a closed tab slower, goes back/forward slower, stutters as it scrolls... an…

It's definitely down in a large part to plug-ins. Things like Dark Reader I can understand, but I have no idea why 1Password would cause a 30% performance drop on a site that I don't even have a PW for.

My point still stands about going back a page and arrowing up/down the URL bar to select something and having it swap at the last second. Those behaviours are peculiar to Safari and they're really inexplicable from a user perspective. Whether it's related or not, the mobile version of Safari is even worse - going back a page refreshes 95% of the time, when it shouldn't given the amount of RAM iPhones have had for the past 5+ years.

The Chromium stuttering on M1 Macs is definitely a problem and I wish Google would get to fixing it.

Re: New WebKit features in Safari 15.4

#166

Post by enos_feedler »

arilotter wrote: post #162

Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…

I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?

Re: New WebKit features in Safari 15.4

#167

Post by AbacusAvenger »

arilotter wrote: post #162

Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…

Out of curiosity, what are the WebGL bugs you ran into?

Re: New WebKit features in Safari 15.4

#169

Post by ben-schaaf »

enos_feedler wrote: post #166
arilotter wrote: post #162

Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…

I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?

"Our product doesn't work in safari, use chrome or firefox instead"

Re: New WebKit features in Safari 15.4

#170

Post by heavyset_go »

enos_feedler wrote: post #166
arilotter wrote: post #162

Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…

I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?

Those WebGL bugs might not be present in other browser engines like Gecko or Blink.
Post reply on HN