- The disagreement about removing prefers-contrast: forced (Issue #5433: duplication of `forced-colors: active` and `prefers-contrast: forced`) was focused around users who have defined a color set which would not qualify as high or low for the forced-colors media query and therefore would not be detected if prefers-contrast: forced was removed.
- Firefox will gather data about the colors used so the group can monitor if the change would cause a negative impact in experience for these users.
- There was also disagreement as to if reduced visual complexity is necessary when there are forced colors. There was no data available about expectations and people had contrasting views on what is most likely.
- There was discussion on if the prefers-contrast MQ should be held back until the group decides how to handle the reduced complexity and forced color relationship. The group didn’t agree, though, so it will be opened as a separate issue.
- Resolved: Remove the forced value from prefers-contrast MQ (Issue #5433)
- Resolved: Bake the smoothing into non-integer changes in current pixelated value. Add a new value for nearest neighbor jaggedness (Issue #5837: image-rendering:pixelated should not force “nearest neighbor” (or similar) when the scale factor is far from an integer (e.g. 150%))
- Resolved: Republish CR-snapshot of Scroll Snap
- Resolved: Add an ‘alternate’ value which is the initial value (Issue #5971: Alternating sides for ruby-position)
↧
Minutes Telecon 2021-02-24
↧
