Skip to content

OpenWindow lacks either sourceDocument or userInvolvement argument when running Navigate algorithm #1776

@saschanaz

Description

@saschanaz

In the step 7.2.1 of openWindow:

HandleNavigate: Navigate newContext to url with exceptionsEnabled true, and historyHandling "replace".

It doesn't pass source document here so it becomes the default value null, nor the user involvement argument which becomes "none". And the step 5 of the navigate algorithm:

  1. If sourceDocument is null:
    1. Assert: userInvolvement is "browser UI".

Which ends up with an assertion failure.

There's no document to pass (as this is a service worker function), so it seems the only way to make it happy is to pass the user involvement argument, but not sure "browser UI" fits here because the caller is certainly the script here. Thoughts?

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