chrome/common/insecure_content_renderer.mojom - Issue 2674843002: Convert ChromeViewMsg_SetAllowRunningInsecureContent to use mojo.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/common/insecure_content_renderer.mojom

Issue 2674843002: Convert ChromeViewMsg_SetAllowRunningInsecureContent to use mojo. (Closed)

Patch Set: Created 3 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 // Copyright 2017 The Chromium Authors. All rights reserved.

	2 // Use of this source code is governed by a BSD-style license that can be

	3 // found in the LICENSE file.

	4

	5 module chrome.mojom;

	6

	7 // Renderers of possibly insecure mixed-content.

	8 interface InsecureContentRenderer {

	9 // Sent to allow or forbid the running of insecure mixed-content. It may also

	10 // reload the frame afterwards.

	11 SetAllowRunningInsecureContent(bool allow, bool reload_frame);
	Sam McNally 2017/02/03 17:36:58 These parameters seem unnecessary; the renderer ca These parameters seem unnecessary; the renderer can correctly predict their values. Can we get rid of them? nigeltao1 2017/02/04 06:29:10 Done. Show quoted text On 2017/02/03 17:36:58, Sam McNally wrote: > These parameters seem unnecessary; the renderer can correctly predict their > values. Can we get rid of them? Done.
	12 };

OLD	NEW