Nicky McCurdy

This comment on a similar issue could be useful: > The intuitive way [to detect chrome-extension pages] is to check `location.protocol`. https://github.com/facebook/react/issues/8409#issuecomment-319755594 There's also a pull request: https://github.com/facebook/react/pull/10359

I can reproduce with a fresh install of the example: [prettier-chrome-extension](https://github.com/prettier/prettier-chrome-extension/tree/options) (install from source and open extension options)

Sorry, I just realized I changed the example I gave previously in a way that no longer reproduces the issue. Here's a new minimal reproduction: https://gist.github.com/nickmccurdy/5d53943c3c31587991713b29a04c8009 It seems like this...

I can't use React devtools extension because Chrome doesn’t support extensions (like React devtools) injecting devtools into extension pages (like my extension’s options page which uses React). I also can’t...

Bumping, I think this would improve the DX of React extension development

I don't seem to have this issue on `src/index.tsx`

Browsing the installed game in Steam properties and locating the same location in the tracker's settings seems to work. It doesn't seem like [src/app/mtga_dir_ops.ts](https://github.com/Razviar/mtgap/blob/master/src/app/mtga_dir_ops.ts) is able to locate Steam installations...

This appears to be a [VSCode bug](https://github.com/microsoft/vscode/issues/198517) and duplicate of #118. ## Workarounds ### Disable contextual alternatives with other ligatures ``` 'calt' off ``` ### Enable discretionary ligatures ``` 'dlig'...

Monaspace's usage of [contextual alternatives](https://learn.microsoft.com/en-us/typography/opentype/spec/features_ae#calt) for texture healing is unique, so I don't think using them should implicitly enable all ligature features. However, I believe some of the [discretionary ligatures](https://learn.microsoft.com/en-us/typography/opentype/spec/features_ae#dlig)...

That's being tracked in #77. This issue is specifically about behavior in VSCode.