Implement direct write fallback proxy

content/child/dwrite_font_proxy/dwrite_font_proxy_win.h

Index: content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
diff --git a/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h b/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
index 63d1f54316b66a2da3c77e7acd7d6722acb77ea2..81dab8c71d11d3c326b2d451f862db567c26a0a3 100644
--- a/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
+++ b/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
@@ -71,6 +71,12 @@ class CONTENT_EXPORT DWriteFontCollectionProxy
   bool LoadFamily(UINT32 family_index,
                   IDWriteFontCollection** containing_collection);
 
+  // Gets the family at the specified index with the expected name. This can be
+  // used to avoid an IPC call when both the index and family name are known.
+  bool GetFontFamily(UINT32 family_index,
+                     const base::string16& family_name,
+                     IDWriteFontFamily** font_family);
+
   bool LoadFamilyNames(UINT32 family_index, IDWriteLocalizedStrings** strings);
 
   bool CreateFamily(UINT32 family_index);
@@ -124,6 +130,8 @@ class CONTENT_EXPORT DWriteFontFamilyProxy
 
   void SetName(const base::string16& family_name);
 
+  const base::string16& GetName();

[ananta, 2016/04/13 23:31:09]

You can change this to family_name() and return the family_name_ member?

[Ilya Kulshin, 2016/04/13 23:59:40]

I dislike the idea of using different naming conventions for functions within
the same class that only differ in implementation details (in this case, being
inlined vs not). I also would not want to force someone to have to rename the
function if the implementation happens to grow in complexity.

+
   bool IsLoaded();
 
  protected: