Source/core/frame/Settings.in - Issue 979033003: Move code from StyleResolver to ViewportStyleResolver.

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: Source/core/frame/Settings.in

Issue 979033003: Move code from StyleResolver to ViewportStyleResolver. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Rebased Created 5 years, 9 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:

View unified diff | Download patch

« no previous file with comments | « Source/core/css/resolver/ViewportStyleResolver.cpp ('k') | Source/core/frame/SettingsDelegate.h » ('j') | no next file with comments »

OLD	NEW
1 # Defines properties which are available on the Settings object.	1 # Defines properties which are available on the Settings object.

2 #	2 #

3 # Please think carefully before adding a new Setting. Some questions to	3 # Please think carefully before adding a new Setting. Some questions to

4 # consider are:	4 # consider are:

5 # - Should this be a RuntimeEnabledFeature instead? Settings are for things	5 # - Should this be a RuntimeEnabledFeature instead? Settings are for things

6 # which we support either values of at runtime. Features are set at renderer	6 # which we support either values of at runtime. Features are set at renderer

7 # process startup and are never changed. Features also tend to be set to a	7 # process startup and are never changed. Features also tend to be set to a

8 # value based on the platform or the stability of the code in question, where	8 # value based on the platform or the stability of the code in question, where

9 # as settings both codepaths need to be stable.	9 # as settings both codepaths need to be stable.

10 # - How will you ensure test coverage of all relevant values of your setting?	10 # - How will you ensure test coverage of all relevant values of your setting?

(...skipping 306 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
317 inlineTextBoxAccessibilityEnabled initial=false	317 inlineTextBoxAccessibilityEnabled initial=false

318	318

319 # If true, context menu will be shown on mouse up instead of mouse down.	319 # If true, context menu will be shown on mouse up instead of mouse down.

320 # Typically enabled on Windows to match platform convention.	320 # Typically enabled on Windows to match platform convention.

321 showContextMenuOnMouseUp initial=false	321 showContextMenuOnMouseUp initial=false

322	322

323 disableReadingFromCanvas initial=false	323 disableReadingFromCanvas initial=false

324 strictMixedContentChecking initial=false	324 strictMixedContentChecking initial=false

325 strictPowerfulFeatureRestrictions initial=false	325 strictPowerfulFeatureRestrictions initial=false

326 logDnsPrefetchAndPreconnect initial=false	326 logDnsPrefetchAndPreconnect initial=false

	327

	328 # If true, the UA styles will include viewportAndroid.css. It is used for

	329 # Android, and dynamically set by the inspector for mobile emulation.

	330 useMobileViewportStyle initial=false, invalidate=ViewportRule

OLD	NEW