I guess there're two questions:
- supporting the CSS property value for <video> which is a spec related change (maybe it works in Mozilla, but neither MDN, nor the CSS spec mention it in the context of videos)
- is it something the Chrome video stack can do today

sergeyu@, do you mean that Firefox supports `image-rendering:` for videos?

Yes, image-rendering is supported in Firefox for video (verified it with 50.1.0).

Note that Firefox currently implementes 'optimizeSpeed' and '-moz-crisp-edges', but not 'pixelated' (see https://bugzilla.mozilla.org/show_bug.cgi?id=856337). Also it only works with software rendering (see https://bugzilla.mozilla.org/show_bug.cgi?id=1083516).

This is something I have wanted for a while, but actually implementing it across all the different compositing paths is somewhere between difficult and impossible.

The software decode + regular compositing path is simple enough, it's just a texture filter change. The GLImage paths I'm less sure about, since AFAIK the texture filtering is set by the decoder instead of the compositor.

When we get to full under/overlays it becomes platform-specific and I'm not certain we can do it in all cases. There will likely be a power cost for some platforms (eg. Mac), and no options at all on others (eg. Android, Chromecast).

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot