The array size needs to be updated, but otherwise looks good to me

The array size needs to be updated, but otherwise looks good to me

You are right my bad I will update it

I ran the test locally and the failing test do not seem related to my commit but I could be wrong?

Thanks!

These bytes before ftyp are the size of the ftyp chunk. This chunk contains a variable-length list, so it could have any size.

Instead of collecting implementation-specific lengths, can the length be allowed to be any bytes? The two most significant bytes could be required to be 0, since the chunk is unlikely to ever exceed 64K.

These bytes before ftyp are the size of the ftyp chunk. This chunk contains a variable-length list, so it could have any size.

Instead of collecting implementation-specific lengths, can the length be allowed to be any bytes? The two most significant bytes could be required to be 0, since the chunk is unlikely to ever exceed 64K.

I wondered it myself but could not see how to do it with the current implementation

A simple solution could be to add a start offset to the table of magic strings, and skip 4 bytes in AVIFs case.

If we included a mask of bytes to ignore, we could also have an actual fix for #660