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

Re: Deprecated html elements and javascript functions

From: PhistucK <phistuck@gmail.com>
Date: Wed, 12 Mar 2014 23:32:45 +0200
Message-ID: <CABc02_L7XW0sju5VKNOkMa8rBZiOAuOe7Rea+25+=b7HSsVw0w@mail.gmail.com>
To: Paul Verbeek <paul@webinthehat.com>
Cc: Max Polk <maxpolk@gmail.com>, Douglas Schepers <schepers@w3.org>, Eliot Graff <eliot.graff@microsoft.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
If something is only included for compatibility, I guess you can think
about it as deprecated. But formally, you are right, it does not seem to be
deprecated.
However, the fact that it is not deprecated in the specification, does not
mean it is not deprecated by the browsers.
This function has historically been very problematic, especially regarding
non ASCII text and non UTF 8 encodings, which is why it is being deprecated
and other functions that surely yield UTF 8 are preferred.


☆*PhistucK*


On Wed, Mar 12, 2014 at 11:21 PM, Paul Verbeek <paul@webinthehat.com> wrote:

> It's in 5.1 in the (informative) Compatibility section [1], and in 6.0 in
> the the features for Web Browsers [2].
>
> So if it's in 6.0 it's not deprecated right? But then why does MDN [3] and
> MSDN [4] says it is?
>
> [1] http://www.ecma-international.org/ecma-262/5.1/#sec-B.2.2
> [2]
> http://people.mozilla.org/~jorendorff/es6-draft.html#sec-unescape-string
> [3]
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/unescape
> [4] http://msdn.microsoft.com/en-us/library/ie/dz4x90hk(v=vs.94).aspx
>
>
>
> On 12 March 2014 17:05, PhistucK <phistuck@gmail.com> wrote:
>
>> Hm, why is it on the JavaScript (ECMAScript) reference? as far as I
>> remember, it is not part of (any) such standard. If anything, it should be
>> in the DOM reference as I believe only browsers implement it.
>> The DOM reference has (or used to have, I did not check recently) a field
>> for the status (recommendation, deprecated and so on) which can be used
>> exactly for this purpose.
>>
>>
>> ☆*PhistucK*
>>
>>
>> On Wed, Mar 12, 2014 at 10:17 PM, Paul Verbeek <paul@webinthehat.com>wrote:
>>
>>> 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
>>>>
>>>
>>>
>>
>
Received on Wednesday, 12 March 2014 21:33:53 UTC

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