| Specific features |
References |
|---|
- Support w32 Group Policies
- Allowed extensions
- Basic customizations (eg. company homepage)
- Requires that controls become disabled if overridden by policy. Use the normal Windows UI for editing the policy itself. See bug 267888.
- This should be done in such a way that it is easy to use other management platforms (not just win32/group policies), ie make a cross-platform backend, and a group policy front end. This way other management software (gconf, kcontrol etc.) could be used without duplicating too much code. Perhaps even have a simple flat file (xml etc) front end that works on all platforms.
|
n/a
|
- MSI Installer
- MSI installation package for corporate deployment
|
Frontmotion MSI packages
|
- Better automatic proxy configuration
- Allow async (or in another thread) DNS resolution in proxy.pac so that isInNet doesn't lock ALL browser in a slow DNS query (see bug #208287)
- Automatically discover proxy turn on by default (check if there is a wpad.dat in the install, turn on if true ?)
|
n/a
|
- Updating
- Implement a -update commandline switch which starts Firefox in an automated update mode (core+extensions). Further user interaction shouldn't be necessary
|
n/a
|
- Single Binary File Repositry
- Allow software and theme/extension updates to be stored on a local network. When a new download is required, Firefox can check this location to see if the file has already been downloaded by another user on the network. This would save corporate and Mozilla bandwidth.
|
n/a
|
- Restriction of interface
- Allow setting of restrictions on menus, downloads, changing of home page etc. This could allow Firefox to be on par with IE functionality in Active Directory, and be used in environments that require some user restrictions. This must be manageable either through group policy or a local control panel that is password protected.
|
n/a
|
| General tasks |
|---|
|
n/a
|
n/a
|