Fix default values for settings not being used in the browser extension
The logic for skipping host page configuration of settings that are ignored by the browser extension did not take into account any default values configured via the `defaultValue` property. Also fix and add several related tests: - Correct the test that checks behavior when `defaultValue` is not set to use `undefined` rather than `null` to indicate a missing `defaultValue`. - Add test case for when a default value is overridden. - Add test case for default values in browser extensions.
Showing
Please register or sign in to comment