New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 900045 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug

Blocking:
issue 824647



Sign in to add a comment

Reject dynamic import on ServiceWorkerGlobalScope

Project Member Reported by nhiroki@chromium.org, Oct 30

Issue description

Spec issue: https://github.com/w3c/ServiceWorker/issues/1356#issuecomment-433411852

Dynamic import on ServiceWorkerGlobalScope is controversial in terms of service worker's script installation (see the spec issue for details). At the F2F meeting, for now we decided to reject dynamic import on ServiceWorkerGlobalScope until we understand real usage of module service workers and problems around dynamic import + script installation.
 
Blocking: 824647
Cc: falken@chromium.org
Copied from the falken@'s comment on the spec issue:

> It turned out Chrome is the only browser with immediate plans to implement module service workers.
> 
> There was rough consensus that throwing on dynamic imports for now is the safe thing to do, with room to change later as we get real usage of module service workers and understand the problem more.
> 
> Todo:
> Spec that static module imports are installed
> Spec that dynamic module imports throw
> Add tests.
For implementation, we can do the same thing with WorkletModulatorImpl::IsDynamicImportForbidden().

Sign in to add a comment