- There was pushback in issue #5710 (Shielding system colors to avoid fingerprinting?) to not closing the fingerprinting risk with system colors so the group spent time on the call digging into which of the other possible solutions would be best. However, what was discovered is that both possible solutions would cause bad user experience. Chris and TabAtkins will explain the ramifications of fixing the fingerprinting vector and request the original need be reevaluated. They’ll also involve the Accessibility Group in the discussions since they will be the worst impacted.
- Resolved: Add these 6 colors [caret-color, flood-color, lighting-color, stop-color, fill-color, stroke-color] to the list (Issue #5873: Missing forced color properties)
- Resolved: Have the MQ resolve their em against the actual default size which includes minimum — and anything else that might affect it in the future (Issue #5858: Account for minimum font size in relative length media queries)
- Resolved: UAs may use an accent-color outside of form controls at their discretion (Issue #5657: Use of accent color outside of form control elements)
- Resolved: Close no change [the current spec text is correct] (Issue #4227: min/max(%, %) should explicitly evaluate against the % value, not the resolved value)
- There still was no consensus on if the best name for the new property would be levels or layers (Issue #5840: Layers terminology bikeshed). Layers being commonly used in design programs like photoshop was sighted as both and advantage since it could serve as an analogy but a disadvantage because people already associate it with other functionality. Discussion will continue on GitHub.
- The group was split between using a dot or a space in the syntax (Issue #5791: What is the appropriate syntax for appending to nested layers?). The dot was familiar for those using JS and evoked the right kind of nesting, however the space is more CSS-y. Discussion will continue on GitHub.
↧
Minutes Telecon 2021-01-27
↧