W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: Styling composite elements

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 20 Feb 2013 13:50:01 -0800
Message-ID: <CAAWBYDANjZo+pwmsXEL8=54qK9FgaywBaDaXYRUQ4R-Dd9i-Fg@mail.gmail.com>
To: Antony Kennedy <antony@silversquid.com>
Cc: www-style list <www-style@w3.org>
On Wed, Feb 20, 2013 at 1:46 PM, Antony Kennedy <antony@silversquid.com> wrote:
> Styling select boxes should be a priority. The amount of times in my career I've had to fake these is ridiculous, and you can never adequately meet the intricacies of the real controls. These have existed for years, and we still cannot adequately style them. CSS variables, and such are all well and good, but it doesn't seem like the basics are fixed yet, and we're just inventing new things instead of cleaning house.
> How about if there were a standardised version of the select box you can enable via CSS? And if you don't do this, the browser can do whatever it likes?
> Exactly how -webkit-appearance: none; works, in fact.
> If the standardised version of the select box had specific elements and behaviours, all written down in a specification then authors could predict those behaviours, and the pseudo-elements Henrick described would be predictably available. If the standardised version were enabled via CSS, then that is a lot less difficult to cope with? If it weren't enabled, the browser could do whatever it wanted.

Have you seen what <select> elements do on mobile browsers, like
Chrome on Android or the iOS browser?  It would be a terrible
experience for the user if you could opt into a "normal" <select>.

Received on Wednesday, 20 February 2013 21:51:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:26 UTC