Sanket Joshi
Sanket Joshi
> But if I understand you correctly, it would be up to the UA whether to replace the entire contents or just add something new, right? So the code editor...
> I wonder then, given that this usage is quite different from the form-filling help that the `autocomplete` attribute offers, whether it would not make sense to use a different...
> I also think it should be made clear which input type (before input event and input event) will be used for this. There is called called `insertReplacementText` and the...
> From the explainer: > > > Many sophisticated editors that could benefit from the EditContext API also integrate their own writing assistance features and thus may opt out of...
> The second, which is not documented in the explainer (unless I missed it?), is about what **values** the `autocomplete` attribute may have when it is used on a non-form...
> Maybe I don't fully understand, but it sounds to me like a very different feature than what autocomplete is today, such as: > > Current autocomplete: > > *...
@yisibl Would you be able to provide more details on your scenario for this API?
@slunyou10 Were you trying to file an issue about highlight events?
Yes, I've been working on a fix for the last couple of days but haven't been able to get to the root cause yet. I'm planning to revert the regressing...
I have reverted the regressing change and uploaded a fixed vsix. Keeping this issue open and renaming it to track the re-enablement of VS 2019 support.