Earlier quoted context omitted.
So a particular website goofing something up is Safari's fault? (Incidentally, just went to Booking.com on iOS Safari. Works fine here.)
You haven't been following the news lately I see. Yes, it is.
Introducing Safari Technology Preview
41–50 of 176 posts
Re: Introducing Safari Technology Preview
#42Re: Introducing Safari Technology Preview
#43Re: Introducing Safari Technology Preview
#44Menu bar says "safari tech preview" and not just safari like WebKit nightly. That is big for me. Does anyone know why WebKit nightly doesn't say WebKit nightly?
The Safari Tech Preview is a full-fledged copy of Safari that bundles its own WebKit frameworks rather than using the system frameworks. As it's a separate application it can have a different name, and use an independent copy of preferences, history, bookmarks, etc. from the system version of Safari. WebKit nightly builds run your system version of Safari with an updated version of the WebKit frameworks. This means t…
Re: Introducing Safari Technology Preview
#45That's nice, but no iOS release? Edit: As it is now, it doesn't look very different from what already existed as OSX-side-loadable Webkit Nightlies https://webkit.org/nightly/ or building from source (which even supports iOS simulator!) https://webkit.org/building-webkit/
I don't see that happening as Safari isn't just some application that runs on iOS as an app, it's more built into the OS itself.
Re: Introducing Safari Technology Preview
#46Good move on Apple's part. Similar to Microsoft providing Windows 10 VirtualBox images with versions of their browsers.
I must have missed something. Are you saying it's possible to run these Safari previews on any platform, not just on OS X?
Re: Introducing Safari Technology Preview
#47Good move on Apple's part. Similar to Microsoft providing Windows 10 VirtualBox images with versions of their browsers.
> ... Similar to Microsoft providing Windows 10 VirtualBox images with versions of their browsers. I must have missed something. Are you saying it's possible to run these Safari previews on any platform, not just on OS X?
Re: Introducing Safari Technology Preview
#48Re: Introducing Safari Technology Preview
#49Earlier quoted context omitted.
https://bencollier.net/2016/03/unable-to-open-links-in-safar... http://money.cnn.com/2016/03/28/technology/iphone-safari-bug... http://techcrunch.com/2016/03/28/its-not-just-you-clicking-o... http://www.news.com.au/technology/gadgets/mobile-phones/new-... http://www.theregister.co.uk/2016/01/27/apple_safari_bug/ http://m.nzherald.co.nz/business/news/article.cfm?c_id=3&obj... http://www.independent.co.uk/life-style/ga…
OK, so users with a particular app had Safari issues, the app got patched, and Apple's planning on fixing their end of the bug per http://techcrunch.com/2016/03/28/its-not-just-you-clicking-o... . "Booking.com associates its app with all sorts of domains — too many domains to be precise. With 2.4MB worth of domain-name-to-deep-link entries, Safari and other apps crash when iOS checks links against its Universal Link…
I also never said that Apple should pause development. Not once. It's totally within the realms of possibility that Apple can do more frequent bug fixes and develop new features. I work on LibreOffice and have back ported bug fixes frequently into old versions. If LO can do it, then so can Apple.
Your assumption of bad faith reflects badly on you, not me.
edit: you can reply, press the link that takes you to my direct comment and hit reply.
I spent the time giving you so many links because I went to Google News and typed in "Safari link crashing Apple" and literally hundreds of news sites were reporting it. It would have taken you a few moments to check this yourself. You can't complain that I've provided lots of links to the issue. Now you know.
And yes, it is Apple's problem that Safari stops working because of a bug in their link association file processing. You state that it is caused "by the rare apps that pad out the file to enormous sizes", except that is a very popular app, so popular that there were so many users that got bitten by this bug that pretty much every news site on the planet reported the issue.
So it wasn't an "edge-case" bug that only affected a few people - it seems to have affected tens or hundreds of thousands of people. Possibly millions. And yes, if there was a security issue the fix would be fine pretty quickly. But you miss the point - even nasty non-security related issues are fixed quicker than a three month time frame. Normally within a month, month and a half. And we maintain at least two versions of LO, unlike Apple who only maintain one version of their OS at any point in time.
As for you putting words in my mouth, please stop doing that. Thanks.
Also: there's a chance you've been rate limited. That message indicates that. Email hn@ycombinator.com to request it be removed and have them explain why it occurred.
Edit 2: I've emailed to request your rate limit be removed - given it is as much my fault as anyone's this got do heated.
Re: Introducing Safari Technology Preview
#50Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction. While I never agreed with the nonsensical "Safari is the New IE" meme that was going around, I did fear that Apple's tendency to develop things in a vacuum would continue to harm WebKit relative to Blink, Gecko, etc. But all signs are pointing…
what steps? Any prove? BTW here a good example how Chrome & Safari team cannot communicate and everyone of them implements their own HTML standards. Here gesture support (pinch and zoom, trackpad) on desktops https://bugs.chromium.org/p/chromium/issues/detail?id=596689 for what reason we have W3C/WHATWG etc. ?