RSS Discovery not working with frames on page.

RESOLVED INACTIVE

Status

--
minor
RESOLVED INACTIVE
11 years ago
28 days ago

People

(Reporter: shadow.garret, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16

<frameset>
 <frame src="page.htm" name="someframe" />
</frameset>

RSS discovery not looking for rss link at head of "page.htm"

Reproducible: Always

Steps to Reproduce:
1. Make or find a page with frames in it.
2. If framed page add link to rss.
Actual Results:  
RSS Discovery just don't see rss link in head of framed page.

Expected Results:  
Should show discovered rss on page.
Maybe should tell that rss is inside a frame.

For security reason will be better to cap rss discovery in frames only for same domain.
Amusingly enough, at first (bug 274915) we unintentionally didn't discover them in frames, which people didn't like, then (bug 305472) we unintentionally did discover them in frames, which people didn't like, now (this bug) we unintentionally don't discover them in frames, which people don't like. 
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk

Updated

9 years ago
Duplicate of this bug: 521769
  I don`t think there is real objection to showing rss-feeds from sub-frames as long as we annotate it with the sub-frame uri if there should be multiple sub-frames.
  On the other hand if we do only have one sub-frame the site is using URL-Framing instead of an DNS-redirect: no popup menu needs to be shown; rss and ico <link rel=icon/shortcut icon> should be drawn from the only sub-frame.

Comment 4

8 months ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → INACTIVE

Updated

28 days ago
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.