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. 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 to good things to come. Perhaps Apple's major open source initiative in the area of Swift language and the Swift ecosystem is also benefiting their approach to WebKit now as well.
Programmatic cut and copy to the clipboard
It’s now possible to programmatically copy and cut text in response to a user gesture with document.execCommand('copy') and document.execCommand('cut'). Having this ability may eliminate some websites’ last need for the Flash plug-in.<p>---<p>:'( - So much pain erased in a single stroke!
Nice to have more visibility into which features are coming to WebKit, especially since they don't release to consumers very often.<p>Bummed to not see WebRTC on here though.
Happy to see Webkit at 98% ES6 completion. Hopefully, all of these updates are flowing into Safari<p><a href="http://kangax.github.io/compat-table/es6/#webkit" rel="nofollow">http://kangax.github.io/compat-table/es6/#webkit</a>
Menu 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?
I 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.<p>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.
I love that they are supporting Shadow DOMs, but until the other browsers support it, the feature is dead in the water. I mean, it's a feature that you'd build a whole app around, but if IE and Firefox don't support it, I can't really do that.
<p><pre><code> fetch("...");
Promise {status: "rejected", result: "Fetch is not yet implemented"} = $1
</code></pre>
If you use a fetch polyfill, it won't install itself because there's a native fetch. But the native fetch is only there to tell you that it's not really there.
It's great to see Apple doing this on the desktop - I wonder if they have any similar plans for Mobile Safari? I would imagine they could do something similar to the process for iOS public betas: allow users to install a cert for Safari Technology Preview, keeping them on a parallel channel of updates.
I wish they support WebGL stuff for 360 Video Playback...
<a href="https://milkvr.com/view/VUNmjRRDV60" rel="nofollow">https://milkvr.com/view/VUNmjRRDV60</a>
While 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.
Where is Safari in terms of security? Speed, battery usage, and standards support are one thing, but as far as I know, neither Firefox nor Safari have the robust level of sandboxing and other Chrome security features.
It would be great if they mentioned El Capitan as a pre- requisite before people download and find out.<p>I know the expectation is that most Macs are up to date but if you can't install it on Yosemite, they should let people know.
That's nice, but no iOS release?<p>Edit: As it is now, it doesn't look very different from what already existed as OSX-side-loadable Webkit Nightlies <a href="https://webkit.org/nightly/" rel="nofollow">https://webkit.org/nightly/</a> or building from source (which even supports iOS simulator!) <a href="https://webkit.org/building-webkit/" rel="nofollow">https://webkit.org/building-webkit/</a>
So what is Apple going to do about fixing bugs in Safari in iOS quicker?<p>I shouldn't have to wait for 3 months for awful rendering issues that entirely prevent me from viewing important websites to be fixed!<p>Obviously it's unpopular to complain about Apple and their dreadful fix timeframes, but there are often thousands of affected websites and often Apple have a fix already checked in and tested. But Apple being Apple, they consider web rendering bugs to be part of their iOS update process, and not just an issue with an app so we all must wait for three months for them to roll it into a major update.<p>I'm seriously considering setting up a seperate website to track iOS bugs. Apple are hardly willing to be open and transparent about bugs, so perhaps it should be taken from their hands?