Posted 13 years ago
by Paul Hasselfeldt
Version: 4.0.0287
Platform: .NET 4.0
Environment: Windows 7 (64-bit)
When the ending token for a embedded language stops at the end of the document the interior language ends on the token, skips over the token and then incorrectly restarts just after the language ending token. So if the cursor is at the end of the document (outside the embedded language) interrogating the cursors token (DocuemntEndToken) reports the language incorrectly.
Steps to reproduce in the Sample C# Project:
1) Set language to HTML and allow the sample to load
2) Highlight and remove all lines of text from line 29 to end of document (leaving 29 lines in the editor with the last one empty and the cursor on the last line).
3) Backspace from line 29 one time resulting in 28 lines and that line containing " %>" with the cursor at the right of the terminating ASP script language token. The Language gray out will extend past the ASP end token and fill then entire line.
5) The cursor should now be on the DocumentEndToken and reports the language as VBScript (incorrectly). If you move the cursor to the left with the arrow key it will be on the ASPDirectiveEndToken and correctly report the language as HTML.
Thanks,
Paul
Steps to reproduce in the Sample C# Project:
1) Set language to HTML and allow the sample to load
2) Highlight and remove all lines of text from line 29 to end of document (leaving 29 lines in the editor with the last one empty and the cursor on the last line).
3) Backspace from line 29 one time resulting in 28 lines and that line containing " %>" with the cursor at the right of the terminating ASP script language token. The Language gray out will extend past the ASP end token and fill then entire line.
5) The cursor should now be on the DocumentEndToken and reports the language as VBScript (incorrectly). If you move the cursor to the left with the arrow key it will be on the ASPDirectiveEndToken and correctly report the language as HTML.
Thanks,
Paul
