Additional idea, for even more shiny if the user supports JavaScript, either -- I'm not sure what is better:
* Interrogate all the timezones that currently match the users time for the DST rules ( or failing that, get the times for midnight on the first day of the next 12 months -- hoping that hits a DST transition ), and when presenting users the options, pass that info ( UTC time and matching local time ) along and some JS magic in the browser would create dates from those UTC times and make sure they match what they should be -- disqualifying any that don't.
* Grab the local and UTC time for the first day at midnight local time of the next 12 months ( does DST ever last less then a month anywhere? *g* ), and send that along and let the server disqualify things.
no subject
Additional idea, for even more shiny if the user supports JavaScript, either -- I'm not sure what is better:
* Interrogate all the timezones that currently match the users time for the DST rules ( or failing that, get the times for midnight on the first day of the next 12 months -- hoping that hits a DST transition ), and when presenting users the options, pass that info ( UTC time and matching local time ) along and some JS magic in the browser would create dates from those UTC times and make sure they match what they should be -- disqualifying any that don't.
* Grab the local and UTC time for the first day at midnight local time of the next 12 months ( does DST ever last less then a month anywhere? *g* ), and send that along and let the server disqualify things.