feat(browser): roll webkit to r1219

microsoft · May 6, 2020 · 3bff45f · 3bff45f
1 parent 840e420
commit 3bff45f
Show file tree

Hide file tree

Showing 6 changed files with 8 additions and 8 deletions.
diff --git a/browsers.json b/browsers.json
@@ -10,7 +10,7 @@
     },
     {
       "name": "webkit",
-      "revision": "1216"
+      "revision": "1219"
     }
   ]
 }
diff --git a/docs/ci.md b/docs/ci.md
@@ -24,7 +24,7 @@ steps:
     run: npm test
 ```
 
-We run [our tests](/.github/workflows/tests.yml) on GitHub Actions, across a matrix of 3 platforms (Windows, Linux, macOS) and 3 browsers (Chromium, Firefox, WebKit).
+We run [our tests](/.github\workflows\tests.yml) on GitHub Actions, across a matrix of 3 platforms (Windows, Linux, macOS) and 3 browsers (Chromium, Firefox, WebKit).
 
 ## Docker
 
@@ -42,7 +42,7 @@ We run our tests on Travis CI over a Linux agent (Ubuntu 18.04). Use our [Travis
 
 ## CircleCI
 
-We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md). Use our [CircleCI configuration](/.circleci/config.yml) to create your own.
+We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md). Use our [CircleCI configuration](/.circleci\config.yml) to create your own.
 
 ## AppVeyor
 

diff --git a/docs/development/releasing.md b/docs/development/releasing.md
@@ -15,7 +15,7 @@ Releasing is a 3-step process.
 
 Once release branch is pushed, it's last commit will be picked up by our CI/CD:
 - make sure commit passes all the bots. If there are any failures, carefully inspect failures to see if these are flakes.
-- the [`publish_canary`](../../.github/workflows/publish_canary.yml) workflow will publish a `@next` version for the commit - this will be our **release candidate**. Go manually to it's page on NPM   to see what it looks like. Try installing locally.
+- the [`publish_canary`](..\..\.github\workflows\publish_canary.yml) workflow will publish a `@next` version for the commit - this will be our **release candidate**. Go manually to it's page on NPM   to see what it looks like. Try installing locally.
 
 # 2. Prepare release notes
 
@@ -30,5 +30,5 @@ Once release branch is pushed, it's last commit will be picked up by our CI/CD:
 
 1. Hit "publish release"
 
-Once release is published, the [`publish_release`](../../.github/workflows/publish_release.yml) will kick in and publish package version on NPM.
+Once release is published, the [`publish_release`](..\..\.github\workflows\publish_release.yml) will kick in and publish package version on NPM.
 
diff --git a/docs/intro.md b/docs/intro.md
@@ -80,7 +80,7 @@ Firefox and WebKit work across the 3 platforms (Windows, macOS, Linux):
 * **macOS**: Requires 10.14 or above.
 * **Linux**: Depending on your Linux distribution, you might need to install additional
   dependencies to run the browsers.
-  * For Ubuntu 18.04, the additional dependencies are defined in [our Docker image](docker/Dockerfile.bionic),
+  * For Ubuntu 18.04, the additional dependencies are defined in [our Docker image](docker\Dockerfile.bionic),
     which is based on Ubuntu.
 
 <br>

diff --git a/packages/playwright-webkit/browsers.json b/packages/playwright-webkit/browsers.json
@@ -2,7 +2,7 @@
   "browsers": [
     {
       "name": "webkit",
-      "revision": "1216"
+      "revision": "1219"
     }
   ]
 }
diff --git a/packages/playwright/browsers.json b/packages/playwright/browsers.json
@@ -10,7 +10,7 @@
     },
     {
       "name": "webkit",
-      "revision": "1216"
+      "revision": "1219"
     }
   ]
 }