Summary: | Some valid JP2s are failing to decode | ||
---|---|---|---|
Product: | WebKit | Reporter: | Eric Portis <e> |
Component: | Images | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | karlcow, sabouhallawa, simon.fraser, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 16 | ||
Hardware: | Unspecified | ||
OS: | All |
Description
Eric Portis
2022-11-22 16:13:12 PST
I should also note it seems extremely related to https://bugs.webkit.org/show_bug.cgi?id=219977 & FB9671920, which seems to have been recently fully fixed? Just as with that bug, the issue only seems to affect very "simple" images (for example, but not limited to: single-color images). I will update both this and the feedback as I find more examples of failing JP2s. The JP2s seem to fail consistently when they are over a certain size. Setting the "width" parameter in this URL to anything over 3248 generates a failing image: https://assets.meinauto.de/image/upload/f_jp2,w_3250/v1668594966/website/pics/landingpages/black-deals/red Anything under 3248 succeeds: https://assets.meinauto.de/image/upload/f_jp2,w_325/v1668594966/website/pics/landingpages/black-deals/red Changing the color space to CMYK seems to change this boundary to 3260 https://assets.meinauto.de/image/upload/f_jp2,w_3260,cs_cmyk/website/pics/landingpages/black-deals/red (WORKS) https://assets.meinauto.de/image/upload/f_jp2,w_3261,cs_cmyk/website/pics/landingpages/black-deals/red (FAILS) > I have cross-filed this as FB11815925 rdar://102613994 Karl: not sure how this is BrowserCompat? failing to decode JPEG2000 arguably just makes us behave the same as everyone else (who don't support JPEG2000); I guess it could lead to site compat problems with usage of content negotiation or similar, as we'll get served a JPEG2000 image and then fail to render it. Hmm Indeed. Sorry about that. |