Last updated: Jan 27, 1999
Table of ContentsSummary
The JS file is created after all the values have been input by the user. The two different kinds of representation in the JS file are
- Defaultpref - these are user prefs that the ISP can lock by using the defaultpref option and then hashing it to prevent tampering with the files
- Config - These are the configuration items that cannot be edited thru any UI for the browser and can only be changed by including it in the config.js file they include - User agent strings, Animated logo, guide button, help menu and other additional customizations.
- There can be a duplicate pref - in which case the wizard notifies the user about it andt here could be wrong values input into them and there is no current solution for that.
- If they user decides to input a totally new pref in the file it is being done at their own risk!.
The current testing model given to the QA is as follows
1- A name value pair file for inputing the values into the array
2- A file for specifying the defaultpref and config preferences.(sample file will be provided for both)
For the testing of the final JS file - there needs to be appended any other preferences file of similar format to either the one produced by the CE or any common communicator pref file.(test sample provided )