Dominik Röttsches

We analysed this issue on the Chrome side, [details here](https://bugs.chromium.org/p/chromium/issues/detail?id=1426792#c8). The code @sorinui [mentioned above](https://github.com/microsoft/monaco-editor/issues/3217#issuecomment-1471587448): https://github.com/microsoft/vscode/blob/4c53c189a195c78a305ccce19d47341b9bee9baa/src/vs/editor/browser/controller/mouseTarget.ts#LL1037C12-L1037C12 - fails in newer Chrome and Safari Technology Preview as the `font` property serialisation...

The change in https://github.com/microsoft/vscode/pull/178795/files is not setting `font-feature-settings` for the measurements, which may explain the difference in measurement vs. displayed text.

> Mozilla standards-positions issue URL https://github.com/mozilla/standards-positions/issues/925 #### Explainer [Explainer: Animating font-palette](https://docs.google.com/document/d/1XMTrKH003KBOes6hxzI-3E7LTwp5YwFC-rnzoFpFrfw/edit?usp=sharing)

Can we explore combining 1 and 2 more? Safari still [disables Ahem antialiasing without any flag guard](https://github.com/WebKit/WebKit/blob/38694a9a62607c8f9f4ad897d6c3257b57c2258a/Source/WebCore/platform/graphics/coretext/FontCoreText.cpp#L176). Firefox disables AA as [a combination of a preference setting and a family...

The irregularities stem from the fact that `font-variant-alternates` tries to squeeze different kind of OpenType feature semantics into one property. It's important to look at what kind of mapping the...

From the font technology perspective, for OpenType fonts the maximum glyph extent and maximum per-glyph bounding box should be specified in the HEAD table in the xMin, xMax, yMin, yMax...

> And how do the extents in the 'head' table work in the case of variable fonts? Do they indicate the maximum bounding box under any combination of variation settings,...

Related FreeType changes and Chromium issue comment: * https://gitlab.freedesktop.org/freetype/freetype/-/commit/3481b154430faea9f6b4002519e60a8ad8ebe8d8 * https://bugs.chromium.org/p/chromium/issues/detail?id=1190525#c14 and https://gitlab.freedesktop.org/freetype/freetype/-/commit/369d8be97f537c56f2dbd1d3bd23aba74dc24cea

First of all, big thanks @justvanrossum for the report on Chromium/Skia using the incorrect start axis (vertical up instead of horizontal right). I filed the following issues after further investigation:...

I think I have the `reflect` and `repeat` modes wrong and the observation that the > * The reflecting sector seems too small? is incorrect. For the ``` _sample_sweep(0, 90,...