Area Normal (by Blaze Type) is served with different vertical metrics on the web than on the desktop, even though both carry the same version string (Version 2.000; Glyphs 3.4 (3400)).

Desktop (Creative Cloud font sync), all 44 Area styles:
hhea / OS/2 typo / OS/2 win: 950 / -250, USETYPOMETRICS on

Web projects (use.typekit.net), all Area Normal upright weights we checked (100–900):
hhea 1300 / -340, OS/2 typo 750 / -250, OS/2 win 1300 / 340, USETYPOMETRICS off

capHeight is 780 in both. Because browsers use the web files' hhea/win values, capital letters render about 0.09em lower on websites than in design tools that use the desktop font. Text in buttons and labels looks off-center on the web while it is centered in the design files.

This is not a browser or device issue: Chrome, Safari and Firefox all read the same values from the file. A brand-new web project created today serves the same 1300 / -340 files, so the difference seems to come from the web font serving pipeline rather than an outdated project.

Expected: web project files should have the same vertical metrics as the desktop version (950 / -250, USETYPOMETRICS on), which also matches the foundry's current build on blazetype.eu.