<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 6 Nov. 2016, at 10:03 am, Ryosuke Niwa <<a href="mailto:rniwa@webkit.org" class="">rniwa@webkit.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I DO want to enable experimental features to be enabled in Safari Technology Preview and WebKit nightly builds by default because that's sort of the whole point of having those versions of Safari in the first place.</span></div></blockquote></div><br class=""><div class="">I might be the only one with this point of view (and it explains the confusion since I added the code), but "Experimental" means exactly that: it isn't ready to be enabled by default. If it can be enabled by default, it isn't experimental.</div><div class=""><br class=""></div><div class="">Safari Technology Preview is meant to be used as a full-time browser. It has to be stable. Yes, it has features that haven't yet shipped in main Safari, but they should not be dangerous. The idea of the Experimental Features is that developers can easily choose to enable them, just like they do on other browsers.</div><div class=""><br class=""></div><div class="">I don't understand why we'd pick a different behaviour than Chrome, Firefox, etc in this case. Developers understand this situation.</div><div class=""><br class=""></div><div class="">Dean</div><div class=""><br class=""></div></body></html>