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

Issue 2274693003: [MD settings] scroll to section from URL (Closed)

Created:
4 years, 4 months ago by dschuyler
Modified:
4 years, 3 months ago
Reviewers:
tommycli, michaelpg
CC:
chromium-reviews, michaelpg+watch-md-settings_chromium.org, michaelpg+watch-md-ui_chromium.org, dbeam+watch-settings_chromium.org, stevenjb+watch-md-settings_chromium.org, arv+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

[MD settings] scroll to section from URL This CL moves the doWhenReady higher in the call chain to fix scrolling to a section directly from an entered URL in the omnibox. BUG=640102 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Committed: https://crrev.com/cd5548a75759006cf54eaf13d662fc68e29ac33e Cr-Commit-Position: refs/heads/master@{#414111}

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+10 lines, -20 lines) Patch
M chrome/browser/resources/settings/settings_page/main_page_behavior.js View 3 chunks +10 lines, -20 lines 1 comment Download

Messages

Total messages: 15 (9 generated)
dschuyler
4 years, 4 months ago (2016-08-23 23:52:08 UTC) #5
tommycli
lgtm
4 years, 4 months ago (2016-08-23 23:58:58 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2274693003/1
4 years, 4 months ago (2016-08-24 18:26:30 UTC) #10
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 4 months ago (2016-08-24 18:34:16 UTC) #11
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/cd5548a75759006cf54eaf13d662fc68e29ac33e Cr-Commit-Position: refs/heads/master@{#414111}
4 years, 4 months ago (2016-08-24 18:35:59 UTC) #13
michaelpg
4 years, 4 months ago (2016-08-24 22:02:00 UTC) #15
Message was sent while issue was closed.
https://codereview.chromium.org/2274693003/diff/1/chrome/browser/resources/se...
File chrome/browser/resources/settings/settings_page/main_page_behavior.js
(right):

https://codereview.chromium.org/2274693003/diff/1/chrome/browser/resources/se...
chrome/browser/resources/settings/settings_page/main_page_behavior.js:50:
doWhenReady(
can we change doWhenReady to run the callback immediately if the test is
initially true?

otherwise we are adding a 10ms delay to every transition for no reason, which
makes testing harder and the order things happen more confusing

Powered by Google App Engine
This is Rietveld 408576698