playwright/browser_patches
2020-06-24 10:04:11 -07:00
..
buildbots chore(webkit): add libvpx Windows build instructions (#2649) 2020-06-22 12:49:30 -07:00
firefox browser(firefox): do not fail when decoding large responses (#2671) 2020-06-22 16:01:16 -07:00
tools devops: prettify telegram messages 2020-02-07 12:42:20 -08:00
webkit docs: linux core dump instructions (#2690) 2020-06-24 10:04:11 -07:00
checkout_build_archive_upload.sh Revert "devops: teach buildbots to run sanity check script (#2064)" (#2075) 2020-05-01 12:09:36 -07:00
download.sh devops: combine webkit-wpe and webkit-gtk together 2020-01-17 16:27:07 -08:00
export.sh chore: export juggler as a standalone folder for browser build (#2432) 2020-06-02 16:51:13 -07:00
prepare_checkout.sh chore: export juggler as a standalone folder for browser build (#2432) 2020-06-02 16:51:13 -07:00
README.md docs: link to wk upstream status 2020-05-29 11:30:17 -07:00
sanitize_and_compress_log.js devops: use node.js to gzip logs 2020-04-20 02:52:26 -07:00
upload.sh devops: use node.js to gzip logs 2020-04-20 02:52:26 -07:00

Contributing Browser Patches

Firefox and WebKit have additional patches atop to expose necessary capabilities.

Ideally, all these changes should be upstreamed. For the time being, it is possible to setup a browser checkout and develop from there.

WebKit upstream status

1. Setting up local browser checkout

From the playwright repo, run the following command:

$ ./browser_patches/prepare_checkout.sh firefox <path to checkout>

(you can optionally pass "webkit" for a webkit checkout)

If you don't have a checkout, don't pass a path and one will be created for you in ./browser_patches/firefox/checkout

NOTE: this command downloads GBs of data.

This command will:

  • create a browser_upstream remote in the checkout
  • create a playwright-build branch and apply all playwright-required patches to it.

2. Developing a new change

You want to create a new branch off the playwright-build branch.

Assuming that you're under ./browser_patches/firefox/checkout:

$ git checkout -b my-new-feature playwright-build
$ # develop my feature on the my-new-feature branch ....

3. Exporting your change to playwright repo

Once you're happy with the work you did in the browser-land, you want to export it to the playwright repo.

Assuming that you're in the root of the playwright repo and that your browser checkout has your feature branch checked out:

$ ./browser_patches/export.sh firefox <path to checkout>

This script will:

  • create a new patch and put it to the ./browser_patches/firefox/patches/
  • update the ./browser_patches/firefox/UPSTREAM_CONFIG.sh if necessary
  • bump the ./browser_patches/firefox/BUILD_NUMBER number.

If you omit the path to your checkout, the script will assume one is located at ./browser_patches/firefox/checkout

Send a PR to the Playwright repo to be reviewed.

4. Rolling Playwright to the new browser build

Once the patch has been committed, the build bots will kick in, compile and upload a new browser version to all the platforms.

You can check the CDN status:

$ ./browser_patches/tools/check_cdn.sh

As the builds appear, you can roll to a new browser version in the ./browsers.json file.