Closed Bug 521769 Opened 15 years ago Closed 15 years ago

correctly interprete rss-links

Categories

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

Product:
Firefox Graveyard
Component:
RSS Discovery and Preview
Platform:
Other
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 448390

People

(Reporter: estellnb, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE
Build Identifier: MozillaFirefox-3.5.3-1.3

  If I browse with Konqueror an rss-icon appears on the bottom-right of the browser if the opened site support rss: I would wish this for Firefox as well.
<head> ...
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://mirror.elstel.com/elstel.rss" />
</head>

  The rss-feed should also be found if hidden in a sub-frame. As I do not pay for an own server for my site (www.elstel.com) I need to use URL-Framing which will hide my basic site content and all html-headers in an HTML-Frame (It would be groovy if Firefox could even draw icons from an only sub-frame <link rel=icon/shortcut icon>).

  Of course explicit rss-links in the body should be supported as well:
<a href="http://mirror.elstel.com/elstel.rss" type="application/rss+xml" title="elstel - site updates">

  It should be possible to select the default rss-reader as it should be possible to select other standard components like mailing app. and file management app.. For KDE-users it would be handy if the default apps. from systemssettings/kcontrol or in case of the rss-reader the standard file association of mime-type text-rss would be overtaken.


  

As I do not pay for an own server I have to use URL-Framing

Reproducible: Always
see bug 448390 comment 1
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
May we keep this one as request to select the default rss-reader and other components?
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.