- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 18:23:15 +0000
- To: public-css-archive@w3.org
After the discussion yesterday, and giving @annevk’s remarks some more thought, we actually agree that it seems best to have separate opt-in’s for the in-page control and the picker, **even in the case of `<select>`**. So despite our comments yesterday, we’re in favor of adopting @fantasai’s [proposed three bullet points](https://github.com/w3c/csswg-drafts/issues/10440#issuecomment-2303554166), as-is. As mentioned by @emilio, we will have to work through exactly what happens in the two “mismatched” cases, where the picker is native and the in-page is “base”, or vice versa. That’ll take some work, but it seems tractable. It's possible we run into some roadblocks and we'll have to revisit those here. But otherwise we'll get started thinking about it. Your input would be appreciated! Separately, there was a request made for Google to provide our own more-explicit “vision” for how to go about this form redesign process, and we’re working on that. More to come. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10440#issuecomment-2307593411 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 18:23:16 UTC