CCK:Firefox
CCK Customization for Firefox
- Company name at the end in the titlebar
- Company identifier added to the user agent
- Change Activity Indicator URL
- Change Activity Indicator tooltip
- Change Activity indicator image
- Add one item to the help menu
- New default homepage
- New default start page (first page before homepage)
- Add items to the personal toolbar (including live bookmarks)
- Remove items from the personal toolbar
- Add a single custom bookmark or a custom folder with up to five items (including live bookmarks)
- Remove bookmarks
- Default proxy configuration
- Add additional search engine
- Change update URL
- Change plugin URL
- Add sites to default "don't block popups" list
- Add sites to default "allow to install software" list
- Customize the toolbar (add/remove)
- Add/Remove/Hide menubar items, context menu items
- Disable downloads
- Disable about:config
- add about:plugins back?
- Locked preference panel to set all this?
- Disable the ability to install additional extension?
--Nirwana 08:52, 27 Apr 2005 (PDT) If the CCK were an extension, this could easily be disabled or uninstalled. IMHO, this is not the best option for companies/ISPs wishing to customize Firefox. They'd like to be really sure that what they customize cannot easily be undone. Mostly they customize the browser for a reason and do not like it when this reason can easily be circumvented.
--Gavin Sharp 09:53, 27 Apr 2005 (PDT) So why not add the ability to prevent disabling and uninstallation? People seem to be quick to reject the extension system because of minor issues like these, but these issues seem much easier to fix than rearchitecturing the installer.
--MikeKaply 09:03, 27 Apr 2005 (PDT) Very true, and I'm not sure necessarily at this point an extension is the right thing. I'll remove the extension comment at the top and just focus on collecting the types of things people will want to modify.
--fantasai The CCK should guide people through branding issues based on what customizations they have made.
--DERoss I would like to see Firefox on the PCs in my local public library. Actually, it would have to be installed in 12 libraries in my county's system. For this to happen, customization beyond the proposed list is mandatory.
(1) When the browser is started, a "terms of use" window appears. The user must select the "Accept" button to continue. (This might be via a non-browser system capability.)
(2) For accessibility, users must be allowed to change preferences for fonts and colors. However, whenever the browser is terminated, those changes must be "forgotten". Other preferences (e.g., popup permissions) might also be changed but must also be "forgotten". However, administrator-set preferences would have to persist.
(3) All cookies received during a user's session would have to be treated as session-only cookies.
(4) All history and cache must be erased at termination.
(5) File downloads would have to be blocked. Any file would have to open in the browser. Allowed file-types would be restricted per an administrator-set whitelist. (Of course, the administrator would have to set the whitelist to correspond to installed plugins, which the users would not be allowed to download and install.)
(6) Allow administrator-set bookmarks (any number).
This is only a partial list of customization capabilities for CCK if it is to be used to make Firefox suitable for installation in public libraries.