Back to index
|Syncs a container's fields with its convenience attributes. |
|Uses description, subtitle, summary, content and extensions to generate a summary. |
|The date the entry was published, in RFC822 form. |
|Uses atom:content and content:encoded to provide a 'full text' view of an entry. |
|Enclosures are podcasts, photocasts, etc. |
|Enclosures, etc. |
|Many feeds contain an ID distinct from their URI, and entries have standard fields for this in all major formats. |
|The fields found in the document. |
|Sometimes there's no title, or the title contains markup, so take care in decoding the attribute. |
|Returns the primary link for the feed or entry. |
|Returns all links for a feed or entry. |
|Returns the categories found in a feed or entry. |
|The rights or license associated with a feed or entry. |
|A list of nsIFeedPersons that authored the feed. |
|A list of nsIFeedPersons that contributed to the feed. |
|The date the feed was updated, in RFC822 form. |
|The attributes found on the element. |
|The baseURI for the Entry or Feed. |
An nsIFeedEntry represents an Atom or RSS entry/item.
Summary and/or full-text content may be available, but callers will have to check both.
Syncs a container's fields with its convenience attributes.
The fields found in the document.
Common Atom and RSS fields are normalized. This includes some namespaced extensions such as dc:subject and content:encoded. Consumers can avoid normalization by checking the feed type and accessing specific fields.
Common namespaces are accessed using prefixes, like get("dc:subject");. See nsIFeedResult::registerExtensionPrefix.