Chrome-part of disabling web fonts by default. ...

Chrome-part of disabling web fonts by default while still alowing SVG fonts

(The webkit part is http://codereview.chromium.org/67209/show and 
 http://bugs.webkit.org/show_bug.cgi?id=25239 )

1. Adds '--enable-remote-fonts' command line switch
2. Adds a field ('enable_remote_fonts) to WebPreference
3. Pass the value of enable_remote_fonts to the corresponding field in WebCore::Settings (m_downloadableBinaryFontsEnabled)

BUG=9633
TEST: 1. Run Chrome with and without '--enable-remote-font' command line flag and go to http://www.alistapart.com/d/cssatten/heid.html. Without the flag, the page should be rendered with 'dull-looking ordinary' fonts. With the flag, the page should be rendered with 'decorative' remote fonts.
2. Even without the above flag, Chrome should should get 100/100, with no  boxes in the upper right corner (still has the Linktest Failed error).

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

[jungshik at Google, 2009-04-17 22:44:45]

This is a Chrome-side companion to http://codereview.chromium.org/67209/show
(Webkit change) to use in the 2.0 branch.

[tony, 2009-04-17 22:51:35]

I agree with brett.  Do we need a value in pref_names for this?  There's no UI
for setting the pref so it's probably sufficient to just have the command line
flag.

[jungshik at Google, 2009-04-21 17:27:01]

Hmm. why did I miss this reply? :-)

As for the pref entry, I debated about it myself before making this patch. I
thought some advanced users might want to edit their pref. file and set the
value there, but they can achieve the same goal with a command line flag and a
shortcut (except when they start Chrome by clicking on an html file) So, I'll
get rid of it as you suggested. 


On 2009/04/17 22:51:35, tony wrote:
> I agree with brett.  Do we need a value in pref_names for this?  There's no UI
> for setting the pref so it's probably sufficient to just have the command line
> flag.

[jungshik at Google, 2009-04-21 20:36:11]

Patch updated. Can you take another look? 

On 2009/04/21 17:27:01, Jungshik Shin wrote:
> Hmm. why did I miss this reply? :-)
> 
> As for the pref entry, I debated about it myself before making this patch. I
> thought some advanced users might want to edit their pref. file and set the
> value there, but they can achieve the same goal with a command line flag and a
> shortcut (except when they start Chrome by clicking on an html file) So, I'll
> get rid of it as you suggested. 
> 
> 
> On 2009/04/17 22:51:35, tony wrote:
> > I agree with brett.  Do we need a value in pref_names for this?  There's no
UI
> > for setting the pref so it's probably sufficient to just have the command
line
> > flag.

[tony, 2009-04-21 21:03:27]

LGTM!