We've never really formalized an approach to new Web platform features, but the
usual practice has been something like:
- Use an ENABLE macro if the feature is one that ports may be unable to support
immediately or may wish to turn off for other reasons.
- Have it on by default if:
(a) The
Keeping it off by default until it has some mainstream acceptance
seems like a bit of a self-defeating policy for new features; is this
often done in WebKit?
-- Dirk
On Mon, Oct 4, 2010 at 10:12 PM, Maciej Stachowiak m...@apple.com wrote:
Since a ping has been controversial in the past (for
I don't think it is the norm. This one is special for the reasons already
stated.
-Darin
On Mon, Oct 4, 2010 at 11:17 PM, Dirk Pranke dpra...@chromium.org wrote:
Keeping it off by default until it has some mainstream acceptance
seems like a bit of a self-defeating policy for new features; is
Given that a ping really doesn't open up any new privacy holes (just makes
it easier for sites to get the data they're going to gather anyway without
slowing down the experience for the user), it seems like we might as well
enable it by default. If a port doesn't want it, they can always disable
Since a ping has been controversial in the past (for arguably bogus reasons,
but controversial nontheless), I suggest we keep it off by default until we
find it has some mainstream acceptance and/or we discover that more ports want
it.
Regards,
Maciej
P.S. We haven't decided yet if we want
This is a few days late, but I just wanted to let the team know that, as of
http://trac.webkit.org/changeset/68166, WebKit can support a
pinghttp://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#hyperlink-auditing(but
support is disabled by default).
The reason I left it disabled
6 matches
Mail list logo
