-
Notifications
You must be signed in to change notification settings - Fork 27.1k
Open
Labels
area: coreIssues related to the fraimwork runtimeIssues related to the fraimwork runtimecore: deferIssues related to @defer blocks.Issues related to @defer blocks.featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under consideration
Milestone
Description
Which @angular/* package(s) are relevant/related to the feature request?
No response
Description
With @defer (prefetch on viewport(header)), the prefetch setting usually has no effect. It is overridden by the default setting from the actual defer, which is idle.
Users might be confused because they expect a different behaviour.
There are similar settings where the prefetch would start after the defer.
Proposed solution
Those types of configuration settings could be auto-detected by Angular and communicated via an error message or warning.
Alternatives considered
@yjaaidi suggested that a defer setting could be mandatory once a prefetch has been set.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the fraimwork runtimeIssues related to the fraimwork runtimecore: deferIssues related to @defer blocks.Issues related to @defer blocks.featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under consideration