{
  "category": "JavaScript",
  "flag_name": null,
  "id": 5072451480059904,
  "milestone": 135,
  "name": "Remove clamping of setInterval(...) to >= 1ms",
  "summary": "Currently setInterval with a value less than 1 is clamped to 1. This intent removes that restriction.\n\nBefore: setInterval(..., 0) -> 1ms delay.\nAfter: setInterval(..., 0) -> 0ms delay.\n\nNotes:\n* This has no effect on the 4ms clamping for nested calls to timeouts.\n* setTimeout clamping was removed in a previous intent."
}

{
  "category": "JavaScript",
  "flag_name": "--js-float16array",
  "id": 5164400693215232,
  "milestone": 135,
  "name": "Float16Array",
  "summary": "Adds the Float16Array typed array. Number values are rounded to IEEE fp16 when writing into Float16Array instances."
}

{
  "category": "JavaScript",
  "flag_name": null,
  "id": 5067669587623936,
  "milestone": 136,
  "name": "Update ProgressEvent to use double type for 'loaded' and 'total'",
  "summary": "The ProgressEvent has attributes `loaded` and `total` indicating the progress, and their type is `unsigned long long` now.\r\n\r\nWith this feature, the type for these two attributes is changed to `double` instead, which gives the developer more control over the value. For example, the developers can now create a ProgressEvent with the `total` of 1 and the `loaded` increasing from 0 to 1 gradually. This is aligned with the default behavior of the <progress> HTML element if the max attribute is omitted. "
}

{
  "category": "JavaScript",
  "flag_name": "--js-regexp-escape",
  "id": 5179154657705984,
  "milestone": 136,
  "name": "RegExp.escape",
  "summary": "RegExp.escape is a static method that takes a string and returns an escaped version that may be used as a pattern inside a regular expression.\r\n\r\nFor example, copied from the proposal explainer:\r\n\r\n```\r\nconst str = prompt(\"Please enter a string\");\r\nconst escaped = RegExp.escape(str);\r\nconst re = new RegExp(escaped, 'g'); // handles reg exp special tokens with the replacement.\r\nconsole.log(ourLongText.replace(re));\r\n```"
}

{
  "category": "JavaScript",
  "flag_name": "harmony_remove_intl_locale_info_getters",
  "id": 5148228059398144,
  "milestone": 136,
  "name": "Deprecate getters of Intl Locale Info",
  "summary": "Intl Locale Info API is a Stage 3 ECMAScript TC39 proposal to enhance the Intl.Locale object by exposing Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale.\r\nhttps://github.com/tc39/proposal-intl-locale-info\r\n\r\nWe ship our implementation in m99 (https://chromestatus.com/feature/5566859262820352 ) . But later on the propose made some change in Stage 3 and move several getters to functions. We need to remove the deprecated getters and relaunch the renamed functions\r\n"
}

{
  "category": "JavaScript",
  "flag_name": "",
  "id": 5100466238652416,
  "milestone": null,
  "name": "Explicit Compile Hints with Magic Comments",
  "summary": "Allow attaching information about which functions should be eager parsed & compiled in JavaScript files.\n\nThe information will be encoded as magic comments.\n\nWe'll first target launching the file-based explicit compile hints, and as a follow up, investigate selecting individual functions for eager compilation."
}

{
  "category": "WebAssembly",
  "flag_name": null,
  "id": 5165273114738688,
  "milestone": 137,
  "name": "WebAssembly Branch Hints",
  "summary": "Improves the performance of compiled WebAssembly code by informing the engine that a particular branch instruction is very likely to take a specific path.\n\nThis allows the engine to make better decisions for code layout (improving instruction cache hits) and register allocation.\n\nhttps://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md"
}

{
  "category": "WebAssembly",
  "flag_name": "enable-experimental-webassembly-stack-switching",
  "id": 5674874568704000,
  "milestone": 137,
  "name": "JavaScript Promise Integration",
  "summary": "JavaScript Promise Integration (JSPI) is an API that allows WebAssembly applications to integrate with JavaScript Promises.\n\nIt allows a WebAssembly program to act as the generator of a Promise, and it allows the WebAssembly program to interact with Promise-bearing APIs.\n\nIn particular, when an application uses JSPI to call a Promise-bearing (JavaScript) API, the WebAssembly code is suspended; and the original caller to the WebAssembly program is given a Promise that will be fulfilled when the WebAssembly program finally completes.\n\nJSPI is described in more detail in https://github.com/WebAssembly/js-promise-integration which is part of the W3C WebAssembly standards track. See  also https://github.com/WebAssembly/stack-switching and https://github.com/WebAssembly/meetings/tree/main/stack."
}