- From: Chris Lilley <chris@w3.org>
- Date: Tue, 6 Feb 2024 14:30:10 -0500
- To: "Chris Blume (ProgramMax)" <programmax@gmail.com>
- Cc: public-png@w3.org
- Message-ID: <14239e7d-106b-44f7-9ffa-b276f801737d@w3.org>
On 2024-02-06 12:31, Chris Blume (ProgramMax) wrote: > Right. I only added support for the eXIf chunk when it arrives before > IDAT. > That test uses the eXIf chunk arriving after IDAT (invalid, should be > ignored). Then it uses zTXt to package EXIF data early. Right. I should add one that uses eXIf early as well to be sure that one works. > > Support for EXIF in zTXt should be added. But I wanted to focus on > just the eXIf chunk to resolve the 'at risk' concern. Of course! > > On Tue, Feb 6, 2024 at 10:29 AM Chris Lilley <chris@w3.org> wrote: > > > On 2024-02-06 07:41, Chris Blume (ProgramMax) wrote: >> Hello everyone, >> >> Yesterday, my eXIf patch for Chromium landed >> <https://chromium-review.googlesource.com/c/chromium/src/+/5249880>. >> It takes a while for WPT bots to pick up the latest build. But >> the WPT eXIf test now shows Chromium passing >> <https://wpt.fyi/results/png/exif-chunk.html?label=master&label=experimental&aligned>. > > Excellent. > > Although oddly, this one still fails. Should dig into it more > https://wpt.fyi/results/css/css-images/image-orientation/image-orientation-exif-png.html?label=master&label=experimental&aligned > <https://wpt.fyi/results/css/css-images/image-orientation/image-orientation-exif-png.html?label=master&label=experimental&aligned> > >> >> That makes two browsers. I believe we can remove the 'at risk' >> mark for eXIf. > Yes. PR incoming. > > -- > Chris Lilley > @svgeesus > Technical Director @ W3C > W3C Strategy Team, Core Web Design > W3C Architecture & Technology Team, Core Web & Media > -- Chris Lilley @svgeesus Technical Director @ W3C W3C Strategy Team, Core Web Design W3C Architecture & Technology Team, Core Web & Media
Received on Tuesday, 6 February 2024 19:30:14 UTC