Update page: 1.7.1 → 1.11.3 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ page (1.7.1 → 1.11.3) · Repo · Changelog

Release Notes

1.11.3

Fixes a regression with options being passed into start()

1.11.2

Fixes a bad build that was created in 1.11.1

1.11.1

This is a patch release, fixing a bug with the page instance being configured twice when page.create() is used. Specials thanks to @jsnajdr for this bug fix. Pull request

1.11.0

This is a minor release that adds the clickHandler property.

1.10.2

This is a patch release, fixing #501

1.10.1

This is a patch release, fixing an issue from when clicking a link from within a page with query parameters, and navigating to the same page (such as a hash). Previously the querystring was not included in the Context object. This fixes that.

1.10.0

This is a minor release, adding the new page.create() API, for creating distinct page objects.

Calling page.create(options) create a new page function that behaves just like the global page. It contains its own internal state, options, and event handlers. You can target the page to another window, like an iframe or a popup, if you want.

var newPage = page.create({
  window: someIframe.contentWindow
});

The main reason for adding this feature was to clean up or testing infrastructure. Numerous things had to be done in the past to make sure each test was cleanly in isolation. That stuff is no longer necessary now that we can just create a new page instance for each test.

1.9.0

This is a minor release, adding a new ES module bundle to the distributed package. This module is available as page.mjs. It contains one export, the default export which is the usual page object.

<script type="module">
  import page from "//unpkg.com/page/page.mjs";

  page('/home', () => {
    showHome();
  });
  page();
</script>

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)