> I don't mind which one stays. If it works on Macs -- I believe that's what > you use > Do you have an alternative browser to test?
I do use Mac, safari normal (though Firefox seems faster, at least on the javascript side of things, but it just aint as pretty!) so I have tried it in Firefox and Camino, and yeah it works fine apart from a slight flicker opening the months/years drop downs. > complying with their 'copyright' notice on the HTML code seems a bit too > much to me. Keeping it with the script or adding it when there's embedded > data sounds OK, but adding it to each and every HTML page... sure, perhaps that's not the best one then, I didn't really look too much in to it to be fair. I think it depends entirely on the implementation. To make sure we're all thinking on the same lines; If your creating an application for a known audience and need fast data entry I can see a need to allow input in the fastest way, which would be a single text box, and in the format most natural to the user. But if you are building an international public web site then it's going to be inanely difficult to build the entire site so it feels "natural" to every user. Therefore providing a globally accessible method to select the date in a way that is very hard to get wrong, i.e. a Javascript calendar that falls back to select boxes to remain usable without Javascript, would be, in my opinion, a reasonable option.
