Two color previews showing under certain conditions

Description

Build 4112 on Windows 10 x64, regular installer. Latest version of ColorHelper. 2 monitors, not sure if that impacts issue. I’m using a slightly modified version of the SoDaReloaded Dark theme, and my Neon Color Scheme.

The project I currently have open in my main window (there’s another window just for SublimeREPL) is split into 2 panes, so I’m viewing 2 files at the same time, one of them being a .sublime-color-scheme. The other one varies, but it doesn’t have colors in it from CH. When I start up Sublime with the color scheme pane focused (or focus it quickly before the plugin loads), CH displays normally:

However, if I start up with the other pane focused, when CH loads it shows 2 color previews, the one on the right clickable like normal, the one on the left not:

This is the same if I scroll down through the file and more colors are rendered as they come into view.

I also see this behavior when I click to another .sublime-color-scheme file in a different tab, regardless of whether the startup tab has single or double previews. So, in other words, I start up, the file in view has its previews generated (either single or double, depending on focus), then I click to another tab with a different color scheme, and it always generates double previews.

Now, interestingly, I tested this with a random CSS file, and it only generates single previews, regardless of whether it’s focused or not during startup, tab visible or not. I wonder if this behavior is specific to color schemes. I don’t have examples of other files with colors in them, but if you have any ideas for other file types to try, I can find some online.

Finally, I scanned through all the startup messages and couldn’t find any errors related to CH. If there’s a debug mode, let me know and I can enable it. Let me know if you need any other info.

[facelessuser]

@MattDMo, Finally have a solution:

Go to Preferences -> Package Settings -> LSP -> Servers -> LSP-JSON and add this:

// Settings in here override those in "LSP-json/LSP-json.sublime-settings"

{
    "disabled_capabilities": {
        // the trigger characters are too blunt, we'll specify auto_complete_selector manually
        "completionProvider": {
            "triggerCharacters": true
        },
        "colorProvider": true
    }
}

[facelessuser]

I am fairly certain this is not a ColorHelper issue. The secondary color previews seem to have a border that is a slightly different color than the color they represent. We have no code anywhere that would create borders like that.

@MattDMo I will wait for your confirmation, but it is very unlikely that this is not a ColorHelper issue. As things stand now, I think this is a wontfix as there is nothing for us to fix.

@gir-bot remove S: triage, S: more-info-needed @gir-bot add S: wontfix