Joe Pea

[Custom Elements] Error in IE11: The custom element being constructed was not registered with `customElements`.

11

### Description `CustomElementInternals.js` causes an error in IE. #### Live Demo Run this pen in IE11: https://codepen.io/anon/pen/dJerjB #### Steps to Reproduce See the pen in IE11. You can use http://crossbrowsertesting.com...

Hey, thanks for that feedback! Neat project btw. I realized right after we chatted something totally simpler: in a single traversal, the first encountered node that is valued between a...

Proposal 2, for The Decorator Ordering Problem

1

# The problem in general: See the following issues (most recent first) where "Proposal 1" is mentioned in comments such as [this one](https://github.com/tc39/proposal-decorators/issues/571#issuecomment-3652480940). This is a separate issue to outline...

I wish "context initializers" ran in definition order.

28

I wish the following, implemented with `context.addInitializer()` only, would simply work: ```js class MyClass { @signal a = 1 @signal b = 2 @memo get sum() { return this.a +...

decorators run in unexpected order

3

This is unexpected and unintuitive: ```js function signal(_, context) { console.log('@signal decorator', context.name) } function memo(_, context) { console.log('@memo decorator', context.name) } class My { @signal a = 1 @signal...

Yet another unexpected initializer ordering causes TDZ errors

29

This throws: ```js function dec2(_: any, context: any) { context.addInitializer(function (this: any) { console.log(this[context.name]) // Boom! Error! "Cannot read private member from an object whose class did not declare it"...

ability to patch/observe initializers

6

# The problem It is currently not possible to patch initializers (f.e. for class fields). If it were, we could easily do the following: ```js class MyClass { @signal a...

Start to disambiguate between types of initializers.

2

The README says [here](https://github.com/tc39/proposal-decorators?tab=readme-ov-file#adding-initialization-logic-with-addinitializer): > **Field and Accessor decorators:** During class construction, immediately after the field or accessor that they were applied to is initialized This [TypeScript playground example](https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABAEwKYTgCgN4HNVQA0iAzgQL4BciAwgDYCGJJAghBKs3AE4Ai6PBlB4AVBt3xQAPOADWYOAHcwxOQuUA+YtAAe1ek1btOJHvwzchPGgiiodUAJT7GzNhy58Bl4dwBKnCB00gxgAJ7EoWEaiNgAUIiJiLoAdAzIyACSYDCwDHQwAF6o3JigkLAIiJiOsQlJDRhgpnSoKXRwuJgA5AzGnslQOmkZ2bkw+UUl1eD2AA7odsiO3cSYUAAWMCSITLvhjinAcHC1APRniPOLqMiIAIwATADMxLhwUIjgaMAwYLfVGDARC5EE7ABE+W4qHSYRBOTyBWKyHBxE2qCQmVIGzgQTuZFQiHRiAAbvkQKhHPVEuQqdTENCoCBuEg8ARiGQiPDcjU6g0GlBuHD4vzRckEC02h0ur1+qZuAyCMykH9xpNitxVtVNttdjsoodjqd6Q1yMkhBANphKXyxY0JXBWu1Oj0+h55VduNweIr0n9cIg5twYGS7KQoEJCQAjVDHaHcxFFITwJDWnQLaC3FbnS7XTN3Ere7hvD6eosmpLkenkKtVuLlaAplACR6YAD61G+sb+t20QxchgAYjBUHRkOZBL4bGA7A5nNV1lsSNQosQyXQVwdEABeGIG22JVLpLIIiZIkplcCNqq8kVipqS50y36ju5H0an9XTTCzdM3ZZaouup7AaRwnDmVx-vmDwvCWnxdr8-x3JgQIgp8uqQnQ0KwgmZ5TCiaIbBiiBYiQOJ4qQqCEsS64UlSpp0g0jLKogDaVGAQHLvsYS1HeooPo6Uout0L5joqTIsrhX4KmmGZLCshHbGBpyIBckFyQCCE9sgcFfGAPzadUJCwHQdBSUi-r0ZWcR1hArg7AAsmEBjMAeiAAAJoBguxyj6Ro7jBzxxPSnktogUbiAFAAsACsABsNnBf8iiIE5LkkDUcRAA) shows...