Peter Kasting pkasting at google.com
Mon Jul 13 10:52:59 PDT 2009

On Mon, Jul 13, 2009 at 10:47 AM, David Hyatt <hyatt at apple.com> wrote:

> I agree.  We should formalize this as policy too in my opinion.  Maybe
> something time-based, e.g., if you have an implementation of a new Web
> technology that is going to take > (1month?) to implement, then the feature
> should be landed inside ENABLE ifdefs (that can then be removed when the
> feature is sufficiently far along).

For Chromium this kind of time frame can be problematic, since there's
pretty much no guarantee of when a WebKit trunk build could be shipped as
(eventually) a stable Chromium/Google Chrome release.  Even having an
incomplete feature in the tree a few days can result in the incomplete
feature getting shipped to web authors.

There is a general problem here of "when is the WebKit trunk shippable by
third-parties", which is an issue too large and hairy for me to get into,
let alone propose concrete changes for.  However, if we simply had a policy
of "if a web author can detect and try to use the feature, but it doesn't
work right yet, then put it under a flag", that would at least take care of
this piece of the problem.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20090713/f58fd2a3/attachment.html>

More information about the webkit-dev mailing list