Closed Bug 870296 Opened 11 years ago Closed 7 years ago

Handle RSS/Atom feeds in some way

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sync-1, Unassigned)

Details

(Keywords: feature, Whiteboard: IOT, Poland, Buri)

Attachments

(1 file)

AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.094 Firefox os v1.0.1 Mozilla build ID:20130502070201 +++ This bug was initially created as a clone of Bug #451445 +++ DEFECT DESCRIPTION: [DT][Browser]Device is unable to render RSS feeds properly REPRODUCING PROCEDURES: 1.go to www.engadget.com and click on RSS feed icon to subscribe). 2.the RSS feed is displayed in plain XML source code instead of being rendered properly---KO EXPECTED BEHAVIOUR: Browser provides a mechanism to subscribe to RSS feeds and view them accordingly. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT:Customers can neither subscribe to RSS feeds nor even view them properly. REPRODUCING RATE:5/5 For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #451445 description ++++++++++
Clone from brother
Clone from brother
blocking-b2g: --- → tef?
There is no "proper" way to view RSS feeds, they are just data. Firefox for Android and Chrome for Android behave in the same way. We could explore adding a rendered view of RSS feeds for Firefox OS in Gecko, or some kind of "subscribe" web activity to subscribe to RSS feeds triggered for a particular MIME type, but they would be new features.
Keywords: feature
This should not block 1.0.1
Whiteboard: [tef-triage]
Whiteboard: [tef-triage] → [tef-triage], IOT, Poland, Buri
Agreed - way OOS for v1.0.1
blocking-b2g: tef? → -
Whiteboard: [tef-triage], IOT, Poland, Buri → IOT, Poland, Buri, c=
User story: As a user, when I click on an RSS/Atom feed I would like to see a rendered view of that feed with an option to subscribe to it Similar to what you see in desktop Firefox. The "subscribe" button could fire a web activity.
Component: Gaia::Browser → General
Summary: [Buri][Shira-49056][Browser]Device is unable to render RSS feeds properly → Rendered RSS view
Whiteboard: IOT, Poland, Buri, c= → IOT, Poland, Buri
(In reply to Ben Francis [:benfrancis] from comment #6) > User story: As a user, when I click on an RSS/Atom feed I would like to see > a rendered view of that feed with an option to subscribe to it > > Similar to what you see in desktop Firefox. > > The "subscribe" button could fire a web activity. Ben, I would be interested to know how this is handled by Android. Is there a specific Intent for that or is it a simple "view" Intent on a RSS feed?
Flags: needinfo?(bfrancis)
(In reply to Mounir Lamouri (:mounir) from comment #7) > Ben, I would be interested to know how this is handled by Android. Is there > a specific Intent for that or is it a simple "view" Intent on a RSS feed? Neither Chrome or Firefox on Android have a rendered RSS view with a subscribe button as far as I can tell, but this StackOverflow post[1] seems to indicate that Google Reader and Google Listen use(d) a VIEW intent to open the RSS feed. I'm not sure how this intent gets fired, perhaps the browser fires it silently when you visit a file with one of the matching MIME types. So yes, perhaps a VIEW activity would be more appropriate. http://stackoverflow.com/questions/4901662/how-to-open-my-android-app-when-rss-link-is-opened-in-browser
Flags: needinfo?(bfrancis)
Actually thinking about it, that sounds like a better solution than building the rendered view with a button into Gecko. Fire a view activity which can be consumed by an RSS reader app. That might make this a duplicate of bug 830203 depending on what the behaviour there is defined to be.
Summary: Rendered RSS view → Handle RSS/Atom feeds in some way
we need fix it on v1.1 thanks.
As required by Shira, this should be supported in V1.1 I mark it as leo?
blocking-b2g: - → leo?
(In reply to Amelie Kong from comment #11) > As required by Shira, this should be supported in V1.1 > I mark it as leo? It's too late to take this into 1.1 at this point. We cannot take any features into scope this late in the game.
Triage - leo-'ing as a feature request. Bumping to koi? for attention.
blocking-b2g: leo? → koi?
ni? Karen for consideration
Flags: needinfo?(krudnitski)
Why is this required for 1.2? It wasn't scoped out as a must-have feature and wasn't highlighted on my radar either (when coming into 1.2 half-way through).
Flags: needinfo?(krudnitski) → needinfo?(jcheng)
it's for you to take this bug into your backlog and prioritize it as your team sees fit :)
Flags: needinfo?(jcheng)
Considering I have no compelling requirement to prioritize into the 1.3 feature set, this is something that can be considered for 1.4 (and I have added this item to my list for consideration in that timeframe).
per comment 17 moved to 1.3.
blocking-b2g: koi? → 1.3?
Based on the recent comments setting the 1.3? flag here as a place-holder
Note: to set correct expectations, it is not a priority for 1.3 so will be considered for 1.4.
This isn't happening anytime soon for any target release, so I'm clearing the nom.
blocking-b2g: 1.3? → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: