Status

defect
P3
normal
RESOLVED WORKSFORME
10 years ago
5 months ago

People

(Reporter: dietrich, Unassigned)

Tracking

(Blocks 2 bugs, {perf})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ts])

Reporter

Description

10 years ago
nsIFeedWriter and impl have only a single caller and use-case: displaying the feed preview.

we should investigate if we can either bundle it directly with the content page, or convert it to a js module.

for background, see bug 336903.
Reporter

Updated

10 years ago
Keywords: perf
Whiteboard: [ts]
Bug 499123 seems to be doing something very much along these lines. I think that will help.
Depends on: 499123
Reporter

Updated

10 years ago
Priority: -- → P3
Blocks: deCOM
Reporter

Updated

9 years ago
Blocks: 447581
Can I just remove BrowserFeedWriter and include the FeedWriter.js into subscribe.js?
This will allow us to remove the nsIFeedWriter interface.
(In reply to Dietrich Ayala from comment #0)
> nsIFeedWriter and impl have only a single caller and use-case: displaying
> the feed preview.
> 
> we should investigate if we can either bundle it directly with the content
> page, or convert it to a js module.
> 
> for background, see bug 336903.
Surely the point of bug 336903 was that the component was created to make the feed preview page safe, by not having it run as chrome? Currently only an XPCOM component can do this.
So can't we deCOMtaminate it?
Reporter

Comment 5

8 years ago
(In reply to neil@parkwaycc.co.uk from comment #3)
> Surely the point of bug 336903 was that the component was created to make
> the feed preview page safe, by not having it run as chrome? Currently only
> an XPCOM component can do this.

Yeah, the idea is to explore other ways of exposing the data to content. We now have framescripts, as well as trivial means of exposing JS APIs to web content. I haven't dug around the feed preview page enough to know what exactly the danger points are, or whether these things are feasible.
nsIFeedWriter seems to not exist any more.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME

Updated

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