Confirmed users
66
edits
CCK:Firefox: Difference between revisions
Customizing Firefox for Public Libraries
No edit summary |
(Customizing Firefox for Public Libraries) |
||
| Line 39: | Line 39: | ||
--[[User:fantasai|fantasai]] | --[[User:fantasai|fantasai]] | ||
The CCK should guide people through branding issues based on what customizations they have made. | The CCK should guide people through branding issues based on what customizations they have made. | ||
--[[User:DERoss|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. | |||