| components.conf |
|
545 |
- |
| EnterprisePolicies.sys.mjs |
|
830 |
- |
| EnterprisePoliciesContent.sys.mjs |
|
2021 |
- |
| EnterprisePoliciesParent.sys.mjs |
the EnterprisePoliciesManager |
28150 |
- |
| macOSPoliciesParser.sys.mjs |
|
4559 |
- |
| metrics.yaml |
|
1698 |
- |
| moz.build |
|
1056 |
- |
| nsIEnterprisePolicies.idl |
Checks if a specific feature is allowed by the enterprise policies.
@param feature The feature to check.
@returns A boolean - true if the feature is allowed.
|
3547 |
- |
| PoliciesHelpers.sys.mjs |
Records the operations that failed while a policy was being applied, so that
about:policies can report that policy as only partially applied.
A policy whose operation failed stays in getActivePolicies(): those are the
parameters the administrator asked for, and most of the policy may well have
been applied. What failed is recorded here instead.
|
25227 |
- |
| PolicySchemaValidator.sys.mjs |
This module validates enterprise policy parameters against the policy schema.
Policy data arrives from several sources (policies.json, Windows GPO, macOS
config profiles) in shapes that differ from clean JSON. This module turns it
into validated, ready-to-use data in three stages:
1. NORMALIZE: transform source-specific quirks into standard JSON so the
value can be validated by an off-the-shelf validator. Booleans delivered
as 0/1 integers or as "true"/"false" strings become real booleans; values
delivered as a JSON string (fields marked "contentMediaType":
"application/json") are parsed into objects/arrays. No validity decisions
happen here.
2. VALIDATE: the compliant validator in JsonSchema.sys.mjs checks the
normalized value using only standard JSON Schema keywords (type, format,
pattern, enum, required). Every entry of a list, and every open-ended key
of an object (one matched by patternProperties, e.g. an extension ID in
ExtensionSettings), is validated individually: invalid entries are dropped
(and logged) so one bad entry never discards the whole collection. Any
other bad value fails its policy.
3. HYDRATE: validated "format": "uri" strings are turned into URL objects,
which the policy implementations consume (.href, .hostname, etc.).
The schema itself stays standard JSON Schema, so the same file can drive
other tooling (e.g. the enterprise console). "contentMediaType" is the only
keyword this module keys on beyond standard validation.
|
13497 |
- |
| SitePolicyUtils.sys.mjs |
|
1067 |
- |
| tests |
|
|
- |
| WindowsGPOParser.sys.mjs |
|
4783 |
- |