W3C home > Mailing lists > Public > public-webplatform@w3.org > March 2014

Re: Deprecated html elements and javascript functions

From: Paul Verbeek <paul@webinthehat.com>
Date: Wed, 12 Mar 2014 13:17:27 -0700
Message-ID: <CAHN5aqRT=aMECZu3+kcbv+aNxn=nCZViWUsxs1Yw71EdfASwQA@mail.gmail.com>
To: Max Polk <maxpolk@gmail.com>, Douglas Schepers <schepers@w3.org>, Eliot Graff <eliot.graff@microsoft.com>
Cc: "public-webplatform@w3.org" <public-webplatform@w3.org>
Hi Max,

Even though that explains why it's deprecated, I think it should still be
on WPD. It's widely implemented by browsers and used in some projects.

I was speaking to Doug and Eliot, and they had the idea to add flags for
things like this (deprecated, obsolete, etc.) like MDN does.

For now, I just added it to the 'depracted' group of related articles, so
we can easily filter them out when we have the flags.


On 11 March 2014 16:39, Max Polk <maxpolk@gmail.com> wrote:

>  On 3/11/2014 1:26 PM, Paul Verbeek wrote:
> Hi all,
>  I'm working on the docs for the unescape function. This function is
> deprecated and the only way to tag that is at the See Also section.
>  I think a deprecated function or html elements should say that it's
> deprecated in a more noticeable way. Maybe a message on top saying
> something like "This function/object/element is deprecated. We advice
> against using it in new projects. Please use with caution.".
>  Paul.
> It seems to have been deprecated in favor of a replacement:unescape ->
> decodeURI or decodeURIComponent
Received on Wednesday, 12 March 2014 20:18:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:59 UTC