Joe Pea

### Timing problem Isn't a resize callback ultimately due to a recalc that a style observer would also be able to observe? Because of this, I think ResizeObservers and ComputedStyleObservers...

Here's a prime example of current timing issues with observer callbacks: - https://github.com/whatwg/dom/issues/1105 That issue was unjustly closed because the closer thinks there's no problem to be solved, but rather...

By that logic we might as well type `event.target` as `HTMLElement` instead of `EventTarget` which is also totally wrong. I don't think this makes a lot of sense.

Does a browser then need to look at `content-type` headers? And if so, then what's the point of import attributes if the browser can look at content-type?

It seems then that the import attribute should just be the ultimate source of truth, so that `from './foo.dope' with { type: "wasm" }` will fail if a JS content-type...

I hear what you are saying, but people will intuit the following: - `import foo from 'foo'` - "treat it as a JS file (error at me if it is...

> Perhaps, but since wasm isn’t a valid type value, you’ll learn the proper mental model quickly. yes, and it also won't make sense. Sure, I'll learn what to do,...

> Not having the attribute also allows libraries to swap a JS implementation with a potentially faster wasm one. I get what you're saying. By this same token, this seems...

> Not having the attribute also allows libraries to swap a JS implementation with a potentially faster wasm one. @nicolo-ribaudo I can imagine wanting to switch from a JSON file...

It's been 1.5 years since the last update.