I saw this odd behavior as well (version 2.0 build 2210) and your fix worked for me as well. The only difference was that I was editing plain HTML files and saw the same behavior. Thanks for the fix.