This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7258 - Should state that a new Date object is returned each time the date/time/timezone attributes are accessed if the intention is for them not to be reflecting datetime="" or the element content.
Summary: Should state that a new Date object is returned each time the date/time/timez...
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://whatwg.org/specs/web-apps/curr...
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2009-08-11 07:42 UTC by contributor
Modified: 2010-10-04 13:58 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2009-08-11 07:42:17 UTC 
Section: http://whatwg.org/specs/web-apps/current-work/#the-time-element

Comment:
Should state that a new Date object is returned each time the date/time/timezone attributes are accessed if the intention is for them not to be reflecting datetime="" or the element content.

Posted from: 203.217.71.141
Comment 1 Ian 'Hixie' Hickson 2009-09-09 09:49:33 UTC 
It's a single dateTime attribute now, but modulo that, fixed.
Comment 2 Maciej Stachowiak 2010-03-14 14:48:57 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
  http://dev.w3.org/html5/decision-policy/decision-policy.html

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.