Search

DevEnv crash when editing html inline-css code by 大海mer

Closed

2
0
Sign in
to vote
Type: Bug
ID: 775848
Opened: 1/4/2013 6:23:50 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I don't have VS2012. The bug happends in my VS2010.

The DevEnv will crash when inserting a line-break at a particular position.
Please read [Steps to reproduce] to get more details.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Create a new page file, such as example.aspx

2. Paste some html code containing font-family, such as:
<span style="font-family:仿宋_GB2312">some text</span>

3. Type ENTER between [font-family:] and [仿宋_GB2312]

4. DevEnv crashes.

*Another method:
1. Type some html code that can cause crash and seveas a page file with some other editor(such as notepad). Code example:(just keep that new-line-char behide [font-family:])
<span style="font-family:
仿宋_GB2312">some text</span>

2. Open this file with VS2010.

3. VS2010 crashes.

** This bug won't happen when font-family has an English attribute.

Product Language

Chinese - Simplified

Operating System

Windows 7

Operating System Language

Chinese (Simplified)

Actual results

DevEnv crash.

Expected results

Don't crash.
File Attachments
File Name Submitted By Submitted On File Size  
SxjhPage.aspx 1/4/2013 174 bytes
Sign in to post a comment.
Posted by Microsoft on 1/6/2013 at 6:07 PM
Thanks for your feedback . The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
<http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx>
We can't reproduce this issue on VS 2012.
Posted by Microsoft on 1/4/2013 at 6:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.