Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

toString method for a number returns 'undefined'

more options

The toString method for a Number object is returning the string 'undefined' (a string literal, not the undefined object) instead of the string representation of the number in question. This can be tested with a literal:

(5).toString();

Or with a variable:

var test = 5; test.toString();

And occurs in both in code running on a page, in the built-in JS console, and in Firebug, with Firefox versions 40.0.3 and 41.0. Expected result would be the string literal "5". (Which is exactly what I get with other browsers.)

This does not conform to the spec located here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toString

Is this a known defect? If so, is there a recommended workaround?

UPDATE: Looks like this is specific to a particular site, so I presume the client has implemented something that overrides the toString method. Feel free to close and ignore this request.

The toString method for a Number object is returning the string 'undefined' (a string literal, not the undefined object) instead of the string representation of the number in question. This can be tested with a literal: (5).toString(); Or with a variable: var test = 5; test.toString(); And occurs in both in code running on a page, in the built-in JS console, and in Firebug, with Firefox versions 40.0.3 and 41.0. Expected result would be the string literal "5". (Which is exactly what I get with other browsers.) This does not conform to the spec located here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toString Is this a known defect? If so, is there a recommended workaround? UPDATE: Looks like this is specific to a particular site, so I presume the client has implemented something that overrides the toString method. Feel free to close and ignore this request.

Được chỉnh sửa bởi netgecko99 vào

Tất cả các câu trả lời (1)

more options

Testing in Firefox 41 on Windows, I see the expected result in the Web Console (Ctrl+Shift+k). Screen shot attached. ??