The current format of the `version` field in the manifest is very complicated. Let's encourage the use of a simpler versioning format (see below) by adding format + onError:warn to the schemas. Simple format: `<number>.<number>.<number>.<number>` where `<number>` is 0 to 65535 (16 bit unsigned integer)
Bug 1793925 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The current format of the `version` field in the manifest can be very complicated. Let's encourage the use of a simpler versioning format (see below) by adding format + onError:warn to the schemas. Simple format: `<number>.<number>.<number>.<number>` where `<number>` is 0 to 65535 (16 bit unsigned integer)
The current format of the `version` field in the manifest can be very complicated. Let's encourage the use of a simpler versioning format (see below) by adding format + onError:warn to the schemas. Firefox will only emit warnings. We might enforce a simpler format later but that will be done in the linter, not in Firefox. Simple format: `<number>.<number>.<number>.<number>` where `<number>` is 0 to 65535 (16 bit unsigned integer)
The current format of the `version` field in the manifest can be very complicated. Let's encourage the use of a simpler versioning format (see below) by adding format + onError:warn to the schemas. Firefox will only emit warnings. We might enforce a simpler format later but that will be done in the linter, not in Firefox. Simple format: `<number>.<number>.<number>.<number>` where `<number>` is ~~0 to 65535 (16 bit unsigned integer)~~ 0 to 999999999 (an integer with up to 9 digits) and no leading zeros.