Closed Bug 1346081 Opened 9 years ago Closed 7 years ago

[test262][ecma402] Two regressions in NumberFormat.prototype.format for RTL locales

Categories

(Core :: JavaScript: Internationalization API, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: zbraniecki, Unassigned)

Details

## test262/intl402/NumberFormat/prototype/format/11.3.2_TRP.js: rc = 3, run time = 0.046876 uncaught exception: Test262Error: Formatted value for 123.44500, en-US-u-nu-arab and options {"useGrouping":false,"minimumSignificantDigits":3,"maximumSignificantDigits":5} is ١٢٣٫٤٥; expected ١٢٣٫٤٤. TEST-UNEXPECTED-FAIL | test262/intl402/NumberFormat/prototype/format/11.3.2_TRP.js | (args: "") ## test262/intl402/NumberFormat/prototype/format/11.3.2_TRF.js: rc = 3, run time = 0.065173 uncaught exception: Test262Error: Formatted value for 12344501000000000000000000000000000, en-US-u-nu-arab and options {"useGrouping":false,"minimumIntegerDigits":3,"minimumFractionDigits":1,"maximumFractionDigits":3} is ١٢٣٤٤٥٠١٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٠٫٠; expected ١٢٣٤٤٥٠١٠٠٠٠٠٠٠٠٠٤٨٧٨١٥٤٤٤٦٧٨٣١١٩٣٦٫٠. TEST-UNEXPECTED-FAIL | test262/intl402/NumberFormat/prototype/format/11.3.2_TRF.js | (args: "")
Priority: -- → P5
Two more new tests hit the same bug, a total of four tests: test262/intl402/NumberFormat/prototype/format/format-fraction-digits.js test262/intl402/NumberFormat/prototype/format/format-fraction-digits-precision.js test262/intl402/NumberFormat/prototype/format/format-significant-digits.js test262/intl402/NumberFormat/prototype/format/format-significant-digits-precision.js
I've split the tests up (https://github.com/tc39/test262/commit/d9f67d53d11459c1e0e245d8ebe9fb0608abcaaa). Only the ones ending with "-precision.js" now need to be skipped for us.

The tests were changed to match "web-reality", which means browsers, which means whatever ICU does. The spec however wasn't yet changed, see the linked ecma-402 issue from above. Therefore resolving as WFM.

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.