impr: enable dots typed effect for ligature languages (@byseif21)

[byseif21]

fix the limitation of dots effect wouldn't work correctly for ligature-based languages cuz connected letters cannot be rendered as individual dots.

before it was not worth the fix for the theme only now after the new typed effect feat #7360 i think this needed.

• introduces a small helper that breaks ligatures only after a word is finished, allowing the dots effect to render correctly while keeping ligatures intact during typing.

• runs only when needed (on word completion or when the typed effect is switched to dots) and avoids any continuous checks or performance overhead.

related #6472

[Leonabcd123]

We now run updateWordWrapperClasses unnecessarily when a user changes fontFamily.

[byseif21]

the thing is I think I still need some of the layout updates it triggers when fontFamily changes. I’ll give it some manual testing to see

[Leonabcd123]

Can we do this?

if (key !== "fontFamily"){
  updateWordWrapperClasses();
}
Ligatures.update(key, wordsEl);

[byseif21]

kinda feel like fontFamily should also trigger updateWordWrapperClasses but can’t really prove it visually enough till now, so yeah ok I’ll leave it limited for now

[byseif21]

check if ok? or heavy and should we do batching instead?

[Leonabcd123]

I'd do this:

words.forEach((word) => {
  if (shouldReset) reset(word);
  applyIfNeeded(word);
})

(not tested)

[byseif21]

i meant performance wise

[Leonabcd123]

Performance wise we're running on the words twice when shouldReset is true, while we can do it one pass. I don't see why go with this approach rather than doing it in one loop.

[byseif21]

what do you think about batching then? too much or worth it?

[Leonabcd123]

I'd say it's worth it.

[Leonabcd123]

Consider replacing with this:

return wordEl.getParent().hasClass("withLigatures");

[byseif21]

why? closest faster and better, getParent() creates a new ElementWithUtils object wrapper every single time

[Leonabcd123]

closest seems less readable, as it doesn't make it clear what element might have the withLigatures class. Also (it might just be me), but I really hate the !! syntax.

[byseif21]

let's do the spin

[Leonabcd123]

I lost, so keep current approach.