Use removeFontFace to avoid resetting fontSelector.

Source/core/frame/Settings.h

Index: Source/core/frame/Settings.h
diff --git a/Source/core/frame/Settings.h b/Source/core/frame/Settings.h
index 76f5ac5097f6f27694fd84a4fe0cce2853601043..5448dbc56dde41d01bbffa0330939d852c3f5c80 100644
--- a/Source/core/frame/Settings.h
+++ b/Source/core/frame/Settings.h
@@ -55,6 +55,7 @@ public:
     static PassOwnPtr<Settings> create();
 
     GenericFontFamilySettings& genericFontFamilySettings() { return m_genericFontFamilySettings; }
+    void notifyGenericFontFamilyChange() { invalidate(SettingsDelegate::FontFamilyChange); }

[dglazkov, 2014/01/29 05:11:50]

I was hoping to avoid this function altogether. Do we need a VC to talk this
through?

The key thing here is that in production, the genericFontFamilySettings is only
set once, when creating the renderer. There are no sub-systems that enable
changing them, right? Why do we need this complex notification system that
attempts to pretend that this change could happen anytime?

[tasak, 2014/01/29 10:13:43]

Looking at some layout test or WebSettings, GenericFontFamilySettings might be
updated from chrome side via some interface?

I'm not sure. At least, some layout test depends on that
window.internals.settings.setXXXFontFamily can update all existing
GenericFontFamilySettings.
So we can fix (or remove) the layout tests? (e.g.
fast/text/international/content-language-font-selection.html)

 
     void setTextAutosizingEnabled(bool);
     bool textAutosizingEnabled() const;