Closed defects are harder to find, which is part of the reason we close them.
If you do some research into a defect it would be helpful for others if you add a comment about why it's invalid. Also, Using tapx isn't really a workaround On Aug 12, 2011 12:21 AM, "Massimo Lusetti" <[email protected]> wrote: > On Fri, Aug 12, 2011 at 2:44 AM, Josh Canfield <[email protected]> wrote: > >> TAP5-178 - Support for optional validator constraints >> As far as I know this is still a valid request. >> >> TAP5-31 - DateField Calendar component has scroll bar burn through >> Has the calendar implementation changed? > > These two was old and never touched for the same time (18 Sep 2008), > are marked to affect only 5.0.x, are unassigned and plus the TAP5-31 > has a workaround in the comment: use the tapx-datefield so I decided > to "close" them. > > FWIW The DateField component behave strange here on my box so I have > thought I'll give it a look for trying to fix when the 5.3 has been > rolled out. > >> They just have been closed with a "Please open a new one for 5.3 if >> this still applicable" > > The text is the same as other issues but it didn't mean I've not looked at them. > > I think I'll go as Howard suggest to tag the next issues and continue > to close the one I think should be closed. > If you feel strong about some you can reopen and assign to you, no > arrogance here. > > Thanks for spotting them out. > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
