Re: [csswg-drafts] [css-grid][css-sizing] Aspect Ratio (#333)

The specific [WICG Aspect Ratio Incubator Project](https://github.com/WICG/aspect-ratio) was closed and there's a message on its README.md file redirecting the discussion to this issue here.

I wonder why this was done, since the Pixel Aspect Ratio isn't restricted to CSS. I can't even post a new issue there.

I'm trying like to bring awareness to the problem that the [Pixel Aspect Ratio](https://en.wikipedia.org/wiki/Pixel_aspect_ratio) (PAR) is still not rendered correctly by any of the current browsers I tested. This is a metadata present inside JPG, PNG and GIF files.

A lot of content was created in the 80's and 90's that had non-square pixels.

For example, many legacy pixel art based on rectangular pixels (*1) are being destroyed, as the use case is still present and the users are doing workarounds by artificially stretching the images via resize to have the desired aspect ratio. Once the image is stretched like this, it's nearly impossible to restore it without loss.

The same issue affects all images (stills and video) captured from SDTV. NTSC had an effective resolution of 720x480, which means that it's pixels aren't square. Just like pixel art, users have no alternative other than artificially stretch the image to adjust it for square pixels, creating artifacts that will be impossible to cleanup later.

Inspired by the HTML AcidTests, I created the Pixel Aspect Ratio Acid Test, that can be seen in the link below. It will check if the browser renders two sets of images correctly.

http://frs.badcoffee.info/PAR_AcidTest/

*1: Read C64, CGA, EGA, VGA (320x200), SNES, MSX, Amiga, TurboGrafx-16, NEC PC-88 and nearly the [majority of devices from the 80s](https://pineight.com/mw/page/Dot_clock_rates.xhtml), when square pixels were still an expensive luxury.





-- 
GitHub Notification of comment by sdsnatcher
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/333#issuecomment-984712810 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 2 December 2021 15:06:09 UTC