[webkit-dev] Enabling Experimental Features
betravis at adobe.com
Tue Apr 23 14:22:33 PDT 2013
Thanks for your feedback everyone.
I have filed a bug to track this issue
And will do some further investigation into how best to make it happen.
On 4/22/13 12:33 PM, "Eric Seidel" <eric at webkit.org> wrote:
>FWIW, Blink is going through this right now too. We're attempting to
>move completely away from prefixed development:
>To do that, that requires making it possible enable/disable CSS
>properties at runtime:
>Perhaps this is another opportunity for the two code bases to learn
>from one another as we both implement solutions to this.
>On Mon, Apr 22, 2013 at 9:32 AM, Simon Fraser <simon.fraser at apple.com>
>> On Apr 20, 2013, at 10:03 AM, Maciej Stachowiak <mjs at apple.com> wrote:
>> On Apr 19, 2013, at 3:50 PM, Timothy Hatcher <timothy at apple.com> wrote:
>> On Apr 19, 2013, at 6:15 PM, Bear Travis <betravis at adobe.com> wrote:
>> What do folks think about adding a mechanism for users to toggle
>> like this on in WebKit nightlies? I don't have a definite approach yet,
>> wanted to float the idea for feedback.
>> I like the idea. Having things off for everyone but the engineers is a
>> approach and misses out on testing.
>> We could have WebKit modify Safari's Develop menu to provide additional
>> items to toggle. Safari provides an "Enable WebGL" item, we could inject
>> more items next to it.
>> On Mac, we could at the very last use 'defaults write' to toggle
>> experimental runtime-enabled features.
>> One problem is that most CSS-exposed experimental features are not
>> runtime-switchable. We'd have to do a bunch of work in the parser and
>> resolver to make this possible.
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>webkit-dev mailing list
>webkit-dev at lists.webkit.org
More information about the webkit-dev