html - Visual Studio (2012 and lower) deletes CSS properties -


With Visual Studio 2010 I really have a weird problem. When I add CSS properties to a gradient in my stylesheet, Visual Studio is going to delete it sometime after debugging.

For example, the code I add to your stylesheet like:

  .button {/ * Firefox * / background-image: socks-linear-gradient (top, # FFF; #fiffeff); / * Chrome, Safari * / background-image: -vebkit-gradient (linear, left top, left bottom, color-stop (0, # FFF), color-stop (1, #FEFEF)); / * Modern browsers * / background-image: Linear-shield (top, #fff, #phiff); / * IE * / filter: Projed: DXImageTransform.Microsoft.gradient (startColorStr = '# ffffff', Andcolrstre = '# Afifef'); }   

Sometimes when I start debugging, Visual Studio edits CSS:

  .button {/ * firefox * / background -seven: linear-shield (top, #fff, #FEFEF); / * Chrome, Safari * / / * Modern Browser * /}   

So it seems that the Visual Studio does not want to delete some features which it does not know. It's really upset Any idea how can I stop it?

This is not the problem of CSS comments. It can also happen without comment.

Update

It seems that files containing the CSS file are saved. When I edit my master layout and save it, Visual Studio destroys the above mentioned properties in the written CSS file.

And its no is a CSS3 problem because it probably does not touch my range-radius classes and ID, though this property is filtered, I have permissions in the Visual Studio CSS file Without changing my things is to stop.

Update 27. June 2014

The problem was resolved in Studio 2013

OK I found a temporary setting for this:

"Filter:" The style is that the last one list Except all "background-image:" styles are disappearing. It is not that it is being removed which he does not know, it is only removing everyone but the last "background image" style should be the way to create a Microsoft (intentional) filter listed and an MS specific background image Style play well together, although they have not done it very well, definitely to counteract an MS VS fault, just right click in the CSS class Have code similar to:

  Background color: #EBEBEB; / * The color of the background fallback for unsupported browsers * / background-image: the -vibkit-gradient (linear, left top, right top, (#FFFFFF), (# DAD6E7)); Background image: -WebKit-Linear-shield (left, #FFFFFF, # DAD6E7); Background image: -Mo-linear-shield (left, #FFFFFF, # DAD6E7); Background-image: -mms-linear-shield (left, #fffff, #dad6e7); Background-image: -o-linear-shield (left, #fffff, #dad6e7); Background-Image: Linear-Slope (Left, #FFFFFF, # DAD6E7); Filters: Przid: Dximage Transform. Microsoft.Gradient (Startcollerstrat = '#FFFFF', Endocrilarates = '# DAD 6E7', Gradient Type = '1'); / * IE6 - IE9 * /   

and then select "Create Style ..." Then click "OK" without changing anything and delete it all, but skipped the previous background image. Try changing the sequence of background-image styles and leave webkit and then look for yourself.

You will see that if you remove the "filter" style: "problem" though We need (for this example), so the solution "filter:" looks like the style above all "background-image" lines. Once you do this, leaving them alone and the problem Goes away.

  Filters : Projed: DXImageTransform.Microsoft.gradient (startColorStr = '#FFFFFF', Andcolorset = '# DAD6E7', Gradient type = '1'); / * IE 6 - IE 9 * / background-color: # Ibiibiibi; / * unsupported browser fallback background color * / background-image: -vibkit-gradient (linear, left top (# Ffffff), from (# DAD 6 e 7)); background-image: -vebkit-linear-gradient (left, #FFFFF, # DAD6E7); Background-Image: -Mo-Linear-Slope (Left, #FFFFFF, # DAD6E7); Page Umi-images -mms-linear-gradient (left, # Ffffff, DAD # 6 e 7); BA Ckground-image: -o-linear-gradient (left, #FFFFFF, # DAD6E7); Background-Image: Linear-Slope (Left, #FFFFFF, # DAD6E7);     UPDATE:   works only for uptime when applied to VS formatting when you "build style" .. - & "Style Festival" dialog because I saw it above right above it so it should be something else.   

Comments