1381295 - String.charCodeAt() doesn't exist

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Jim Michaels]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170628075643

Steps to reproduce:

String.charCodeAt(34)


Actual results:


51
String.charCodeAt is deprecated; use String.prototype.charCodeAt instead


Expected results:

should have worked. code point API not completely there yet, 1 String method missing.

Comment 1

[Jim Michaels]

ReferenceError: charCodeAt is not defined[Learn More]

Comment 2

[Kohei Yoshino [:kohei]]

See https://www.fxsitecompat.com/en-CA/docs/2016/non-standard-array-string-generics-have-been-deprecated/

Comment 3

[Jim Michaels]

wow the guy that made that web page was grumpy. that's like removing String and Array and expecting something good from it.
I think my report here was based on a mistake in code by not starting from a string I saw something like fromCodeAt or something like that. but that web page is a major red warning bells alarm to me.

Comment 4

[Jim Michaels]

removing those is a bad idea, since there is no functionally-equivalent replacement. indexOf does NOT work the same as .search for example. I did a search and replace in my code, and my code went bonkers.

NS browser invented Javascript. I don't think it should be just thrown away so lightly. shouldn't ff be the standard now that it has replaced NS? please don't throw away a useful language at the ecma and trash JS anymore.

Comment 5

[Till Schneidereit [:till]]

(In reply to Jim Michaels from comment #4)
> removing those is a bad idea, since there is no functionally-equivalent
> replacement. indexOf does NOT work the same as .search for example. I did a
> search and replace in my code, and my code went bonkers.

I'm not sure what you're saying here. String.prototype.indexOf will never be removed, so why would you try to replace it with String.prototype.search? String.indexOf will be removed - just as String.search and all the other static functions on String and Array that just forward to .prototype versions.

> NS browser invented Javascript. I don't think it should be just thrown away
> so lightly. shouldn't ff be the standard now that it has replaced NS? please
> don't throw away a useful language at the ecma and trash JS anymore.

"The standard" isn't supposed to be a single browser, regardless of which one it'd be. It's the set of interoperable functionality implemented in all browsers with any meaningful market share, ideally codified in a formal standard such as ECMAScript. This set should ideally approach 100% of all functionality implemented in any of those browsers. We're not at all interested in extending the ways in which content authors could write code that only works in Firefox, not other browsers.