Commit 88221907 authored by Weidong Guo's avatar Weidong Guo Committed by Commit Bot

Disable Overscan option for internal display in display settings

Bug: 781747
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I128f64943031087f08bdf3f64c743bcbb7784694
Reviewed-on: https://chromium-review.googlesource.com/820094
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: default avatarMitsuru Oshima <oshima@chromium.org>
Reviewed-by: default avatarSteven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523988}
parent 39c8129a
......@@ -175,7 +175,8 @@
<button is="cr-link-row" icon-class="subpage-arrow" class="indented hr"
id="overscan" label="$i18n{displayOverscanPageTitle}"
sub-label="$i18n{displayOverscanPageText}" on-tap="onOverscanTap_">
sub-label="$i18n{displayOverscanPageText}" on-tap="onOverscanTap_"
hidden$="[[!showOverscanSetting_(selectedDisplay)]]">
</button>
<settings-display-overscan-dialog id="displayOverscan"
......
......@@ -285,6 +285,16 @@ Polymer({
loadTimeData.getBoolean('enableTouchCalibrationSetting');
},
/**
* Returns true if the overscan setting should be shown for |display|.
* @param {!chrome.system.display.DisplayUnitInfo} display
* @return {boolean}
* @private
*/
showOverscanSetting_: function(display) {
return !display.isInternal;
},
/**
* @param {!Array<!chrome.system.display.DisplayUnitInfo>} displays
* @return {boolean}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment