Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.73.1 OS Version: Windows Steps to Reproduce: Have these internal settings enabled: "editor.inlineSuggest.allowQuickSuggestions": true, "editor.inlineSuggest.allowSuggestOnTriggerCharacters": true The Intellisense interaction with grey text is awesome! But I noticed some flickering. Here is the GIF. ! I grabbed screenshots to make the flickering clear: WLC prediction is in Italics ! When Intellisense is up, Intellisense text is in Italics and wlc prediction is not. ! When .is typed, there is a small latency where wlc prediction disappears. This is because . is a trigger character for Intellisense so first it will process Intellisense and then request the wlc inlineCompletionProvider. ! After that small latency, the wlc prediction shows up again in Italics ! So, the 2 main problems here are 1) When Intellisense pops up while walking the prediction, the prediction goes from Italics to non-Italics. It goes back to Italics when Intellisense is dismissed (either by manual dismissal or item committed). In VS, we keep the font for grey text the same regardless of whether Intellisense is up or not, that would be helpful in VS Code. 2) The small delay that happens when a trigger character is hit and the wlc prediction disappears and comes back again. cc
This is normal, I use Copilot and experience the same thing. I believe this is not a bug but a slight delay in rendering.
I cannot reproduce: ! Please log all calls from VS Code into your implementation of the inline completions provider and send me that log.
Here are the logs, lmk if you need anything else.
I was able to repro the bug in code-oss. ghostText is indeed when the flickering happens. I captured a GIF of the logs so you can see at what point ghostText becomes undefined. ! Here are the logs
I was also able to repro this bug in the sample extension. I used the extension from here - !
Verified that inline completions do not flicker anymore.

Discussion:
*--------------------------------------------------------------------------------------------*/ import { compareBy, findMaxBy, numberComparator } from 'vs/base/common/arrays'; <del> import { RunOnceScheduler } from 'vs/base/common/async'; </del> import { Emitter, Event } from 'vs/base/common/event'; import { Disposable } from 'vs/base/common/lifecycle'; import { IActiveCodeEditor } from 'vs/editor/browser/editorBrowser';

public readonly onDidChange = this.onDidChangeEmitter.event; <del> // This delay fixes a suggest widget issue when typing "." immediately restarts the suggestion session. private readonly setInactiveDelayed = this._register(new RunOnceScheduler(() => { if (!this.isSuggestWidgetVisible) { if (this._isActive) { this._isActive = false; this.onDidChangeEmitter.fire(); } } }, 100)); </del> /** * Returns undefined if the suggest widget is not active. */

})); this._register(suggestController.widget.value.onDidHide(() => { this.isSuggestWidgetVisible = false; <del> this.setInactiveDelayed.schedule(); this.update(this._isActive); </del> <ins> this.update(false); </ins> })); this._register(suggestController.widget.value.onDidFocus(() => { this.isSuggestWidgetVisible = true;

assert.strictEqual(rangeStartsWith(new Range(1, 1, 10, 5), new Range(1, 1, 11, 4)), false); }); <del> test('Active', async () => { </del> <ins> // This test is skipped because the fix for this causes https://github.com/microsoft/vscode/issues/166023 test.skip('Active', async () => { </ins> await withAsyncTestCodeEditorAndInlineCompletionsModel('', { fakeClock: true, provider, }, async ({ editor, editorViewModel, context, model }) => {