javascript.operators.import - don't cache HTTP errors

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

The description says

Only evaluation failures are cached; if a module fails to load or link, the next import may try to load and link the module again. The browser may or may not cache the result of the fetch operation, but it should follow typical HTTP semantics, so handling such network failures should not be different from handling fetch() failures.

. But this wasn't the case in the spec until recently and browsers still cache the failures. https://github.com/whatwg/html/pull/10327 has changed the spec to not cache the HTTP errors.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

A new row in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import#browser_compatibility that shows which browser doesn't cache the HTTP errors.

Did you test this? If so, how?

I haven't tested this.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

• Browser releases
  • Firefox 155 beta

    • A dynamic import() that fails due to a network or HTTP error is no longer cached as a failure in the module map, so retrying the same specifier can now succeed.
      https://www.firefox.com/en-US/firefox/155.0beta/releasenotes/#:~:text=A%20dynamic%20import()%20that%20fails%20due%20to%20a%20network%20or%20HTTP%20error%20is%20no%20longer%20cached%20as%20a%20failure%20in%20the%20module%20map%2C%20so%20retrying%20the%20same%20specifier%20can%20now%20succeed.

    • https://bugzilla.mozilla.org/show_bug.cgi?id=2055211
  • WebKit (not released yet)
    • https://bugs.webkit.org/show_bug.cgi?id=319492
    • https://github.com/WebKit/WebKit/pull/69559
    • Included in Safari TP 252
  • Chromium (not merged yet)
    • https://issues.chromium.org/issues/534781954
• Other runtimes
  • Node: https://github.com/nodejs/node/issues/64517
  • Deno: https://github.com/denoland/deno/issues/36057

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import

MDN metadata

Start at the javascript.operators.import compatibility data entry linked from the MDN page. Check the Firefox release notes and linked WebKit and Chromium issues to verify which browser support is released, then add the corresponding compatibility data and confirm the entry represents HTTP-error retry behavior.