16959 2012-05-07 17:11:13 +0000 i18n-ISSUE-88: local/floating date terminology 2016-04-18 23:11:32 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WORKSFORME P2 editorial --- 1 addison travil mike public-html-admin public-html-wg-issue-tracking public-i18n-core robin rubys travil public-html-bugzilla oldest_to_newest 67393 0 addison 2012-05-07 17:11:13 +0000 2.5.5.7 Global dates and times http://dev.w3.org/html5/spec/single-page.html#global-dates-and-times This defines a 'global date and time', which is the same as a 'local date and time', only with a time zone representation. I propose changing the 'local' value to use the term 'floating' (since it is not truly local). The term 'global' could remain. I would also suggest adding a reference to w3.org/TR/timezone (our note) to help users understand when to use which type. 70181 1 contributor 2012-07-18 07:04:24 +0000 This bug was cloned to create bug 17855 as part of operation convergence. 100067 2 travil 2014-02-07 22:47:02 +0000 My plan for this bug is to add the reference to w3.org/TR/timezone and change the "local date and time" section to "floating date and time" (which section is still needed by the HTMLTimeElement, regardless of removing the <input type="datatime-local"> control. This will align the terminology and hopefully avoid author confusion. 100234 3 travil 2014-02-11 01:09:11 +0000 The change to rename local to floating terminology has landed in HTML5.1. Please review for consistency/correctness. Thanks! https://github.com/w3c/html/commit/22162bf56037c266c78f9c9d77ccd1c8fda40b77 100242 4 addison 2014-02-11 04:13:29 +0000 Diff looks good to me, but I don't see the addition of the reference to w3.org/TR/timezone? Is that intentional? 100244 5 addison 2014-02-11 04:56:22 +0000 Argh. I see it addressed in bug 16957 101185 6 travil 2014-02-22 01:42:31 +0000 Now back-ported to fix the HTML5.0 CR issue: https://github.com/w3c/html/commit/efd24702b2bd4803850971b55745210e50af6420 Leaving active as there is some concern raised with this change Removed the CR keyword as this is addressed for CR. 103588 7 rubys 2014-04-08 23:59:43 +0000 It was noted that at the F2F that this feature is at risk for 5.0. 125897 8 travil 2016-04-18 23:04:39 +0000 HTML5.1 Bugzilla Bug Triage: Works for me Double-checked, and the health warning is still there. If there is follow-up needed, let's get a new issue filed. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks! 125898 9 addison 2016-04-18 23:11:32 +0000 Looks good to me. I don't believe we need to re-examine in github issues.