8 years ago
4 months ago


(Reporter: mak, Unassigned)


(Blocks 1 bug)

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)



(1 attachment)

Posted patch wipSplinter Review
This thing (toolkit/components/feeds) has something like 11 idl files for a couple components, and we don't use most of them. I suspects also addons don't need all of these.
I made this patch some time ago, iirc it passes 199 tests out of 200, so there is probably still something to fix and it's likely bitrotted, but attaching to avoid losing it.
Blocks: deCOM
Philor, do you want to take this bug by chance?

My patch is mostly a cleanup (and likely bitrotted by recent changes to date functions, but that should be easy to fix), but a bunch of interfaces are currently unused looking at addons mxr:

Ideally, this should just be a simple js module, but there are lots of addons relying on these nasty interfaces, maybe we could do the module and provide a deprecated interfaces shim component, that just wraps it. The product would just use the module while add-ons may keep using the component for a while.
I must also say the feedprocessor is tremendously slow and hangs the ui thread, so it's possible we are using the wrong blocking interfaces to fetch and parse, this may be a bug apart though.
Sorry, but based on my experience so far with the modern world, where all interfaces are unfrozen by reviewers, but then flash-refrozen by drivers ordering you to back out immediately, I'll probably never again touch anything that could be remotely construed as an API.
Honestly, you should not care about people trying to slowdown us, for sure not taking personal effort in replying them. They want us to go slower, we just can't, look at the evolving browsers' market. Btw, in this case we'd keep the interfaces, through a simple shim redirecting to the module, for a couple releases.
Btw, I can understand your frustration.
Blocks: 725964
Is this bug still relevant?
yes, we still have a bunch of pointless interfaces in feeds.

Comment 6

11 months ago
Per policy at If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Last Resolved: 11 months ago
Resolution: --- → INACTIVE


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