mirror of
https://github.com/storytold/harfbuzz.git
synced 2026-11-21 06:51:01 +01:00
hb_accelerate_subtables_context_t::dispatch() filled accelerator entries with a counter that advanced only for the subtable types ChainSubtable::dispatch() knows, while Chain::apply() reads entries by subtable position. A subtable of a reserved type (3, or 6 and up), which the sanitizer accepts and apply() steps over, shifts every later entry down by one, so each later subtable is gated by the wrong glyph set and the last one gets a zeroed entry and is never applied. Output then depends on where the unknown subtable sits in the chain. Add Chain::accelerate(), the same walk Chain::dispatch() does but setting the context's index to the subtable position before each dispatch, and stop the context's dispatch() from advancing the index itself; create() calls accelerate() instead of dispatch(). Unknown- type subtables keep a zeroed entry, which is what the calloc in create() already relies on, and apply() does nothing for them anyway. mort shares Chain/ChainSubtable so it is fixed too; the kerx accelerator already fills one entry per subtable and is untouched. Adds a regression font with subtables [reserved, 1->2, 3->1] to the in-house aat-morx shape tests. Reported by Anthropic's OSS Scanner as ordinary bug ANT-2026-OIN1GIHX. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>