Subject: Re: 'Leap Second' to Be Added on New Year's Eve This Year
@Newsgroups: comp.lang.c,comp.programming,alt.comp.os.windows-10,alt.os.linux.˙
@ ubuntu
@References: 
@ 
@  
@ 
From: Mark Lloyd 
@User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
@ Thunderbird/45.5.1
@MIME-Version: 1.0
@In-Reply-To: 
@Content-Type: text/plain; charset=windows-1252; format=flowed
@Content-Transfer-Encoding: 7bit
@Lines: 18
@Message-ID: 
@X-Complaints-To: abuse(at)newshosting.com
@NNTP-Posting-Date: Sat, 31 Dec 2016 20:29:27 UTC
@Organization: Newshosting.com - Highest quality at a great price! www.newshos˙
@ ting.com
@Date: Sat, 31 Dec 2016 14:29:27 -0600
@X-Received-Bytes: 1569
@X-Received-Body-CRC: 334572728
@Xref: b4gate.uuhec.net comp.lang.c:41977 comp.programming:1413 alt.comp.os.wi˙
@ ndows-10:1784
 
On 12/30/2016 04:37 PM, Keith Thompson wrote:
 
[snip]
 
> That depends on how Javascript, or the code your web page is running,
> handles leap seconds.
>
 
I did make a little change yesterday, to limit the Javascript 
Date.getSeconds() and Date.getUTCSeconds() function return value to 59, 
since the analog clock can't display properly (since it uses an angle 60 
= 0). That is, I have it show 23:59:60 as 23:59:59 rather than 23:59:00.
 
-- 
Mark Lloyd
http://notstupid.us/
 
"Call on God, but row away from the rocks." [Indian proverb]

--- ViaMAIL!/WC v2.00