The issue with the no-op filter affecting rendering is a software bug that should be reported to the browser vendor for resolution. Providing a reduced test case will assist in troubleshooting and fixing the problem.
In addition, there is an ongoing challenge with color profile management in videos that needs attention. Images and CSS colors on the web typically adhere to the sRGB color space, while videos internally utilize various other color spaces such as Rec. 709 (for HD) and BT. 601 (for old SD TV).
The issue arises when these profiles are not accurately converted between, leading to discrepancies in color representation. Differences in gamma values between Rec. 709 (~2.4) and sRGB (~2.2) can result in variations in brightness, while mixing up 709/601 can cause shifts in hue.
Aligning video colors with CSS colors requires precise coordination:
- The software used to generate videos must read colors in sRGB and convert them correctly to the video's color space (e.g. Rec. 709), which may require specific settings adjustments.
- Metadata within the video file should include information about the color space to prevent players from making assumptions. Some players, like Firefox, may still guess incorrectly.
- The player (browser) must comprehend video color spaces and select the appropriate color space accordingly.
- The browser should play the video while converting colors to match the display color space, although some browsers may not do this automatically without manual configuration.
- The browser must also convert CSS colors from sRGB to the display color space, or at least ensure videos are always converted to sRGB. Chrome has been known to struggle in this area.
Safari typically handles these color conversions smoothly, but many other browsers exhibit significant bugs in this process. It might be worth considering design changes to mitigate any noticeable differences caused by color discrepancies.