Closed
Bug 285362
Opened 20 years ago
Closed 17 years ago
RSS 2.0 without item titles doesn't fall back to dc:date
Categories
(Firefox :: Bookmarks & History, defect)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: hhwong, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Live Bookmarks doesn't seem to work with Instapundit's RSS feed. It just gives
me a "Live Bookmark feed failed to load." message. It worked with that RSS
extension I was using before FF 1.0.
Reproducible: Always
Steps to Reproduce:
1. Add Instapundit RSS as a Live Bookmark
2. Access it
3.
Actual Results:
The only output is "Live Bookmark feed failed to load."
Expected Results:
Shown the RSS output.
Using Qute theme.
Comment 1•20 years ago
|
||
Workaround: use http://instapundit.com/index.rdf where we expect to find a
dc:date as a fallback for an empty title.
The problem is that bug 260308 gave us a fallback for feeds with empty titles,
but it only expects dc:date in RSS 1.0 feeds, and in RSS 2.0 it expects either
pubDate or updated, but not the dc:date that the first two or three years of
Movable Type templates used, even in RSS 2.0 (google "funky RSS" for background).
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Instapundit RSS doesn't work with Firefox Live Bookmarks → RSS 2.0 without item titles doesn't fall back to dc:date
Version: unspecified → Trunk
Assignee: vladimir+bm → nobody
Comment 2•19 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
Comment 3•17 years ago
|
||
it's WFM but i suppose the website has updated their feed, so i'd say incomplete actually
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•