This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
This bug was cloned to create bug 17855 as part of operation convergence.
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.
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
Diff looks good to me, but I don't see the addition of the reference to w3.org/TR/timezone? Is that intentional?
Argh. I see it addressed in bug 16957
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.
It was noted that at the F2F that this feature is at risk for 5.0.
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!
Looks good to me. I don't believe we need to re-examine in github issues.