Hacker News Reader

Comment by tb100 | Hacker News Reader

I wrote up the bug report for this a couple of weeks ago when iOS 14.6 first rolled out. iOS 14.6 at least did finally fix using HLS streams in gl.texUpload2D() on iPhone 12 series (which was broken since launch) but this new bug did mean our delight at that fact was somewhat short-lived!

Well done on your viral tweet that got some personal attention from Apple. Usually when I spend days narrowing down Safari bugs to minimal reproducible test cases, finding workarounds, and writing everything up in detail on the webkit bug tracker the only public response from Apple is the radar importer bot, and then everything goes quiet.

Btw, your original twitter thread implies you were the author of the bug report. Minor annoyance, but I did spend quite a while writing that up :)

View on HN

Chrome 91 on Android also managed to break WebAssembly memory growth which affects our sites too, so it's been a rough couple of weeks working around browser bugs for us. https://bugs.chromium.org/p/v8/issues/detail?id=11863

I find the Chromium team much more willing to engage directly and constructively on their bug trackers at least.

I also encountered this problem, can you please tell me how you solved it on Chrome 91 version?

I’ve been shocked at the number of show-stopper bugs shipping in Safari recently so I’m doing what I can to draw attention to it. I hope it helps the Safari team get the resources they need from the big wigs at Apple.

Also: Didn’t mean to imply I wrote that report. We were about to open a duplicate issue before noticing yours. Thanks!

No worries, I imagine many teams have been through the same process over the past couple of weeks!

We've definitely had the same experience of Safari introducing way more issues with new releases than Chrome, and the fact it's part of the iOS image seems to make quick patching just never really an option.

I just wish they'd engage a bit more directly on the bug tracker - find it hard to believe that twitter is a more effective means to get attention on bugs.

I've always been a Linux user, but recently I got a new Macbook Air and wanted to try a non-Chrome browser.

Then I loaded up my 2005-vintage personal wiki which has been working fine for 15 years on all the browsers I use (Chrome and Firefox).

And it has a tabindex bug in Safari!

https://stackoverflow.com/questions/1848390/safari-ignoring-...

I'm not sure but isn't this a violation of the spec? Or is there some newer thing for tabindex? Either way I switched back to Firefox and Chrome.

I kinda like the idea of a browser that doesn't implement all the Chrome crap. But I also feel like it should interpret 15 year old pages correctly!

I'm confused, you said there's a bug but as far as I can tell it's just that Safari disables using "tab" for more than form elements by default.

It might not be a bug in the sense that it's a spec violation, but it's behavior that every other browser I've used for 15 years has.

If this were a commercial product (my wiki), there would be a bug in the tracker for it :) In the link people have given JS workarounds.

> the only public response from Apple is the radar importer bot, and then everything goes quiet

That's been my experience as well.

When reporting a bug to Chromium you get an answer in hours.

When reporting a bug to WebKit it's mostly crickets.

Reply on news.ycombinator.com