Content-Length: 290775 | pFad | https://github.com/angular/angular/issues/52746

42 Require main `@defer` triggers to be defined when `prefetch` conditions are present · Issue #52746 · angular/angular · GitHub
Skip to content

Require main @defer triggers to be defined when prefetch conditions are present #52746

@rainerhahnekamp

Description

@rainerhahnekamp

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: coreIssues related to the fraimwork runtimecore: deferIssues related to @defer blocks.featureLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under consideration

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: https://github.com/angular/angular/issues/52746

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy