Allow localhost manifests via a developer tool switch. |
|||||
Issue descriptionAllow localhost manifests via a developer tool switch as discussed on https://github.com/w3c/payment-method-manifest/pull/19. For testing and development, allow the (1) payment method identifier, (2) default application URL, and (2) supported origin to be localhost. For example: http://localhost:8080/some-path http://127.0.0.1:8080/some-path http://[::1]/some-path
,
Oct 30 2017
,
Oct 30 2017
DevTools team: Where would be the best place in DevTools for a "Allow localhost payment manifests" toggle?
,
Oct 30 2017
CC-ing devtools folks.
,
Nov 12 2017
Spoke with DevTools team in person. Because this feature is going to be used by a small fraction of developers, the team suggested a command-line flag. Because this flag would be disabling a security feature, Chrome should display a butter bar with a security warning. Dismissing the bar should restore the security to the safe level.
,
Nov 21 2017
> Dismissing the bar should restore the security to the safe level. Existing security features in https://cs.chromium.org/chromium/src/chrome/browser/ui/startup/bad_flags_prompt.cc don't do this, so we're not going to either.
,
Nov 21 2017
,
Dec 14 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rouslan@chromium.org
, Oct 30 2017