Secure contexts: remove user-data-dir requirement for --unsafely-treat-insecure-origin-as-secure |
||
Issue descriptionChrome is currently fairly draconian about the ways in which it allows developers to treat otherwise insecure origin as secure for development purposes. Chrome must be started with two distinct command-line flags, one of which forces the developer into a distinct profile directory. This made sense at the time, but provides a level of friction that seems out of balance with the actual risk developers are opting-into. We should consider being less draconian.
,
Aug 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/55dab613843031ab360193116f5d80d0d23308fb commit 55dab613843031ab360193116f5d80d0d23308fb Author: Mike West <mkwst@chromium.org> Date: Fri Aug 25 15:36:26 2017 Secure contexts: remove user-data-dir requirement. Requiring developers to create a new profile in order to debug features that need secure contexts is overkill. Let's loosen that requirement. Bug: 757631 Change-Id: Ic8edf5172f11f6e2bdff94b9d45b1bd9fbbacf7d Reviewed-on: https://chromium-review.googlesource.com/625094 Reviewed-by: Steven Holte <holte@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Emily Stark <estark@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#497417} [modify] https://crrev.com/55dab613843031ab360193116f5d80d0d23308fb/chrome/common/chrome_switches.cc [modify] https://crrev.com/55dab613843031ab360193116f5d80d0d23308fb/chrome/common/secure_origin_whitelist.cc [modify] https://crrev.com/55dab613843031ab360193116f5d80d0d23308fb/chrome/common/secure_origin_whitelist_unittest.cc [modify] https://crrev.com/55dab613843031ab360193116f5d80d0d23308fb/tools/metrics/histograms/histograms.xml
,
Sep 11 2017
Fixed by #2 |
||
►
Sign in to add a comment |
||
Comment 1 by mkwst@chromium.org
, Aug 21 2017