W3C home > Mailing lists > Public > public-html@w3.org > April 2010

Re: ISSUE-96 Change Proposal

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 1 Apr 2010 07:41:25 -0700
Message-ID: <h2x63df84f1004010741hc8c28b12m158f2c3480ac6fb3@mail.gmail.com>
To: Shelley Powers <shelley.just@gmail.com>
Cc: HTMLWG WG <public-html@w3.org>
On Thu, Apr 1, 2010 at 6:04 AM, Shelley Powers <shelley.just@gmail.com> wrote:
> In my opinion, this is a bad direction to take across the board.  Do
> we really want to disregard the strides we've made with JavaScript and
> CSS and start creating declarative elements? Especially in an
> environment that is not set up for declarative elements or animations?

My impression is that yes, declarative elements are a good thing. I
think W3C has been a supporter of declarative markup languages for a
long time.

> If we're 'allowing' people to come up with their own web designs, why
> not a progress bar that matches the web site, rather than the
> operating system? I personally don't want the browser companies and OS
> to dictate what my page looks like.

Indeed, I think that in order for <meter> and <progress> to be popular
CSS will need to grow the ability to style them to web authors
content. Same thing with <input type=date> and some of the other new
form controls.

We're already seeing this with scrollbars where sites are starting to
create much less accessible pages in order to hack together their own
scrollbars using piles of <divs> in order to get them to look the way
they want. I believe Apple has stepped up and proposed some extensions
to CSS to help with this situation.

My point is that this isn't something that HTML should fix, but
something that needs to be fixed using CSS expansions.

/ Jonas
Received on Thursday, 1 April 2010 14:42:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:00 UTC