Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(chromium): roll Chromium to r843427 #6797

Merged
merged 13 commits into from Feb 2, 2021
Merged

feat(chromium): roll Chromium to r843427 #6797

merged 13 commits into from Feb 2, 2021

Conversation

sadym-chromium
Copy link
Collaborator

@sadym-chromium sadym-chromium commented Feb 1, 2021

This corresponds to Chromium 89.0.4389.0
This roll includes:

  • Add SameParty attribute to cookies (crrev.com/c/2598846)
  • Anchor target=_blank implies rel=noopener (crrev.com/c/1630010)
  • Don't expect ignored elements in the AXTree (crrev.com/c/2505362)

BREAKING CHANGE:

  • page.$$ doesn't return skipped elements anymore.

@mathiasbynens

This comment has been minimized.

await page.goto(server.PREFIX + '/grid.html');
const screenshot = await page.screenshot({
clip: {
x: 50,
y: 600,
x: 0,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why would not the old test work?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to what I got from the CL 2643792, it used to cut the screenshot respecting the ViewPort position, but now the viewport moves to the clip first, and then taking screenshot. So the initial ViewPort offset doesn't matter anymore.
Actual output of the initial version of the test: https://i.imgur.com/QC2rTB5.png

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this is a breaking change in how Puppeteer's clip works?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it is.
Another breaking change is in the AriaQuery

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioned in the initial commit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, it's the breaking change in how the screenshot works. The clip is still respected in both offset and size. But the result screenshot is filled with white without respect of the initial ViewPort offset, only based on its size.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, there are some problems with the respecting offset in the screenshot.
EG this example produces the incorrectly-looking result: https://i.imgur.com/syIImrg.png

await page.setViewport({ width: 50, height: 50 });
await page.goto(server.PREFIX + '/grid.html');
const screenshot = await page.screenshot({
  clip: {
    x: 25,
    y: 25,
    width: 100,
    height: 100,
  },
});

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, thanks. Btw, per https://www.conventionalcommits.org/en/v1.0.0/#summary we should use this format:

BREAKING CHANGE: …

@sadym-chromium
Copy link
Collaborator Author

Please update versions.js as well

done

test/page.spec.ts Outdated Show resolved Hide resolved
test/page.spec.ts Outdated Show resolved Hide resolved
await page.goto(server.PREFIX + '/grid.html');
const screenshot = await page.screenshot({
clip: {
x: 50,
y: 600,
x: 0,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this is a breaking change in how Puppeteer's clip works?

Copy link
Member

@mathiasbynens mathiasbynens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM % lint and other failing CI checks

@mathiasbynens
Copy link
Member

As discussed offline, we should first roll to Chromium 89 and cut a Puppeteer release before landing this.

@sadym-chromium sadym-chromium changed the title feat(chromium) roll Chromium to r848005 feat(chromium): roll Chromium to r848005 Feb 1, 2021
@sadym-chromium
Copy link
Collaborator Author

As discussed offline, we should first roll to Chromium 89 and cut a Puppeteer release before landing this.

All the breaking changes are the same, so I just updated the versions of this PR so that it rolls Chromium 89.

@sadym-chromium sadym-chromium changed the title feat(chromium): roll Chromium to r848005 feat(chromium): roll Chromium to r843427 Feb 1, 2021
@sadym-chromium sadym-chromium linked an issue Feb 1, 2021 that may be closed by this pull request
@mathiasbynens mathiasbynens merged this pull request into main Feb 2, 2021
@mathiasbynens mathiasbynens deleted the chrome_update branch February 2, 2021 07:39
mathiasbynens pushed a commit that referenced this pull request Feb 2, 2021
This corresponds to Chromium 89.0.4389.0.

This roll includes:

- Add `SameParty` attribute to cookies
  https://crrev.com/c/2598846
- Anchor `target=_blank` implies `rel=noopener`
  https://crrev.com/c/1630010
- Don’t expect ignored elements in the AXTree
  https://crrev.com/c/2505362

BREAKING CHANGE: The built-in `aria/` selector query handler doesn’t return ignored elements anymore.

Issue: #6758
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Roll Chromium 89
3 participants