If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Move browser/components/feeds to toolkit

NEW
Unassigned

Status

()

Toolkit
XUL Widgets
11 years ago
5 years ago

People

(Reporter: Nick Kreeger, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9.1 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
In order for embedded applications (I.E. Camino) to take advantage of Firefox's feed interfaces, we need the existing code in browser/components/feeds to move to a better global location. 

According to sayrer via IRC conversation, this is a possibility.

Comment 1

11 years ago
Yah, but FeedWriter.js and whatever presentation files are found in browser/components/feeds/content/ should probably stay in browser/. You guys will probably want to write your own stuff there anyway.
(Reporter)

Comment 2

11 years ago
Yeah, I think we were concerned with the idl and implementation files.
Blocks: 355748

Updated

11 years ago
Blocks: 380415
OS: Mac OS X → All
Hardware: Macintosh → All
Version: 1.8 Branch → Trunk

Updated

11 years ago
Assignee: nobody → dmose

Comment 3

11 years ago
This is possibly something we'd like to have for getting a feed reader in SeaMonkey - not sure if it's a real blocker for that one but at least it's connected and of interest to us...
Blocks: 255834

Updated

11 years ago
Blocks: 354800

Updated

11 years ago
Blocks: 383535

Updated

10 years ago
No longer blocks: 380415

Updated

10 years ago
Assignee: dmose → nobody
Songbird would love this too.
Blocks: 357052

Updated

10 years ago
Blocks: 380247
Flags: blocking1.9.1?
No patch, can't block. We could still take this for 1.9.1, but it's not necessary.
Flags: blocking1.9.1? → blocking1.9.1-
Blocks: 458052

Updated

5 years ago
Duplicate of this bug: 380247
You need to log in before you can comment on or make changes to this bug.