Closed Bug 779370 Opened 13 years ago Closed 13 years ago

Use standard resource mapping for services JS

Categories

(Cloud Services :: Firefox: Common, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: gps, Assigned: jimm)

Details

I think the resource://services-<foo> is silly. Everything else uses resource://gre/modules/ or at least something like resource://services/sync (no hyphen). Basically, JS modules in services/ are a one-off compared to everything else and I think that is wrong. philikon says mconnor may know the reason here. I suspect it has something to do with Sync's history as an add-on. But, since we aren't an add-on any more, I don't see a reason for us to not adopt the road more traveled. Switching could be backwards compatible (we could change the existing resource:// aliases to point to the new locations).
mconnor has no problem with changing this to become sane. The original reason was all about Sync being an add-on and we are no longer bound to this requirement.
Blocks: 815320
Assignee: nobody → jmathies
No longer blocks: 815320
Considering we're going to move half services in gre and keep the other half in app, and considering how many mistakes have been made in the past with resource:/// vs. resource://gre/, I think it's actually much better to keep using the resource://services-* aliases, which avoid any kind of ambiguity.
Works for me!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.