Search

BUG formating CSS document by LastCyborg

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 337653
Opened: 4/10/2008 7:40:33 AM
Access Restriction: Public
Primary Feedback Item: 292096
0
Workaround(s)
2
User(s) can reproduce this bug
Every time I press the format document button (MainMenu->Edit->Advanced->Format Document) when I'm using stylesheets editor, it adds a 'backspace' before the URL
E.g.:
before formating
background: url('../../Images/barTitle.gif' ) no-repeat;

After pressing the button 5 times (to make more visible the bug)
background: url(#####'../../Images/barTitle.gif' ) no-repeat;

I used the # char to make it visible, because this web form removes leading backspaces
so, replace the # for a backspace char
Details (expand)
Product Language
English

Version

Visual Studio 2008 (All Products and Editions)
Operating System
Windows Vista
Operating System Language
English
Steps to Reproduce
Write theis little css script
background:url('../../Images/barTitle.gif');
press several times the format document button (MainMenu->Edit->Advanced->Format Document)
Actual Results
background: url(##### '../../Images/barTitle.gif' );

I used the # char to make it visible, because this web form removes leading backspaces
so, replace the # for a backspace char

Expected Results
background: url( '../../Images/barTitle.gif' );
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

Sign in to post a comment.
Posted by Microsoft on 4/15/2008 at 1:45 PM
Hi LastCyborg -

Thank you for the feedback. We have been able to reproduce the issue you describe and are fixing it in the next release of the software (most likely SP1).

Thanks,
The Web Tools Team
Posted by Microsoft on 4/10/2008 at 8:16 PM
Thanks for your feedback. We are escalating 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.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.