Combined LESS rules not recognized as mixins - by Edward D. Brey

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 780854 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/6/2013 3:01:53 PM
Access Restriction Public


When multiple LESS rules are created at once using a comma to separate them, none of them can be used as a mixin.
Sign in to post a comment.
Posted by Van [MSFT] on 2/7/2014 at 12:38 PM
This has been fixed in Update 2 RC.
Posted by Van [MSFT] on 2/7/2014 at 12:38 PM
This has been fixed in Update 2 RC.
Posted by Mads [MSFT] on 3/18/2013 at 8:50 AM
Thanks for clarifying, Edward. I misunderstood. We now know what is needed to continue with this bug. Thanks again - a fix is coming.
Posted by Edward D. Brey on 3/12/2013 at 12:37 PM
This issue is about CSS rules that are not mixins, for example, ".one, .two {}", as opposed to multiple mixins, which would be like ".one(), .two() {}". LESS inherits from CSS the support for comma-separated plain-old CSS rules. These CSS rules should be able to be used as a mixin in a new rule, regardless of how they were declared.
Posted by Mads [MSFT] on 3/12/2013 at 10:47 AM
Thanks for the feedback. The official LESS compiler doesn't allow you to declare multiple mixins separated by a comma. It will throw a syntax error. The LESS editor in Visual Studio reflects this behavior.
Posted by Microsoft on 3/11/2013 at 11:41 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Helen [MSFT] on 3/6/2013 at 3: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(