FWIW, Blink is going through this right now too. We're attempting to move completely away from prefixed development: http://www.chromium.org/blink#vendor-prefixes
To do that, that requires making it possible enable/disable CSS properties at runtime: https://code.google.com/p/chromium/issues/detail?id=232181 https://code.google.com/p/chromium/issues/detail?id=234270 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.fra...@apple.com> wrote: > On Apr 20, 2013, at 10:03 AM, Maciej Stachowiak <m...@apple.com> wrote: > > On Apr 19, 2013, at 3:50 PM, Timothy Hatcher <timo...@apple.com> wrote: > > On Apr 19, 2013, at 6:15 PM, Bear Travis <betra...@adobe.com> wrote: > > What do folks think about adding a mechanism for users to toggle features > like this on in WebKit nightlies? I don't have a definite approach yet, but > wanted to float the idea for feedback. > > > I like the idea. Having things off for everyone but the engineers is a bad > 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 style > resolver to make this possible. > > Simon > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
