238263 - global pref file renames aren't consistant [all.js browser-pref.js]

Status: RESOLVED INVALID

(Core :: Preferences: Backend, defect)

Description

[Pete Boyd]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

the global preference files appear to have been renamed in the Mozilla 1.7
development time frame. editor.js has become composer.js, all.js has become
browser-prefs.js and there's inspector.js and mailnews.js

consistancy is a feature in itself

it seems pointless and confusing to be changing the names at this stage and
introducing an inconsistancy - surely browser-prefs.js should be browser.js?

Reproducible: Always
Steps to Reproduce:

Comment 1

[Nickolay_Ponomarev]

In current mozilla builds there is greprefs/all.js which is supposed to be
shared between all gecko apps and defaults/pref/*.js which is app-specific.
Sounds consistent enough to me.

You're right though, browser-prefs isn't a very good name, but browser.js would
be quite confusing imo, as there is such file in chrome already.

suggesting wontfix.

Comment 2

[Pete Boyd]

The only inconsistancy I was on about was the added '-prefs' on just the one
file, when all such files are preferences. But, as you say, if there's already a
browser.js for the chrome it makes it unlikely we're going to have a consistant
file naming convention here

Comment 3

[Nickolay_Ponomarev]

it can be called browser.js (technically), but thats'd be a little confusing imo.

Is anything else being tracked in this bug? If not, could you resolve this as
invalid or wfm?

Comment 4

[Serge Gautherie (:sgautherie)]

(Filter "spam" on 'prefs-nobody-20080612'.)

Comment 5

[Nicholas Nethercote [inactive]]

The filenames have been this way for a long time now, so this bug no longer serves a useful purpose.