« Bugzilla Issues Index

#1153 — codePointAt: `undefined` vs. `NaN` return value

Step 7 returns `undefined` for invalid positions, but per introductory paragraph `NaN` should be returned in that case.

Yes, Norbert needs to confirm whether this should be NaN (consistent with charCodeAt) or undefined (consistent with other missing element access)

*** Bug 1902 has been marked as a duplicate of this bug. ***

comment fixed in rev19 editor's draft

(this is why we try to avoid redundant informative text)

fixed in rev19