Removes cache fps range when SetFpsRange() gets invalid input
This CL removes cache fps range entry if SetFpsRange() gets invalid input so that it will use default fps range rather than unexpected cache range. In addition, it fixes a bug of method typo in options.js and avoids reporting error when the SetFpsRange() fails intendedly. Bug: None Test: Manually. Change-Id: I924a663607a5d0829c8f0aa5873a7488aca072f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1687569 Auto-Submit: Wei Lee <wtlee@chromium.org> Reviewed-by:Shik Chen <shik@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Sheng-hao Tsao <shenghao@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#676309}
Showing
Please register or sign in to comment