Issue metadata
Sign in to add a comment
|
Handle late PSG notifications in TabLifecycleUnitSource::OnLifecycleStateChanged |
||||||||||||||||||
Issue descriptionSee https://chromium.googlesource.com/chromium/src/+/refs/changes/28/1117128/8/chrome/browser/resource_coordinator/tab_lifecycle_unit_source.cc#229, where lifecycle state may be prematurely updated due to late-arriving notifications pertaining to an earlier navigation.
,
Sep 20
It is very important to figure out whether we get this right. The state in the TabLifecycleUnit (in the browser) must be in sync with the state in the PageScheduler (in the renderer). I believe that the TabLifecycleUnit should not drop notifications from the renderer, since the renderer is the source of truth. An exception to that rule is when the renderer is swapped during a navigation... we should make sure not to get a late state change from the old renderer.
,
Sep 21
The NextAction date has arrived: 2018-09-21 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by fdoray@chromium.org
, Sep 20