Good to know, I'm going to use that syntax as well.
On 8/7/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > For a similar component internally we're using: > > af|chooseDate::today > af|chooseDate::today-link > af|chooseDate::regular-day > af|chooseDate::regular-day-link > af|chooseDate::prev-month-day > af|chooseDate::prev-month-day-link > > ... with pairs of styles for the table cell and the link itself. > > -- Adam > > > On 8/7/07, Simon Lessard <[EMAIL PROTECTED]> wrote: > > Along the same lines I think we should assign a style class to the > various > > cells in the calendar (currently you have to use a selector looking like > > "af|chooseDate::content a" to achieve this). > > > > > > ~ Simon > > > > > > 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) > > > Any opinion, suggestion or objection? > > > > > > Regards, > > > > > > ~ Simon > > > > > > > >
