Skip to content

Missing tasks in parallel steps in Background Fetch #176

Open
@dontcallmedom-bot

Description

@dontcallmedom-bot

While crawling Background Fetch, the following algorithms fire an event, or resolve or reject a Promise, within a step that runs in parallel without first queuing a task:

  • The create record objects algorithm resolves/rejects a promise directly in a step that runs in parallel (steps 2.8.3 and 2.8.4)
  • The get(id) algorithm resolves/rejects a promise directly in a step that runs in parallel
  • The getIds() algorithm resolves/rejects a promise directly in a step that runs in parallel
  • The abort() algorithm resolves/rejects a promise directly and throws an exception in a step that runs in parallel
  • The updateUI(options) algorithm resolves/rejects a promise directly in a step that runs in parallel

See Dealing with the event loop in the HTML specification for guidance on how to deal with algorithm sections that run in parallel.

Cc @dontcallmedom @tidoust

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions