W3C home > Mailing lists > Public > public-webplatform@w3.org > July 2013

Re: What to do with CSS properties that have been renamed?

From: Jordan Pagels <jordan@realeyes.com>
Date: Mon, 22 Jul 2013 13:26:35 -0600
Message-ID: <CA+w3VhjJ=zXKZJtgzHu4uphU1ArFkDq0t_DpcJgxKcyKR0HMSg@mail.gmail.com>
To: Lea Verou <lea@w3.org>
Cc: WebPlatform Community <public-webplatform@w3.org>
For my two cents, I think that the second solution you propose of
redirecting to the newest name and including a note with previous names,
might be the best.

It is always amazing what people will manage not to read on the internet,
so I think that would help avoid confusion.


On Sat, Jul 20, 2013 at 1:38 PM, Lea Verou <lea@w3.org> wrote:

> This issue is more prevalent with flexbox. Several properties have been
> renamed over and over during the Working Drafts stage. For example,
> flex-align to align-items.
>
> Do we keep separate pages for these, telling people not to use them in the
> summary and what they’ve been renamed to (such as here [1]) or do we
> redirect to the newest name, adding a note with older names?
>
> I used to do the former so far in my cleanup, but it just dawned on me
> that the latter might be a better approach.
>
>
> [1]: http://docs.webplatform.org/wiki/css/properties/-ms-flex-item-align
>
> Lea Verou
> W3C developer relations
> http://w3.org/people/all#leahttp://lea.verou.me ✿ @leaverou
>
>
>
>
>
>
>


-- 
*[ Jordan Pagels | Creative Developer]** *
[ RealEyes Media, LLC | www.realeyes.com <http://www.realeyesmedia.com/> ]
[ 940 Logan Street | Denver CO, 80203 ]
[ b. www.jpgls.com ]
[ t. @designerJordan <https://twitter.com/designerjordan> ]
Received on Monday, 22 July 2013 19:27:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:52 UTC