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

281–290 of 311 posts

Re: New WebKit features in Safari 15.4

#281

Post by imbnwa »

sccxy wrote: post #280

Safari 15.4 broke my web app. Impossible debug and workes fine in 15.3.x and any other browser. Awkward disappearing elements & zindex or canvas bug. Worst browser especially it is impossible to debug in windows.

WebKit broke my org's -based product with 15.x release, have to disable GPU Acceleration in order to prevent full page refreshes while drawing anything complicated after about 20 seconds and its consistent to reproduce. Checkout Apple Dev forum or any HTML5 Game Engine Disco/Board/Tracker

Re: New WebKit features in Safari 15.4

#282

Post by lioeters »

ukfarmer wrote: post #210
lioeters wrote: post #180

Earlier quoted context omitted.

I've been regularly checking that page, delighted with every step of progress as WebMIDI gets implemented in Firefox. In about:config, I have dom.webmidi.enabled set to true. I'm using this test page and waiting for the day it starts working for regular version of Firefox. https://versioduo.com/webmidi-test/

In Firefox 98.0, it actually works but is well-hidden. You not only have to turn on dom.webmidi.enabled in about:config as you've already done, but also need to manually add 'Access MIDI devices' and 'Access MIDI devices with SysEx support' permissions for the page in Tools -> Page Info before reloading, as otherwise it silently fails instead of prompting for confirmation. Hot-plugging interfaces after the browser is…

Oh joy! It works - thanks for the tip about manually adding permissions to the page. I'll have fun with this.

Re: New WebKit features in Safari 15.4

#283

Post by lenkite »

inopinatus wrote: post #209
dmitriid wrote: post #204

Earlier quoted context omitted.

> If Apple do not wish to implement the standard, they should leave the steering group. No, they shouldn't. There was another standard, HTML Imports. It was agreed on, but then Mozilla decided not to implement them. Should Mozilla leave the steering group, too?

HTML Imports were superseded whilst still a draft. Members of a standards body are accountable for their actions. Endorsing a standard, then undermining it, is a gross dereliction of duty. These omissions have a direct impact, and you can draw a straight line from Apple’s overwhelming institutional arrogance to Safari being the “new IE”.

HTML Imports were superb and amazing. No idea why all modularisation needs to be forced to be Javascript. Even a hello-world web component is forced to be in JS.

It's utterly disgusting because you just know that good proposals are nixed behind the scenes because Google doesn't want anyone disabling JS - their ads would suffer. More JS == GOOD, more declarative stuff in the spirit of HTML == BAD.

I really wish Apple would go their own way and propose and implement alternatives. Better than taking Google's highway. I would prefer a fragmented ecosystem over the Tyranny Of Chrome that wants to destroy your privacy and the spirit of the world wide web.

Re: New WebKit features in Safari 15.4

#284

Post by grumpyDev66 »

sccxy wrote: post #280

Safari 15.4 broke my web app. Impossible debug and workes fine in 15.3.x and any other browser. Awkward disappearing elements & zindex or canvas bug. Worst browser especially it is impossible to debug in windows.

I wrote a PWA for my personal use that appears to be broken now that I upgraded to 15.4. I use it for time tracking, so I think it has something to do with Dates or Inputs of type datetime. Haven't had a chance to debug it yet.

Yeah, Safari is the worst...

Re: New WebKit features in Safari 15.4

#285

Post by dmitriid »

lenkite wrote: post #283
inopinatus wrote: post #209

Earlier quoted context omitted.

HTML Imports were superseded whilst still a draft. Members of a standards body are accountable for their actions. Endorsing a standard, then undermining it, is a gross dereliction of duty. These omissions have a direct impact, and you can draw a straight line from Apple’s overwhelming institutional arrogance to Safari being the “new IE”.

HTML Imports were superb and amazing. No idea why all modularisation needs to be forced to be Javascript. Even a hello-world web component is forced to be in JS. It's utterly disgusting because you just know that good proposals are nixed behind the scenes because Google doesn't want anyone disabling JS - their ads would suffer. More JS == GOOD, more declarative stuff in the spirit of HTML == BAD. I really wish Apple…

To quote Ryosuke Niwa, one of the main developers in WebKit [1]:

> Many years ago, Apple's WebKit team argued that we should have declarative way to define custom elements without scripts but we lost to the aggressive push by Google to get things shipped and iterate on it later ASAP.

[1] https://twitter.com/rniwa_dev/status/1352322006448947203

Re: New WebKit features in Safari 15.4

#286

Post by barkerja »

ezfe wrote: post #145
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…

Well, on my M1 MacBook Air Safari hits 275, whereas Edge is 246 Safari: https://i.imgur.com/LcPD5eE.png Edge: https://i.imgur.com/eWhgSuU.png

I got 110.

Your score is quite the improvement over Safari (15.4) on my late-2019 Intel (i9 2.4) 16" MacBook Pro.

Re: New WebKit features in Safari 15.4

#287

Post by barkerja »

teekert wrote: post #37
CharlesW wrote: post #25

A nice/useful bulleted summary thread by Apple's Jen Simmons: https://twitter.com/jensimmons/status/1503454398487408640?s=...

Nice list but arg that Twitter… HNers complain when sites break the back button, but Twitter breaks back scrolling!

This is one of the best features Twitter Blue has to offer; the "Reader" feature for threads.

Re: New WebKit features in Safari 15.4

#288

Post by moltke »

jimkleiber wrote: post #13

Edit: removing the snark/sarcasm I put into it. I was really hoping this announcement would include support for push notifications for PWAs. I've been trying to build a few Discourse forums and they work very well as PWAs except for the fact that iOS doesn't support PWAs sending push notifications. So here's to hoping the next iteration will.

>So here's to hoping the next iteration will.

I've completely given up any kind of hope for iOS.

I hoped for years iOS would do reasonable things like allowing side loading or multitasking or push notifications. Apple knows these things would improve the platform, they don't do them because it would cut into their profits. If these features are ever added to the platform they will be handicapped in some way that makes them almost useless.

Re: New WebKit features in Safari 15.4

#289

Post by sccxy »

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…

15.4 broke my PWA also. Did not have these problems in 15.3.x.

Random rendering glitches/disappearing-reappearing dom elements.

Impossible to debug without Mac and no problems in any other browser.

Seriously frustrating.

Re: New WebKit features in Safari 15.4

#290

Post by enos_feedler »

rtpg wrote: post #182
enos_feedler wrote: post #181

Earlier quoted context omitted.

The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?

Sometimes browsers ship bugs of the "this API just does not work anymore" variety. When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.

that sounds like a good short term fix. I guess I was thinking about bigger things like stadia.google.com only working on Chrome browsers. It all seems arbitrary
Post reply on HN