| Summary: | www-client/chromium should no longer block libpng[apng] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael <voron1> |
| Component: | Current packages | Assignee: | Chromium Project <chromium> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | kangie, mail |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Michael
2022-09-16 10:33:56 UTC
Is there some will towards this? I changed the dependency libpng:=[-apng(-)] to libpng:= in latest chromium-120.0.6099.109.ebuild and it works fine (media-libs/libpng-1.6.40-r1), no flickering, only some warnings printed repeatedly when visiting pages with APNGs on them (they render fine, though): libpng warning: Number of actual frames fewer than expected libpng warning: size in first frame's fcTL must match the size in IHDR libpng warning: Skipped (ignored) a chunk between APNG chunks libpng warning: Number of actual frames fewer than expected There was a suggestion to resolve the warnings in the original thread: https://bugs.gentoo.org/824018#c55 The chromium bugtracker suggests that the warnings are now gone on Debian: https://bugs.chromium.org/p/chromium/issues/detail?id=1142228 On balance, I don't think it's worth it when we have USE=-system-libpng to enable the use of the bundled libpng: - Chromium doesn't use this apng impl anyway - It's still not in the spec (though v3 looks promising) - It adds maintenance overhead - We'd still need to test and resolve the warnings Toggling the USE will enable users to build libpng[apng] if that's what they want to do for other purposes. |
