Safari also apply “HDR” to CSS filter: brightness() with value greater than 1. Instead of the over-exposure effect, this portion of the screen will be brighter.
You must have an HDR or EDR-capable screen and there must be an HDR video playing to activate the HDR context (can be <video> playing somewhere in a webpage).
Not to say for sure Apple Silicon chips support HW AV1 decode, but I would speculate that recent generations of their SoCs may have hardware support behind a software limitation through the lack of APIs.
Under /System/Library/Video/Plug-Ins/AppleVideoDecoder.bundle there's a Info.plist, inside there are references to AV1, below that is VTIsHardwareAccelerated = true.
AVD refers to Apple Silicon HW decoder. Side note, GVA means Intel, VCP means AMD.
I guess it will be like the situation of VP9. It was available at first via a special entitlement to YouTube iOS app [1] (com.apple.developer.coremedia.allow-alternate-video-decoder-selection) and later opened to all apps.
I believe Windows's approach is localisation not globalisation. Many programmes runs properly only in designed locales, not that programmes run well in any locale.
Chinese/Korean rendered incorrectly on English UI because system hardcoded a font fallback, which put Japanese font first, regardless of how languages are ordered in the Settings. This is largely true for traditional Win32 programmes, like Chrome, Edge, Explorer.exe, etc. However UWP apps using the new UI framework (like Unigram, Intel Command Centre etc) behave correctly if setting Chinese/Korean as secondary language.
It's different on macOS or iOS however, if you set a system locale order as 1. English, 2. Chinese, then Chinese content will render correctly with correct Chinese system font PingFang.
Another issue that is also very important is that Chinese (Simplified or Traditional), Korean and Japanese share amount of the same characters but written differently. That means system must render the glyph in correct variant, like in the example of Source Han Sans
This tool is more important in Chinese/Japanese/Korean environment as CJK glyphs have more strokes per character as compared to Latin languages. Windows's font rendering tends to fit glyph strokes into pixels (tint).
On a low DPI settings (<100), fonts on Windows look more sharp and clear, while on macOS, which discards the bitmaps altogether, the result is blurry (albeit I still prefer to be able to appreciate the original design).
On a higher DPI settings (>130), IMO under normal font sizes (>=10pt) the font has enough pixel realestate to behave like what it was designed. The antialiasing could do its job without relying the heavily hinted result.
Here are some comparisons.
https://pbs.twimg.com/media/EhoCr9GUYAAjzMG?format=webp
Left: AppleWin (Safari for Windows) | Right: Chromium | 12px PingFang SC on 200% system scale
As you can clearly see, Apple's font rendering makes every glyph clear enough while ensuring every stroke has the same weight, while Chromium, relying on Windows's font rendering makes the font jagged (stroke width varies), baseline not level (遵守 on the 3rd last line, component 辶's bottom is way up)
https://pbs.twimg.com/media/EJUJZL8UYAAC7sC?format=webp&name...
Left: AppleWin | Right: Chromium | 15px MS Gothic on 200% system scale
MS Gothic has a very large character design, but on the first line of paragraph, 口 from "口周辺" is not reaching the the height it supposed to do, because of Window's approach of fitting that stroke into a line of pixels. And Windows makes the font thinner. This approach apparently ruined every diagonal strokes like 丿 and 丶, making those strokes even fainter.
I have another example of Microsoft Yahei font being drastically better on 200% with MacType but I couldn't find it at the moment.
It's suffice to say that MacType will recovered the font rendering for Windows in 200% scale. However, in 100% scale, it provides fixes when Windows messed up with fonts in some cases when it purposefully fit the strokes into pixels.
While i appreciate Windows's effort to make glyphs more legible for lower pixel density displays, but at least provide a toggle to turn it off as it literally ruins everything else. Fonts MS used in every Office/Windows/even Windows Terminal showcase video are not hinted font yet the glyphs look pretty legible, and even gorgeous (if you appreciate the curves of Segeo UI) in a 4:2:0 subsampled video, animated, yet average Windows users can't find a way to experience this on daily basis without MacType.