Skip to content

Intl.DateTimeFormat(...).resolvedOptions() always return 'short' in timeZoneName #26790

Closed
Closed
Intl.DateTimeFormat(...).resolvedOptions() always return 'short' in timeZoneName#26790
Assignees
srl295
Labels
i18n-apiIssues and PRs related to Node.js internationalization support.v8 engineIssues and PRs related to the V8 dependency.

Description

@vitvad
vitvad
opened on Mar 20, 2019

Version: tested for 9.21 and 11.60
Platform: OSX Mojave x86_64

tested with ICU v: '63.1', and without.

quick step to reproduce:

var region1 = new Intl.DateTimeFormat('en-US', { timeZoneName: 'long' });
console.log(`'${region1.resolvedOptions().timeZoneName}' should be equal to 'long'`);

will always return 'short'.

Chrome v72.0 - show's correct value
you can check it quickly in sandbox at MDN
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat

Activity

  1. sam-github commented on Mar 20, 2019

    @sam-github
    sam-github
    on Mar 20, 2019
    Contributor

    @nodejs/intl

  2. TimothyGu commented on Mar 20, 2019

    @TimothyGu
    TimothyGu
    on Mar 20, 2019
    Member

    Could you try installing full-icu as documented here?

  3. TimothyGu
    added
    questionIssues asking questions about Node.js.
    i18n-apiIssues and PRs related to Node.js internationalization support.
    on Mar 20, 2019

  4. srl295 commented on Mar 20, 2019

    @srl295
    srl295
    on Mar 20, 2019
    Member

    ^ not repro in all versions, may be something that was fixed in v8

  5. srl295
    self-assigned this
    on Mar 20, 2019
  6. srl295
    added
    assertIssues and PRs related to the assert subsystem.
    on Mar 20, 2019

  7. srl295 commented on Mar 20, 2019

    @srl295
    srl295
    on Mar 20, 2019
    Member

    working fine in 42dbaed

  8. srl295 commented on Mar 20, 2019

    @srl295
    srl295
    on Mar 20, 2019
    Member

    was fixed in 9b4bf7d #23423 "update V8 to 7.1.302.28"

  9. srl295
    closed this as completedon Mar 20, 2019
  10. srl295
    added
    v8 engineIssues and PRs related to the V8 dependency.
    and removed
    questionIssues asking questions about Node.js.
    assertIssues and PRs related to the assert subsystem.
    on Mar 20, 2019

  11. vitvad commented on Mar 20, 2019

    @vitvad
    vitvad
    on Mar 20, 2019
    Author

    @srl295 Thank you for quick response.
    I just checked node v11.12.0 and it has v8 version v8: '7.0.276.38-node.18',
    could you please clarify when node build with new v8 will be available ? As I see in ticket above, original plan was - Dec 2018.
    As I understand it appear in node v12 around 2019-04-23 ?

  12. srl295 commented on Mar 20, 2019

    @srl295
    srl295
    on Mar 20, 2019
    Member

    @vitvad Welcome. I'm not quite sure how to answer your question. You could ask on PR #23423 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

i18n-apiIssues and PRs related to Node.js internationalization support.v8 engineIssues and PRs related to the V8 dependency.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions