Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(6)

Side by Side Diff: third_party/WebKit/Source/core/frame/Settings.in

Issue 2338623004: Add Blink setting to block doc.written scripts on 2g-like networks (Closed)
Patch Set: Update test results after rebase Created 4 years, 2 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
OLDNEW
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 358 matching lines...) Expand 10 before | Expand all | Expand 10 after
369 369
370 progressBarCompletion type=ProgressBarCompletion, initial=ProgressBarCompletion: :LoadEvent 370 progressBarCompletion type=ProgressBarCompletion, initial=ProgressBarCompletion: :LoadEvent
371 371
372 historyEntryRequiresUserGesture initial=false 372 historyEntryRequiresUserGesture initial=false
373 373
374 # Do we want to try to save screen real estate in the media player by hiding 374 # Do we want to try to save screen real estate in the media player by hiding
375 # the volume slider / mute button? 375 # the volume slider / mute button?
376 preferHiddenVolumeControls initial=false 376 preferHiddenVolumeControls initial=false
377 377
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, for users on 2G or connections that are
380 # effectively 2G.
381 disallowFetchForDocWrittenScriptsInMainFrameIfEffectively2G initial=false
382
383 # Whether to disallow network fetches for parser blocking scripts in the main
379 # frame inserted via document.write, for users on slow connections. 384 # frame inserted via document.write, for users on slow connections.
380 disallowFetchForDocWrittenScriptsInMainFrameOnSlowConnections initial=false 385 disallowFetchForDocWrittenScriptsInMainFrameOnSlowConnections initial=false
381 386
382 # Whether to disallow network fetches for parser blocking scripts in the main 387 # Whether to disallow network fetches for parser blocking scripts in the main
383 # frame inserted via document.write, regardless of connection type. 388 # frame inserted via document.write, regardless of connection type.
384 disallowFetchForDocWrittenScriptsInMainFrame initial=false 389 disallowFetchForDocWrittenScriptsInMainFrame initial=false
385 390
386 # The autoplay gesture override experiment is described in crbug.com/487345 . 391 # The autoplay gesture override experiment is described in crbug.com/487345 .
387 autoplayExperimentMode type=String, initial="off" 392 autoplayExperimentMode type=String, initial="off"
388 393
(...skipping 27 matching lines...) Expand all
416 # Whether the CSSPreloadScanner is used for externally CSS preloads. NoPreload 421 # Whether the CSSPreloadScanner is used for externally CSS preloads. NoPreload
417 # indicates that the scanner will be used, but no preloads issued. 422 # indicates that the scanner will be used, but no preloads issued.
418 cssExternalScannerNoPreload initial=false 423 cssExternalScannerNoPreload initial=false
419 cssExternalScannerPreload initial=false 424 cssExternalScannerPreload initial=false
420 425
421 browserSideNavigationEnabled initial=false 426 browserSideNavigationEnabled initial=false
422 427
423 # Some platforms have media subsystems which are too buggy to allow preloading 428 # Some platforms have media subsystems which are too buggy to allow preloading
424 # of content by default. See http://crbug.com/612909 for details. 429 # of content by default. See http://crbug.com/612909 for details.
425 forcePreloadNoneForMediaElements initial=false 430 forcePreloadNoneForMediaElements initial=false
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698