Commit 16d6164b authored by Sky Malice's avatar Sky Malice Committed by Commit Bot

[Feed] Wrap comments at 100 characters.

Change-Id: I35da57c3825753bf348b8388c087249bdc928834
Reviewed-on: https://chromium-review.googlesource.com/1089639Reviewed-by: default avatarTheresa <twellington@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565060}
parent a711806f
......@@ -154,8 +154,7 @@ public class FeedNewTabPage extends BasicNativePage {
stream.getView().setBackgroundColor(Color.WHITE);
mRootView.addView(stream.getView());
// TODO(skym): This is a work around for outstanding Feed bug. Should be
// removed on next DEPS roll.
// TODO(skym): This is a work around for outstanding Feed bug.
stream.triggerRefresh();
// TODO(https://crbug.com/803317): Call appropriate lifecycle methods.
......
......@@ -40,10 +40,9 @@ public class FeedSchedulerBridge implements SchedulerApi {
}
/*
* Sets our copy of the RequestManager. Should be done as early as possible,
* as the scheduler will be unable to trigger refreshes until after it has a
* reference to a RequestManager. When this is called, it is assumed that
* the RequestManager is initialized and can be used.
* Sets our copy of the RequestManager. Should be done as early as possible, as the scheduler
* will be unable to trigger refreshes until after it has a reference to a RequestManager. When
* this is called, it is assumed that the RequestManager is initialized and can be used.
*
* @param requestManager The interface that allows us make refresh requests.
*/
......@@ -59,12 +58,11 @@ public class FeedSchedulerBridge implements SchedulerApi {
int nativeBehavior = nativeShouldSessionRequestData(mNativeBridge,
sessionManagerState.hasContent, sessionManagerState.contentCreationDateTimeMs,
sessionManagerState.hasOutstandingRequest);
// If this breaks, it is because SchedulerApi.RequestBehavior and the
// NativeRequestBehavior defined in feed_scheduler_host.h have diverged.
// If this happens during a feed DEPS roll, it likely means that the
// native side needs to be updated. Note that this will not catch new
// values and should handle value changes. Only removals/renames will
// cause compile failures.
// If this breaks, it is because SchedulerApi.RequestBehavior and the NativeRequestBehavior
// defined in feed_scheduler_host.h have diverged. If this happens during a feed DEPS roll,
// it likely means that the native side needs to be updated. Note that this will not catch
// new values and should handle value changes. Only removals/renames will cause compile
// failures.
switch (nativeBehavior) {
case NativeRequestBehavior.REQUEST_WITH_WAIT:
return SchedulerApi.RequestBehavior.REQUEST_WITH_WAIT;
......
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