Re: Deprecated html elements and javascript functions

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.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/unescape

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.

Paul.


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
>