> If the behavior is fixed, I don't see why we should arbitrarily turn > something off that's been active since 2.0 (or earlier) unless we've got > something better.
Agreed. I really think we should explore our options here, which includes alternative UX behavior as well as removing the feature altogether. In any case we should proceed thoughtfully and with community engagement. I'm doubtful we could do either by a 3.5 release timeframe, which in my mind is roughly Q1 2012. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
