Skip to content

goTo relative paths should use the origin from the current browser session #47

@hawkeyexl

Description

@hawkeyexl

If you perform multiple goTo steps, steps after the first should be able to use the origin of the current browser session to resolve relative paths.

Open question: If a default origin is specified in the config, which takes precedence: the config's origin or the current session's origin? I'm leaning toward the session's origin.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions