www.bokaldo.com - design is broken

[webcompat-bot]

URL: https://www.bokaldo.com/contact/

Browser / Version: Firefox 108.0
Operating System: FreeBSD
Tested Another Browser: Yes Opera

Problem type: Design is broken
Description: Images not loaded
Steps to Reproduce:
Image on top not showing up, but on another browser everything works.

img1 - https://i.postimg.cc/ryWBXLLr/firefox.png
img2 - https://i.postimg.cc/B63xjDXs/opera.png

Browser Configuration

• gfx.webrender.all: true
• gfx.webrender.blob-images: true
• gfx.webrender.enabled: false
• image.mem.shared: true
• buildID: 20230105190654
• channel: aurora
• hasTouchScreen: false
• mixed active content blocked: false
• mixed passive content blocked: false
• tracking content blocked: false

View console log messages

From webcompat.com with ❤️

[softvision-raul-bucata]

OpenBSD is not a target that's supported by Mozilla. As such, that crash needs to be reported to whoever maintains the OpenBSD port. We are sorry for the inconvenience, but there is nothing we can do here on our part.

[qa_05/2023]

[denschub]

This reproduces for me on macOS. The header has a background-image: url(https://www.bokaldo.com/imgldn/contact.avif), but Firefox is refusing to load that.

Looking at ffprobe, this is actually an AVIF image sequence, not jut a static AVIF image:

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'contact.avif':
  Metadata:
    major_brand     : avif
    minor_version   : 0
    compatible_brands: avifmif1miafMA1B
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0[0x1]: Video: av1 (Main), yuv420p(pc, smpte170m/unknown/unknown), 1500x1000 [SAR 1:1 DAR 3:2], 1 fps, 1 tbr, 1 tbn

So this is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1686338

[tnikkel]

Hmm, what makes you think its an animated avif? I get pretty much the same output from ffprobe on a non-animated avif. And if I use nightly with the animated avif pref turned on the file still does not display (and the file appears still when I load it in chrome).

[tnikkel]

I get this failing to parse with "mp4parse_avif_new status: 15", which is MP4PARSE_STATUS_CHECK_PARSER_STATE_ERR aka Status::CheckParserStateErr. Please file a new bug about this.

[denschub]

Oh huh you're right. I got confused by ffmpeg failing to identify the color model in the non-aminated example I used to compare (where it just showed none).

Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1814075

[Zaggy1024]

For the context of anyone coming across this bug, it appears that the file has garbage data at the end that causes a parsing error:

https://bugzilla.mozilla.org/show_bug.cgi?id=1814075#c2