Requesting for an advancement in file modification testing

[6ftrvlr]

Type: Feature Request

To the developer who may concern:
Visual Studio Code gave me a good time when I was handling with codes. One of what I love is the file modification testing, for example, a white dot will appear at one end of the title of the page card. A good feature for the method is that when I stick to undo all my modification made to the file, the file will be examined to be unmodified with the white dot disappear.
But I've recently found some problems about the file modification testing method. When I use the input software along with Windows 11 to input Chinese, my pinyin input will appear on the screen waiting for selecting the ideal Chinese words. But when I regret adding one Chinese word to an unmodified file and I simply use the backspace key to get the pinyin off my file, the file will be examined to be modified. Even if I press Ctrl+Z for dozens of times, the file will still be regarded as a modified one.
My suggestion is to add some complementary methods to examine whether a file is modified. From my perspective, VS Code can introduce a feature where when an undo command is made in the situation where there seems to be no more space for an undo operation, the program will use some method like hashing to compare the file in the editor with the file in the disk. As a result, if they are compared to be the same, the white dot can be removed.
Thanks for any devotion in improving the using experience of VS Code!

VS Code version: Code 1.87.0 (019f4d1, 2024-02-27T23:41:44.469Z)
OS version: Windows_NT x64 10.0.22631
Modes:

[VSCodeTriageBot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!