Per the published standard, this file is invalid because it provides multiple `ColourInformationBox` (`colr`) entries (one ICC profile, and one NCLX) where the HEIF specification [ISO/IEC 23008-12:2017](https://www.iso.org/standard/66067.html) § 6.5.5.1 requires > Quantity (per item): At most one After inquiring with the editor, I was able to obtain an unpublished draft amendment (registered as [DAmd 2](https://www.iso.org/standard/81688.html), but not publicly available, even for purchase) which changes that to > Quantity (per item): At most one for a given value of `colour_type` This is what libavif (the writer responsible for these images) is based on, and despite regular testing against libavif's output, I must not have done a comprehensive retest subsequent to implementing the `colr` box parsing in mp4parse rust. I find it very odd that we haven't run into this previously since the change landed over a month ago in bug 1723247, but here we are. I'm currently discussing options with the release manager for 92, but I think it's likely we will disable AVIF by default for now and not ship in 92. See 1682995 for details.
Bug 1729071 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Per the published standard, this file is invalid because it provides multiple `ColourInformationBox` (`colr`) entries (one ICC profile, and one NCLX) where the HEIF specification [ISO/IEC 23008-12:2017](https://www.iso.org/standard/66067.html) § 6.5.5.1 requires > Quantity (per item): At most one After inquiring with the editor, I was able to obtain an unpublished revision (registered as [ISO/IEC DIS 23008-12](https://www.iso.org/standard/83650.html), but not publicly available, even for purchase) which changes that to > Quantity (per item): At most one for a given value of `colour_type` This is what libavif (the writer responsible for these images) is based on, and despite regular testing against libavif's output, I must not have done a comprehensive retest subsequent to implementing the `colr` box parsing in mp4parse rust. I find it very odd that we haven't run into this previously since the change landed over a month ago in bug 1723247, but here we are. I'm currently discussing options with the release manager for 92, but I think it's likely we will disable AVIF by default for now and not ship in 92. See 1682995 for details.