WebSocket: don't check the restricted port list synchronously
In 2017 the HTML standard changed to no longer check the bad port list synchronously in the WebSocket constructor, instead relying on the lower-level check in Fetch to cause an asynchronous failure. Safari is now implementing this (https://github.com/web-platform-tests/wpt/pull/26392#issuecomment-722593477), so update our implementation to match. BUG=705534 Change-Id: I29c35fa2307a1215d5f382f86ca97bbfd17aba2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521874Reviewed-by:Yoichi Osato <yoichio@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#824747}
Showing
Please register or sign in to comment