Closed Bug 1716019 Opened 3 years ago Closed 3 years ago

dynamic import should be retryable

Categories

(Core :: DOM: Core & HTML, defect)

Firefox 89
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: haoqunjiang, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36

Steps to reproduce:

See https://github.com/sodatea/dynamic-import-retry-demo#readme

The reproduction simulates the following situation:

  • The user loads a webpage
  • Goes offline
  • Triggered a dynamic import on the page, which throws an error
  • Goes online again
  • Retries the failed dynamic import

Actual results:

The second dynamic import also fails, without initiating any network request

Expected results:

https://github.com/tc39/ecma262/pull/1645

Based on idempotency change to the ECMA spec for dynamic imports, the error case does not have to be cached, so the 2nd dynamic import to the same URL should trigger a 2nd HTTP request

The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Netmonitor
Product: Firefox → DevTools
Component: Netmonitor → Networking
Product: DevTools → Core

For anyone who's interested in looking into this issue:

I realized it's not a bug after contacting the Chromium team. However, I don't think this particular part of the HTML spec does the right thing.
So please join the discussion at https://github.com/whatwg/html/issues/6768

This looks like a DOM bug.

Component: Networking → DOM: Core & HTML
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.