W3C home > Mailing lists > Public > www-style@w3.org > March 2016

Fwd: Re: [css-forms][css-ui] Styling native components, a proposal

From: Jens Oliver Meiert <jens@meiert.com>
Date: Sun, 27 Mar 2016 19:34:35 +0200
Message-ID: <CAJ0g8QSBQETEmKQ6UZfASg63M02nE_gmwYQ=mJAuqBff0a5YRw@mail.gmail.com>
To: W3C WWW Style <www-style@w3.org>
Resending due to email mixup.


---------- Forwarded message ----------
From: "Jens Oliver Meiert" <jens.meiert@gmail.com>
Date: Mar 27, 2016 8:39 AM
Subject: Re: [css-forms][css-ui] Styling native components, a proposal
To: "Lea Verou" <lea@verou.me>
Cc: "W3C WWW Style" <www-style@w3.org>

This is an important topic and a great start for discussion. What I
miss is a closer look at the possible response of “take it or leave
it.”

There are not only many technical challenges to overcome on the spec
and implementation sides, but the styling of controls oftentimes (most
of the times?) leads to usability issues on the user end as well.
Furthermore it doesn’t seem clear how many developers need this for
what (many don’t), nor what the drawbacks will be for, coming back a
tiny circle, the spec and implementors.

I have voiced complexity concerns in the past [1,2], and believe
they’re valid here, too. I worry the price tag for this is too steep,
and I don’t believe in features at any cost.

I’m curious about yours and the group’s thoughts.


[1] http://meiert.com/en/blog/20121112/the-css-problem/
[2] http://meiert.com/en/blog/20150518/fing-up-standards/

--
Jens Oliver Meiert
http://meiert.com/en/
Received on Sunday, 27 March 2016 17:35:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:01 UTC