add ENABLE_WEB_SOCKETS

add ENABLE_WEB_SOCKETS

BUG=12497
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=29610

[darin (slow to review), 2009-10-05 18:30:52]

LGTM (assuming that the feature is disabled in some other way such that web
pages could not be able to notice the difference)

[Yuzo, 2009-10-06 04:18:43]

LGTM.

I have no comments to add.

[ukai, 2009-10-06 08:54:30]

On 2009/10/05 18:30:52, darin wrote:
> LGTM (assuming that the feature is disabled in some other way such that web
> pages could not be able to notice the difference)

For now, by enabling WEB_SOCKETS, it could be able to notice the difference that
"WebSocket" property found in window (i.e. "WebSocket" in window becomes true.),
although typeof window.WebSocket is undefined.
Is it acceptable?

[tyoshino (SeeGerritForStatus), 2009-10-06 09:38:50]

LGTM

[ukai, 2009-10-21 03:52:51]

On 2009/10/06 08:54:30, ukai wrote:
> On 2009/10/05 18:30:52, darin wrote:
> > LGTM (assuming that the feature is disabled in some other way such that web
> > pages could not be able to notice the difference)
> 
> For now, by enabling WEB_SOCKETS, it could be able to notice the difference
that
> "WebSocket" property found in window (i.e. "WebSocket" in window becomes
true.),
> although typeof window.WebSocket is undefined.
> Is it acceptable?

Now, webkit r49843 landed, web pages could not be able to notice the difference
without explicitly specifying --enable-web-sockets.