Happy to see Webkit at 98% ES6 completion. Hopefully, all of these updates are flowing into Safari
Introducing Safari Technology Preview
121–130 of 176 posts
Re: Introducing Safari Technology Preview
#122While I'd love to use this app, there's no way to transfer your current Safari config — including extensions and the last browser session — to the Tech Preview. Copying the files doesn't work.
That's actually intentional, this is not supposed to carry over the current Safari configuration.
If you want that, you might as well keep using WebKit Nightly, which reuses your Safari stuff.
Re: Introducing Safari Technology Preview
#123That'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/
That's because it is nearly the same as WebKit Nightly but with a few things included that WebKit Nightly can't include such as iCloud sync. Apple already explained on the same page as the OP link:
> You may already be familiar with the WebKit Nightly, which serves a purpose similar to that of Safari Technology Preview. For most people, we think Safari Technology Preview is a more convenient and stable way to live on recent WebKit changes. Unlike the nightlies, Safari Technology Preview supports the full set of iCloud-based Safari features, including iCloud History and iCloud Tabs. And we’ll use the time between Safari Technology Preview releases to curate and test updates to a point where we think developers will find it practical to use as their primary browser.
Re: Introducing Safari Technology Preview
#124While I'd love to use this app, there's no way to transfer your current Safari config — including extensions and the last browser session — to the Tech Preview. Copying the files doesn't work.
That's actually intentional, this is not supposed to carry over the current Safari configuration. If you want that, you might as well keep using WebKit Nightly, which reuses your Safari stuff.
Sorry to be obstinate, but then I'm not going to use it. Too much hassle. If it turns out that the Tech Preview is too buggy, I can't easily migrate back.
Re: Introducing Safari Technology Preview
#125Apple'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…
I'll take them seriously when they release something that runs on Windows.
They did release Safari for Windows and virtually nobody used it so Apple discontinued it. What are they supposed to do?
Re: Introducing Safari Technology Preview
#126I find Safari to be the nicest browser to use in general, but Chrome seems to have a leg up on performance in key areas like new tab creation especially when opening a link in a new tab. It's weird lapse for Safari to lag in certain situations. I hope they continue to iteratively improve the performance of the general UI and improve the general behavior of the developer tools in addition to adding these new techs.
If you change the new tab to a blank page in the preferences, it opens instantly.
I just wish one thing: that it would remember the zoom level on a per website basis.
It's incredible that it's still impossible to do so. Don't the devs use Safari? Or maybe they all have perfect vision and the most expensive displays.
Re: Introducing Safari Technology Preview
#127Nice to have more visibility into which features are coming to WebKit, especially since they don't release to consumers very often. Bummed to not see WebRTC on here though.
As someone who's focus is on security rather than web development, I'm in no rush to have Safari support WebRTC. Would you mind to explain why you're a fan of WebRTC?
Re: Introducing Safari Technology Preview
#128Earlier quoted context omitted.
There's easier ways to irritate your users. Most websites irritate their users, actually.
Speaking of clipboard shenanigans. Could be imagining it, but I seem to remember a while ago there being something certain websites were doing where if you selected and copied text from them, the text that ended up on your clipboard would have a synthesized paragraph about copyright/attribution appended to it.
iBooks does exactly that; it irritates me to no end. I know why they do it, but still.
Re: Introducing Safari Technology Preview
#129Earlier quoted context omitted.
Their time to fix bugs and regressions in iOS is 3 months! Edit: Again, I write a very unpopular opinion. Yet there are hundreds of regressions that have bit developers. Some of those bugs require workarounds that would be otherwise unnecessary on any normal environment with rapid updates - like Chrome or Firefox. That increases developer effort, and there have been cases that Apple have entirely missed their update…
Downvoter here: I downvoted early on because you're making an argument that seems to me both not particularly good and off-topic to the post you replied to. OP posited: “Apple'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.” You basically responded, “They're still not as good as I want them to be…
I don't care how much I've been downvoted, especially by someone who contributes their own comments so infrequently to HN, but it's funny how you only now decided to make a comment.
I personally feel that Apple are still not as good as not only I want them to be, but pretty much anyone who uses or develops for iOS. But yes, you categorize my comments and opinions well - Apple are indeed not very responsive, and yes Apple need to do a hell of a lot better. As I say, the votes are bouncing up and down, so I'm not the only one who has holds this opinion.
And no, it's not off-topic. As an end user, I now have to incorporate workarounds that no normal user should have to make to get around their issues - I'm literally running Charles proxy (until iOS 9.3 fixed their issue) and a rewrite rule to get around their ridiculous bug. And I had to run it for 3 months. Firefox and Chrome has an issue like this one fixed within their next cycle - in other words, in no time at all.
All of which means I'm not afraid, ashamed or worried about downvotes from folks like yourself. I've not said anything offensive, sexist, racist or even all that terribly controversial. You've finally come out of the woodwork to make your comment, which I appreciate. If only you had made it sooner, eh?
Re: Introducing Safari Technology Preview
#130Earlier quoted context omitted.
There's easier ways to irritate your users. Most websites irritate their users, actually.
Speaking of clipboard shenanigans. Could be imagining it, but I seem to remember a while ago there being something certain websites were doing where if you selected and copied text from them, the text that ended up on your clipboard would have a synthesized paragraph about copyright/attribution appended to it.
Yeah, many tech news sites used to do this. I'm not positive, but I think TechCrunch did at one point, I could be wrong though. Absolutely hate it personally!