(In reply to comment #22)
> On Chrome Linux and Android we already switched to harfbuzz-ng. So, first step is to figure out who still uses harfbuzz.old and switch them over.
To my knowledge, all upstream WebKit ports using harfbuzz directly are using harfbuzz-ng.
(In reply to comment #22)
> On Chrome Linux and Android we already switched to harfbuzz-ng. So, first step is to figure out who still uses harfbuzz.old and switch them over.
To my knowledge, all upstream WebKit ports using harfbuzz directly are using harfbuzz-ng.