You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see same !== sequence rendered in three different ways in VS Code with Fira Code 1.204, whereas I would expect first representation to be used in each of them:
Strangely, issue doesn't appear when I try to remove pieces of code in the condition or uncomment this piece of code, but still can't understand the reason why it occurs.
The text was updated successfully, but these errors were encountered:
This is a third report of the weird ligatures in VS Code (see #397 and #372), so at this point I bet it's something wrong with their renderer again and not the font itself. But it may be already fixed in the more recent builds of VS Code with the commit that supposedly fixes both previously reported issues. I don't know if they have nightly builds for you to try though.
For the following sample:
I see same
!==
sequence rendered in three different ways in VS Code with Fira Code 1.204, whereas I would expect first representation to be used in each of them:Strangely, issue doesn't appear when I try to remove pieces of code in the condition or uncomment this piece of code, but still can't understand the reason why it occurs.
The text was updated successfully, but these errors were encountered: