tapx-date skins are unusable because they are overridden by the theme.

[joshcanfield]

The way tapx-date loads the css it overrides the skin with the theme
renderSupport.addStylesheetLink(findCalendarAsset("skins/" + skin + "/theme.css"), null);
renderSupport.addStylesheetLink(findCalendarAsset("calendar-" + theme + ".css"), null);

The jscalendar-1.0 documentation isn't very clear on how to use the themes and skins, as far as I can tell, but I think that you either use a skin or a theme. On the demo site (http://www.dynarch.com/static/jscalendar-1.0/index.html) the calendar switches between themes and skins, and does not load both.

By default you get the "system" theme and the "aqua" skin is overridden. "system" doesn't work in Safari on my mac because "activecaption" and "captiontext" are both black leaving the month/year as a black bar. I'd like to use Aqua or Tiger skin...

[hlship]

tapx-datefield: Use a per-library message catalog, define a JavascriptStack for the DateField component, use skin or theme (not both).

Closed by 725f34d