Tab.java needsReload duplicates navigation_controller needs_reload_. |
||
Issue descriptionAs stated in the summary. It appears that the native needs_reload is only used when the tab is explicitly discarded [1]. The android version of needsReload is used when the tab is killed by the system, which is common on android (in other platforms it will just sad-tab). It looks like since Tab.java:mNeedsReload only ends up kicking off a call to navigation_controller_->SetNeedsReload(), it would be equivalent to just set that directly. This would avoid the problem of crbug.com/828400 where needs_reload is not reset when a new page load comes in. However, there is a comment in tab_lifecycle_unit.cc suggesting that the native needs_reload is changing/going away [2]. This should be understood before tearing out the android path. [1] https://cs.chromium.org/chromium/src/chrome/browser/resource_coordinator/tab_manager.cc?rcl=7a462a5db6eeeedd30c5e4abfa9f45b6a8aca7f6&l=305 [2] https://cs.chromium.org/chromium/src/chrome/browser/resource_coordinator/tab_lifecycle_unit.cc?rcl=b3b1d34a763ebf8a5153c74d4917fcb09b40a2e5&l=63
,
May 4 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, May 2 2018