changeset 265:196c26539e2c

don't display a timestamp in the stream view, since we don't order by it, and it's confusing
author Myk Melez <myk@mozilla.org>
date Wed, 27 Aug 2008 14:04:33 -0700
parents e294475faeb2
children 3f275f19f5f2
files content/stream.js
diffstat 1 files changed, 12 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/content/stream.js	Mon Aug 25 18:49:46 2008 -0700
+++ b/content/stream.js	Wed Aug 27 14:04:33 2008 -0700
@@ -310,14 +310,18 @@
       }
 
       // Timestamp
-      let lastUpdated = SnowlUtils._formatDate(new Date(message.timestamp));
-      if (lastUpdated) {
-        let timestamp = this._document.createElementNS(XUL_NS, "description");
-        timestamp.className = "timestamp";
-        timestamp.setAttribute("crop", "end");
-        timestamp.setAttribute("value", lastUpdated);
-        centerColumn.appendChild(timestamp);
-      }
+      // Commented out because the timestamp isn't that useful when we order
+      // by time received.  Instead, we're going to group by time period
+      // received (this morning, yesterday, last week, etc.) to give users
+      // useful chronographic info.
+      //let lastUpdated = SnowlUtils._formatDate(new Date(message.timestamp));
+      //if (lastUpdated) {
+      //  let timestamp = this._document.createElementNS(XUL_NS, "description");
+      //  timestamp.className = "timestamp";
+      //  timestamp.setAttribute("crop", "end");
+      //  timestamp.setAttribute("value", lastUpdated);
+      //  centerColumn.appendChild(timestamp);
+      //}
 
       // content (title or short message)
       let body = this._document.createElementNS(XUL_NS, "description");