Home Dashboard Directory Help
Search

HTML select control with runat="server" and multiple attribute bug. by Fábio Franco


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 679821
Opened: 7/18/2011 1:17:47 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

In an ASP.net web application, using the "select" HTML control as server control and XHTML 1.1 validation, the "multiple" attribute in the markup will cause a parser error in application server if the value set to the multiple attribute is the "multiple" value (as dictates XHTML 1.1 validation standard).

When using the XHTML 1.1 validation, Visual Studio will even suggest the "multiple" value. If we set the value to "true" instead, the error disappears, but the value will be flagged by Visual Studio as a warning:

"Validation (XHTML 1.1): The values permitted for this attribute do not include 'true'".

Even so, the markup generated to the browser will be correct, using the "multiple" value instead.

One workaround is to add the attribute in the server side code.
Details
Sign in to post a comment.
Posted by Microsoft on 11/29/2011 at 7:53 PM
Thanks for your feedback. This issue is fixed in the next release of Visual Studio.

When runat="server" is present, multiple supports boolean values (true/false) because it is a property on the control. When there is is not runat="server", multiple="multiple" is valid

Thanks
Visual Web Developer Team
Posted by MS-Moderator10 [Feedback Moderator] on 7/19/2011 at 12:11 AM
Thank you for submitting feedback on Visual Studio 2010 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 MS-Moderator01 on 7/18/2011 at 1:50 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.