- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 May 2024 00:40:33 +0000
- To: public-css-archive@w3.org
> However it would feel a bit odd if appearance: none did not show the rich markup > appearance: auto may be more of a special case given native frameworks may have restrictions that prevent showing the markup. appearance:none and appearance:auto both use the same native or platform-specific picker, so I don’t see how we can make appearance:none switch to using an unrestricted non-native picker without breaking websites which expect to get a native picker. On at least Chromium browsers, this picker exists within a separate OS window that can extend beyond the content area, meaning it cannot contain arbitrary content without creating security issues. > Either way, how appearance: none and auto interact with the rich select markup are questions that should be answered, especially as it will pave the way for how appearance generally works even for future controls. I figured this would be up to the platform because as you mentioned there are platform-specific restrictions which may prevent showing the markup. Should we really mandate that certain portions of the markup do or don’t get rendered by the native framework? -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10332#issuecomment-2111381959 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 May 2024 00:40:34 UTC