Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Has 2.0 Fixed this 1.1 bug? Radio Buttons Are Not Mutually Exclusive When Used in a Repeater Server Control

Reply
Thread Tools

Has 2.0 Fixed this 1.1 bug? Radio Buttons Are Not Mutually Exclusive When Used in a Repeater Server Control

 
 
sloan@ipass.net
Guest
Posts: n/a
 
      01-06-2006
http://support.microsoft.com/default...b;EN-US;316495

Radio Buttons Are Not Mutually Exclusive When Used in a Repeater Server
Control


...


Has 2.0 fixed this bug ?
I coded up a 2.0 page, and get the same behavior.


Or has it (purposely) not been fixed, because it would violate the
rules of the
INamingContainer interface?

I read that 2.0 would fix it, which could have been somebody speaking
without any authority.

Anybody know for sure?

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
2.0 , does it fix BUG: Radio Buttons Are Not Mutually Exclusive When Used in a Repeater Server Control sloan ASP .Net Web Controls 0 01-07-2006 01:24 AM
2.0 , does it fix BUG: Radio Buttons Are Not Mutually Exclusive When Used in a Repeater Server Control sloan@ipass.net ASP .Net 0 01-07-2006 12:17 AM
'SelectedIndex' and 'SelectedValue' attributes are mutually exclusive Stimp ASP .Net 2 10-24-2005 01:53 PM
mutually exclusive radio button js ASP .Net 2 05-19-2005 04:27 PM
Mutually exclusive ALuPin VHDL 2 09-07-2004 04:41 PM



Advertisments