- From: arturjanc via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Nov 2020 15:36:24 +0000
- To: public-css-archive@w3.org
> Would custom elements defining form controls via ElementInternals be able to declare certain attributes as sensitive? > Would JS developers be able to declare a sensitive attribute as "non-sensitive" and expose it to CSS somehow? Or is mirroring it to a data- attribute the only way? I don't think we're at the point of having a specific API proposal here, but IMHO the answer to both questions is that there's nothing preventing us from building an API like this, and it would indeed be useful. Specifically, it would help sites that match on `input[value]` retain their current functionality, like in the examples mentioned above. I imagine it would also be possible to build a default allowlist for legacy uses, i.e. we could permit certain functions or properties in combination with commonly used attributes, such as `value`. This does complicate the design, but it would get us close to allowing backward compatibility while offering a safe path towards shipping new, more powerful, CSS functions. -- GitHub Notification of comment by arturjanc Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5136#issuecomment-732237666 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 November 2020 15:36:26 UTC