For reasons originating back to when we had two font code paths, we still have OpenTypeVerticalData hanging off of SimpleFontData even though it's only used from HarfBuzzFace when HarfBuzz requests vertical layout information.
Instead of pre-initializing OpenTypeVerticalData in SimpleFontData when the font is potentially going to be used in a vertical context, we should move OpenTypeVerticalData to be managed or owned by HarfBuzzFace and initialized lazily when the first vertical metrics function is invoked.
Since OpenTypeVerticalData still requires fallback to regular (non-vertical layout) bounds from SimpleFontData - we first need to move bounds metrics off of SimpleFontData.
Comment 1 by dtapu...@chromium.org
, Nov 15 2017