| 09:19 | <frank-dspeed> | i need help again which category is that https://github.com/frank-dspeed/tc39-proposal-importScripts Normative: changes impacting JavaScript behavior in some way. These changes are called "observable" because it is possible to write code to "observe" the change in behavior. Editorial: any non-normative changes to spec text including typo fixes, changes to the document style, etc. Layering: refactoring of specification text, algorithms, and/or embedder hooks to enable clean integration of the JavaScript specification with other specifications that use JavaScript. Markup: non-visible changes to markup in the spec Meta: changes to documents about this repository (e.g. readme.md or contributing.md) and other supporting documents or scripts (e.g. package.json, design documents, etc.) |
| 09:28 | <nicolo-ribaudo> | That is definitely normative, because you can write JS code that uses that new proposed feature |
| 09:28 | <frank-dspeed> | ok thanks for clarifying |
| 10:28 | <frank-dspeed> | can some people please look into this and give feedback https://github.com/frank-dspeed/tc39-proposal-importScripts/issues/2 |
| 10:29 | <frank-dspeed> | i am not sure if that case leads to web-reality-pr https://github.com/tc39/how-we-work/blob/main/pr.md#web-reality-prs and so i would need to change the name of the proposal? |
| 10:31 | <nicolo-ribaudo> | Web reality PRs are for "all the engines agree on X, but the spec says Y: we should update the spec to say X". This is not the case for your proposal, since importScripts is not already available everywhere |
| 10:34 | <nicolo-ribaudo> | can some people please look into this and give feedback https://github.com/frank-dspeed/tc39-proposal-importScripts/issues/2 Sure, we must make sure that the proposal does not break the web and we can start thinking about it, but it's not high-priority at the moment. |
| 10:41 | <frank-dspeed> | nicolo-ribaudo: thanks a lot sorry for my confusion that explaination helped me a lot. |