I prefer #1 as well since calendars' laf should be consistent throughout an application, however this does reduce the customization possibilities.
~ Simon On 8/7/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > On 8/7/07, Simon Lessard <[EMAIL PROTECTED]> wrote: > > Hello, > > > > Working currently on a skin I found a strange behavior. The selector > > "af|inputDate::content" is used for both the inputDate field and the > popup > > calendar's body. A direct consequence of that is that you cannot assign > a > > border around the calendar without setting one also on the field > implying > > that all fields will need such border as well. > > > > Since ::content is consistently used throughout Trinidad for the field > > content I would keep it that way. Therefore, I see two solutions: > > > > Always use the " af|chooseDate" root for the calendar and ignore the > > difference between inputDate's popup and inline chooseDate's calendar; > > Add a new selector named " af|inputDate::calendar-body" (or something > else > > if you anyone has a better idea) > > I think I lean towards #1. > > -- Adam > > > > Any opinion, suggestion or objection? > > > > Regards, > > > > ~ Simon > > >
