Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

!== is rendered in different ways depending on context #403

Closed
RReverser opened this issue Apr 3, 2017 · 2 comments
Closed

!== is rendered in different ways depending on context #403

RReverser opened this issue Apr 3, 2017 · 2 comments

Comments

@RReverser
Copy link

For the following sample:

/*
if (typeof vm.parentCtrl.item[c].pnx.addata.stitle !== 'undefined') {  }
if (typeof vm.parentCtrl.item[c].pnx.addata.date !== 'undefined') {  }
if (typeof vm.parentCtrl.item[c].pnx.addata.cop !== 'undefined') {  }
*/

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:

screen shot 2017-04-03 at 16 15 40

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.

@sainaen
Copy link
Contributor

sainaen commented Apr 3, 2017

Hi, Ingvar! :)

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.

@RReverser
Copy link
Author

Interesting, thanks. I'll try to check out later builds.

@tonsky tonsky closed this as completed Apr 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants