third_party/WebKit/Source/core/frame/Settings.in - Issue 1662933003: Convert scroll anchoring flag to runtime-enabled feature.

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

Issue 1662933003: Convert scroll anchoring flag to runtime-enabled feature. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: rebase Created 4 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:

View unified diff | Download patch

« no previous file with comments | « content/renderer/render_view_impl.cc ('k') | third_party/WebKit/Source/core/layout/ScrollAnchorTest.cpp » ('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 367 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
378 # Whether to disallow network fetches for parser blocking scripts in the main	378 # Whether to disallow network fetches for parser blocking scripts in the main

379 # frame inserted via document.write.	379 # frame inserted via document.write.

380 disallowFetchForDocWrittenScriptsInMainFrame initial=false	380 disallowFetchForDocWrittenScriptsInMainFrame initial=false

381	381

382 # The autoplay gesture override experiment is described in crbug.com/487345 .	382 # The autoplay gesture override experiment is described in crbug.com/487345 .

383 autoplayExperimentMode type=String, initial="off"	383 autoplayExperimentMode type=String, initial="off"

384	384

385 # When DevTools is emulating mobile device, frame resize may mean device size ha s changed,	385 # When DevTools is emulating mobile device, frame resize may mean device size ha s changed,

386 # which in turn affects media queries.	386 # which in turn affects media queries.

387 resizeIsDeviceSizeChange initial=false	387 resizeIsDeviceSizeChange initial=false

388

389 # Scrolls to compensate for layout movements (bit.ly/scroll-anchoring).

390 scrollAnchoringEnabled initial=false

OLD	NEW