Adding support for windows safari. This requires registering the o3d plugin w...

Adding support for windows safari. This requires registering the o3d plugin with firefox (via registry entries)
and adding Safari to the list of supported User Agents.

[gman, 2009-10-23 00:00:09]

http://codereview.chromium.org/326001/diff/1/3
File plugin/win/config.cc (right):

http://codereview.chromium.org/326001/diff/1/3#newcode85
Line 85: if (user_agent.find("Firefox") == user_agent.npos &&
I just have to ask, is there some reason we check this at all?

Why not just allow everyone and exclude ones we want to exclude?

Otherwise we may be limiting ourselves. For example Flock, Sleipnir, Opera. Some
of them may just work except for this check. Others may not work today but they
might fix them and yet we still won't work because of this check.

[vangelis, 2009-10-23 01:19:55]

http://codereview.chromium.org/326001/diff/1/3
File plugin/win/config.cc (right):

http://codereview.chromium.org/326001/diff/1/3#newcode85
Line 85: if (user_agent.find("Firefox") == user_agent.npos &&
The problem is that while we know which browsers we run on, we don't quite know
which ones we don't.  With the current implementation all this does is pop up an
alert saying that your browser might not be supported.  It kind of feels safer
this way rather than crashing the browser without warning. 

On 2009/10/23 00:00:09, gman wrote:
> I just have to ask, is there some reason we check this at all?
> 
> Why not just allow everyone and exclude ones we want to exclude?
> 
> Otherwise we may be limiting ourselves. For example Flock, Sleipnir, Opera.
Some
> of them may just work except for this check. Others may not work today but
they
> might fix them and yet we still won't work because of this check.
> 
> 
>

[vangelis, 2009-10-27 19:33:26]

Are we ok with checking this in or do you feel strongly about changing the
browser whitelist method?