Remove "BlockageIndicated" from TabSpecificContentSettings
Image models are not 1:1 with content settings. This CL replaces per-tab storage from TSCS to a new per-WebContents container, ContentSettingImageModelState, which contains information that is 1:1 with image models. This allows us to remove custom logic for image models that aren't backed by a single content setting. The new behavior works like this: 1. Per-tab state is stored in ContentSettingImageModelState 2. ShouldRunAnimation / SetAnimationHasRun updates the state 3. State is additionally updated when an image is hidden (3) entails a bunch of changes to UpdateFromWebContents, namely, making it return a boolean for whether the update triggered visibility. The benefit of this CL is that all of the logic to control animation of image models come from ContentSettingImageModel. This CL has no intended user-facing behavior change. Bug: 900645 Change-Id: I99c36a8184a0e04e6356e58fbc93a5aed3f03127 Reviewed-on: https://chromium-review.googlesource.com/c/1310674Reviewed-by:Martin Šrámek <msramek@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#607331}
Showing
This diff is collapsed.
Please register or sign in to comment