Closed Bug 357539 Opened 18 years ago Closed 18 years ago

Feed parser does not recognize lastBuildDate field

Categories

(Firefox Graveyard :: RSS Discovery and Preview, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 3 alpha1

People

(Reporter: ancestor.ak, Assigned: sayrer)

Details

(Keywords: fixed1.8.1.2, Whiteboard: [need testcase])

Attachments

(1 file)

When generating |updated| property of nsIFeedContainer, the parser doesn't recognize <lastBuildDate/>. This field is a common way of specifying when a feed was updated.
silly omission on my part. RSS2 has so many elements!

patch and test file coming soon
Attachment #245113 - Flags: review?(mano)
Comment on attachment 245113 [details] [diff] [review]
add it to our list of the places dates come from

r=mano
Attachment #245113 - Flags: review?(mano) → review+
Checking in src/FeedProcessor.js;
/cvsroot/mozilla/toolkit/components/feeds/src/FeedProcessor.js,v  <--  FeedProcessor.js
new revision: 1.20; previous revision: 1.19
done
RCS file: /cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate.xml,v
done
Checking in test/xml/rss2/feed_updated_lastBuildDate.xml;
/cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate.xml,v  <--  feed_updated_lastBuildDate.xml
initial revision: 1.1
done
RCS file: /cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate_priority.xml,v
done
Checking in test/xml/rss2/feed_updated_lastBuildDate_priority.xml;
/cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate_priority.xml,v  <--  feed_updated_lastBuildDate_priority.xml
initial revision: 1.1
done
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3 alpha1
Flags: in-testsuite+
Comment on attachment 245113 [details] [diff] [review]
add it to our list of the places dates come from

drivers: this a pain for API users. automated test coverage is good.
Attachment #245113 - Flags: approval1.8.1.2?
Comment on attachment 245113 [details] [diff] [review]
add it to our list of the places dates come from

Approved for 1.8 branch, a=jay for drivers.
Attachment #245113 - Flags: approval1.8.1.2? → approval1.8.1.2+
Checking in FeedProcessor.js;
/cvsroot/mozilla/toolkit/components/feeds/src/FeedProcessor.js,v  <--  FeedProcessor.js
new revision: 1.1.2.16; previous revision: 1.1.2.15
done
Checking in xml/rss2/feed_updated_lastBuildDate.xml;
/cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate.xml,v  <--  feed_updated_lastBuildDate.xml
new revision: 1.1.2.1; previous revision: 1.1
done
Checking in xml/rss2/feed_updated_lastBuildDate_priority.xml;
/cvsroot/mozilla/toolkit/components/feeds/test/xml/rss2/feed_updated_lastBuildDate_priority.xml,v  <--  feed_updated_lastBuildDate_priority.xml
new revision: 1.1.2.1; previous revision: 1.1
done
~/bonecho/mozilla/toolkit/components/fee
Keywords: fixed1.8.1.2
hi sayre, can you add testcases to this bug so QA can verify?  or if its not a simple verification for us, would you be able to verify it on the 1.8 branch?  You'll have to change the keywords from "fixed1.8.1.2" to "verified1.8.1.2". Thanks!
Whiteboard: [need testcase]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: