- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Mar 2025 14:27:53 +0000
- To: public-css-archive@w3.org
So in 2020 Blink did a "form controls refresh" which was a joint project between Chrome and Edge. As part of that project, we did actually add a `::reveal` pseudo element for `<input type=search>` and we tried to ship it. However, we got several compat bugs reported (e.g. [this one](https://issues.chromium.org/issues/40654543)), enough that we decided to re-disable the `::reveal` pseudo element. Microsoft was able to successfully ship it as `::ms-reveal` at that point. The compat problems all stem from (*existing*) sites that have their own "reveal" button. The UX is **very** confusing to users when two separate reveal buttons are present. It's a relatively-easy fix for such sites, just setting `display:none` on the pseudo element to hide it. But still there were enough of them that we weren't comfortable shipping the feature back then. But I think with an opt-in like `appearance:base`, it should be a great addition to the platform. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11845#issuecomment-2714524359 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 March 2025 14:27:54 UTC