Search

backspace stops working in aspx/ascx files after left open for a while by Wombat33

Closed
as External Help for as External

8
0
Sign in
to vote
Type: Bug
ID: 574500
Opened: 7/12/2010 11:29:58 AM
Access Restriction: Public
0
Workaround(s)
5
User(s) can reproduce this bug
in source view of html pages (aspx, ascx) some keys stop working; backspace key in particular. It may have something to do w/ focus but I'm not sure
Details (expand)

Product Language

English

Visual Studio Version

Visual Studio 2010

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

Open solution of reasonable size (4 or more projects w/ at least 10 files each)
Leave the editor open for some time (using it or not for maybe 40+ minutes). switch to a aspx or ascx (that was open) and backspace doesn't work.

Fixing this is as easy as closing the file and reopening it. Something close all but this will work as well.

Actual Results

backspace doesn't work

Expected Results

backspace should work
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey.

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by TimeTrips on 7/14/2010 at 9:16 AM
I've noticed the same behavior. Several keys will stop working, specifically the backspace and backarrow keys. I have not found the pattern that induces the problem, but if I close the aspx file and then reopen it the problem goes away for that file, however any other open ASPX pages (in source view) continue to have the problem. Switching to Design view and back to Source view has also eliviated the problem (but not sure that is a consistent work around yet).
Posted by Microsoft on 7/12/2010 at 11:02 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 7/12/2010 at 5:08 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.