You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+3-2
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@
15
15
<br/>
16
16
<ul>
17
17
<li>All of the strftime() tokens are supported for formatting.</li>
18
-
<li>All of the strftime() tokens are supported for user-interaction except for %z and %Z, for two reasons:. <ul><li>Changing the zone doesn't affect the time at all (an internal timestamp), only the display of the time.</li><li>Changing zones and the zone display properly requires having access to the proper tz_data, up-to-date DST boundary tules for the zone. Date() doesn't know about any of this- it exists in your system's locale only, and depending on your locale, your time zone changes depending on the selected time and date. That data can ALSO change over time. Date() doesn't know anything about that.</li><li>There is no workaround in Javascript for the DST-boundary locale problem without including the entire tz database and creating a custom Date() object (beyond the scope of this plugin) or W3C changing the spec for the Date() object and browsers to change locale in the browser window on-the-fly.</li><li><b>Note</b>: these problems are why most web programmers cheap out and put up the three Select boxes for choosing a date.</li></ul></li>
18
+
<li>All of the strftime() tokens are supported for user-interaction except for %z and %Z, for two reasons:. <ul><li>Changing the zone doesn't affect the time at all (an internal timestamp), only the display of the time.</li><li>Changing zones and the zone display properly requires having access to the proper tz_data, up-to-date DST boundary tules for the zone. Date() doesn't know about any of this- it exists in your system's locale only, and depending on your locale, your time zone changes depending on the selected time and date. That data can ALSO change over time. Date() doesn't know anything about that.</li><li>There is no workaround in Javascript for the DST-boundary locale problem without including the entire tz database and creating a custom Date() object (beyond the scope of this plugin) or W3C changing the spec for the Date() object and browsers to change locale in the browser window on-the-fly.</li><li><b>Note</b>: these problems are why most web programmers cheap out and put up the three Select
19
+
boxes for choosing a date.</li></ul></li>
19
20
<li>Tokens in the format of exclaimation-character instead of percent-character are <b>non-interactive replacements</b>. These are tokens that will be replaced according to strftime() rules, but the user won't be able to interact with them.</li>
20
21
<li>The input on this page is currently configuredas such: <b>Tab</b> advances tokens in an input, and after the last interactive token will advance to the next focusable input. <b>Enter</b> advances to the next focusable object (like tab normally does).</li>
0 commit comments